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 Quagga-dev@lists.quagga.net https://lists.quagga.net/mailman/listinfo/quagga-dev
