On Thu, 6 Apr 2017, [email protected] wrote:
Hello.
Recently I started doing some basic simulations for traffic engineering
using my old Imunes with quagga, and I was suprised that my simple
config didnt work at all.
I'm surprised too by the behaviour.
Our documentation is too.
http://www.nongnu.org/quagga/docs/quagga.html#Using-BGP-Communities-Attribute
2nd example "This configuration only permit BGP routes which has BGP
communities value 0:80 or 0:90".
I think the current behaviour is the expected behaviour though.
Below goes the config.. Im NO expert in BGP, if this can be
implemented better and cleaner using standard community matching,
please let me show. For me, current implementation is not flexible.
Using community-list looks useless, 'route-map match community' would
be better using communities directly instead of community-list.. etc..
etc..
With the changes I introduced to community matching, this config
works fine.. everything is announced where it should and it looks
very clear and readable to me.
Yes, it seems useful.
Here is diff against old quagga (yes, I know its old.. I have my reasons,
lets not discuss this issue, I checked how its implemented in master
of current quagga, and it looks like nothing changed there):
http://borg.uu3.net/cgit/cgit.cgi/OEM.MY/quagga-0.99.15/commit/?h=bp_generic&id=2c7dcd91044e8a6844db20db5a8d646054464700
Implementation might NOT be perfect and might have bugs. Its here to start
discuss about how community matching could be done better (In my opinion).
ip community-list 10 permit 1:0 1:10 1:20 1:30
route-map CUST-OUT permit 10
match community 10
I suspect we can't really change the behaviour here. ;) An additional
clause ('any'?) for the match statement is probably best?
regards,
--
Paul Jakma | [email protected] | @pjakma | Key ID: 0xD86BF79464A2FF6A
Fortune:
"The pyramid is opening!"
"Which one?"
"The one with the ever-widening hole in it!"
-- The Firesign Theatre
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
