I tested this again using cloudmonkey by first creating a rule on port 800 using tcp and then
repeated the command with udp
createLoadBalancerRule algorithm=source name=test privateport=800 publicport=800 networkid=299aace4-a5c5-46f4-9ae7-92c86ded0cea
publicipid=2c49bd00-cd6b-44d4-93a5-7082ead298e0 protocol=udp
and I get the message
The range specified, 800-800, conflicts with rule 4214 which has 800-800
Is this supposed to work so we are looking at a bug here ?
Niclas
> On 19 Nov 2020, at 17:05, Daan Hoogland <daan.hoogland@gmail.com> wrote:
>
> Niclas, that doesn't sound good. I am assuming you use the UI and the VR as
> loadbalancer.
> if you look at the API [1], you'll find that protocol is actually not a
> required parameter. Can you;
> 1. check with dev-tools how the call is made?
> 2. try adding it through the API directly (using cloudmonkey or something
> like that)?
>
> [1]
> http://cloudstack.apache.org/api/apidocs-4.14/apis/createLoadBalancerRule.html
>
>
> On Thu, Nov 19, 2020 at 7:45 AM Niclas Lindblom
> <niclas_lindblom@icloud.com.invalid> wrote:
>
>> Hi,
>>
>> I need to add a load balancer rule for a specific port for both tcp and
>> udp. In the drop down I can only select one or the other and I am not able
>> to add 2 rules (one for each protocol) on the same port as I get a message
>> that there’s a conflict with existing rule. How do I achieve opening a port
>> for both tcp/udp into a VPC ?
>>
>> Thanks
>>
>> Niclas
>
>
>
> --
> Daan
|