On Fri, Sep 18, 2020 at 12:58 AM Alexander Constantinescu <
acons...@redhat.com> wrote:
> Hi Han
>
> Sorry for the late reply.
>
> Is this the current situation?
>>
>
> Yes, it is.
>
> When you say there are too many default routes, what do you mean in the
>> above example? How would the
Hi Han
Sorry for the late reply.
Is this the current situation?
>
Yes, it is.
When you say there are too many default routes, what do you mean in the
> above example? How would the SOUTH_TO_NORTH_IP solve the problem?
>
Each corresponds to a node in our cluster, like this:
ip4.src == &&
On Wed, Sep 16, 2020 at 10:07 AM Alexander Constantinescu <
acons...@redhat.com> wrote:
> In this example it is equivalent to just "ip4.src == 10.244.2.5/32"'.
>>
>
> Yes, I was just using it as an example (though, granted, noop example)
>
> Some background to help steer the discussion:
>
>
>
> In this example it is equivalent to just "ip4.src == 10.244.2.5/32"'.
>
Yes, I was just using it as an example (though, granted, noop example)
Some background to help steer the discussion:
Essentially the functionality here is to have south -> north traffic from
certain logical switch ports
On Wed, Sep 16, 2020 at 5:42 AM Alexander Constantinescu <
acons...@redhat.com> wrote:
>
> Hi
>
> I was wondering if anybody is aware of an IP address signifying "external
IP destinations"?
>
> Currently in OVN we can use the IP address 0.0.0.0/0 for match
expressions in logical routing policies /
Hi
I was wondering if anybody is aware of an IP address signifying "external
IP destinations"?
Currently in OVN we can use the IP address 0.0.0.0/0 for match expressions
in logical routing policies / ACLs when we want to specify a source or
destination IP equating to the pseudo term: "all IP
