jch at pps
Jul 7, 2012, 11:06 AM
Post #1 of 2
(157 views)
Permalink
|
|
Help with access-lists for babeld
|
|
Babel, as some of you may know, is a multi-protocol routing protocol:
a single babeld instance takes care of manipulating both v4 and v6
routes, somewhat similarly to what is done in BGP4+. This breaks
access-lists.
Quagga assumes that there are just two access lists in each protocol
instance, one for IN and one for OUT. The effect is that configuring
babeld with
distribute-list local_ipv4 out coloquinte
distribute-list local_ipv6 out coloquinte
causes the second statement to override the first one, and only v6
routes are being filtered.
I believe that bgpd has the same issue, but I haven't checked it, just
looked at the code.
Does anyone here have any plans to fix that? If not, what do people
suggest? Changing struct distribute to have four entries instead of
just two?
-- Juliusz
_______________________________________________
Quagga-dev mailing list
Quagga-dev [at] lists
http://lists.quagga.net/mailman/listinfo/quagga-dev
|
