On 06/05/2015 05:19 PM, Lou Berger wrote:
So what would you expect the logical-table config to look like when
supporting RFC4364 style BGP-VPNs?
I don't know; in fact I don't know how I would implement prorer
kernel forwarding for such VPN: using netns or multiple tables or ...
So I really don't know how to make the connection between kernel
mechanisms and SAFIs and won't have time to explore it (at least in
the short term...)
(and yes, there's some other really interesting config issues here
related to interfaces and tunneling, but I think we can keep that
discussion separate.)
agreed :D
Alain
Lou
On 6/5/2015 10:51 AM, Alain Ritoux wrote:
On 06/05/2015 04:28 PM, Jafar Al-Gharaibeh wrote:
Except that it doesn't index a table really, it does index a "domain"
(for lack of a better term) where multiple tables can live.
No, it really indexes a logical-table (ex-domain); the way the
logical-table is mapped into one of the numerous kernel tables
is the "low" part.
In the patchset we propose, we offer to map the logical-table
to the linux "main" table of a specific netns. If someone wants
to use it to populate a specific table of the basic netns, it's
fine, he just has to provide the code to configure the lower part
but the "upper" part, i.e. the handling of multiple RIB will stay
unchanged.
for example it could be
# current implementation
# this means "main" table netns "VRF1"
logical-table 1 netsn /var/run/VRF1
# possible extensions
# this means table #3 in defaut netns
logical-table 1 table 3
# this means table #3 in netns VRF1
logical-table 1 netsn /var/run/VRF1 table 3
But the way/cli/ZAPI to add static routes to logical-tabla 1 or
the way for a routing protocol, to populate this table must stay
unchanged, whatever the logical-table represents (nested netns /
tables / etc.)
Best regards
Alain
_______________________________________________
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
