I know toke's probably buried, and my message was long. Anyway, this is what happens with my current bird config (prancer) which is attached. For some reason it picks up the .2 route (which I'm not exporting from that babel box), and redistributes it as its own. It doesn't from various other boxes.
dancer is the nuc dancer:~$ ip route default via 172.22.0.2 dev eno1 50.197.142.144/29 via 172.22.0.1 dev eno1 proto babel onlink 169.254.0.0/16 dev eno1 scope link metric 1000 172.20.0.0/14 via 172.22.0.1 dev eno1 proto babel onlink 172.22.0.0/24 dev eno1 scope link 172.22.0.2 via 172.22.0.85 dev eno1 proto babel onlink 172.22.0.172 via 172.22.0.172 dev eno1 proto babel onlink 172.22.148.0/22 via 172.22.0.85 dev eno1 proto babel onlink 172.22.192.0/22 via 172.22.0.85 dev eno1 proto babel onlink 172.22.220.0/22 via 172.22.0.91 dev eno1 proto babel onlink 172.23.252.2 via 172.22.0.85 dev eno1 proto babel onlink 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.2 The extra hop would be sorta ok, except when I kill bird it sends that key box unreachable. default via 172.22.0.2 dev eno1 # static route in self defense from my carnage 50.197.142.144/29 via 172.22.0.1 dev eno1 proto babel onlink 169.254.0.0/16 dev eno1 scope link metric 1000 # ubuntu 16 bug when dhcpd is timing out 172.20.0.0/14 via 172.22.0.1 dev eno1 proto babel onlink # campus gw 172.22.0.0/24 dev eno1 scope link unreachable 172.22.0.2 proto babel metric 4294967295 # main gw - not ok 172.22.0.172 via 172.22.0.172 dev eno1 proto babel onlink unreachable 172.22.148.0/22 proto babel metric 4294967295 # ok, bird's network unreachable 172.22.192.0/22 proto babel metric 4294967295 # ok, bird's network 172.22.220.0/22 via 172.22.0.91 dev eno1 proto babel onlink unreachable 172.23.252.2 proto babel metric 4294967295 # my main gateway -not ok 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.2 after it times out, life goes back to normal default via 172.22.0.2 dev eno1 50.197.142.144/29 via 172.22.0.1 dev eno1 proto babel onlink 169.254.0.0/16 dev eno1 scope link metric 1000 172.20.0.0/14 via 172.22.0.1 dev eno1 proto babel onlink 172.22.0.0/24 dev eno1 scope link 172.22.0.172 via 172.22.0.172 dev eno1 proto babel onlink 172.22.220.0/22 via 172.22.0.91 dev eno1 proto babel onlink 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.2 * As for bird which is running on a weak atom box... peaked at about 32k routes. Limit? if I fire it up during all this carnage, weird things happen. Whether that's bird doing something weird, messing with metrics, or the cost of a route dump, or what, dunno... I had about 1000 seconds left before the lab network is usuable again, which I'm using to write this email. :) ** gotta fix this: Received prefix with no router id. Couldn't parse packet (8, 12) from fe80::230:18ff:fec9:de9c on eno1. ** the carnage of retracting this many routes was "interesting" ** Probably most importantly... I get "permanent" wierdness (metrics? misparsing something?), like for example, on my 172.22.0.0 network... I end up with a route announced and stuck to the bird box here: 172.22.0.2 via 172.22.0.85 dev eno1 proto babel onlink and I should probably filter out any announcements of in 172.22.0.0/24 ge 24 universally, but! .2 has redistribute local deny and is not running the nlogn branch with that bug in it, and this does not happen with babeld exclusively on the network. So I think this is a genuine bird bug. -- Dave Täht CTO, TekLibre, LLC http://www.teklibre.com Tel: 1-831-205-9740
bird.conf
Description: Binary data
_______________________________________________ Babel-users mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/babel-users
