Hi Vladislav,
I was looking at what options we have in OVN to implement a VRF-like
behavior and then remembered you had worked on the multiple routing
table feature.
On 11/19/21 17:07, Vladislav Odintsov wrote:
> This patch extends Logical Router's routing functionality.
> Now user may create multiple routing tables within a Logical Router
> and assign them to Logical Router Ports.
>
> Traffic coming from Logical Router Port with assigned route_table
> is checked against Logical_Router_Static_Routes with same route_table
> field value and routes to connected networks. If no route_table option
> is set to the LRP, routes' lookup is done agains routes with no
> route_table field value ("", empty string) and against routes to
> connected networks.
I was a bit surprised by the fact that if there's no static route with
the same route_table value as the ingress router port we go ahead and
match against all connected networks, regardless of their ports' route
tables.
Does it make sense to change this and perform longest prefix match in
general, always matching on route_table?
In this case connected routes could inherit the route_table value from
the corresponding router ports where they're defined.
Would that break your use case?
Thanks,
Dumitru
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
