Sometimes everything can be solved with a reboot. What had happened here, was that the bird box, had a stuck "babel" protocol route, left over from one of the many crashes this week, which it then decided to redistribute as if I'd intended that to be the case.
A reboot later.... without that... d@spaceheater:~/git/fixes/nlogn-uthash-merge$ ip route default via 172.22.0.2 dev enp6s0 50.197.142.144/29 via 172.22.0.1 dev enp6s0 proto babel onlink 172.20.0.0/14 via 172.22.0.1 dev enp6s0 proto babel onlink 172.22.0.0/24 dev enp6s0 proto kernel scope link src 172.22.0.172 172.22.148.0/22 via 172.22.0.85 dev enp6s0 proto babel onlink 172.22.192.0/22 via 172.22.0.85 dev enp6s0 proto babel onlink 172.22.220.0/22 via 172.22.0.91 dev enp6s0 proto babel onlink 192.168.0.0/24 via 172.22.0.150 dev enp6s0 proto babel onlink So I retract this portion of the bug report. The parsing error is annoying and I'll poke into what issues it's causing after sticking some more boxes on the other side of it. I do check that the ipv6 routes are correct also, they are looking good, not huge on publishing those. Aside from that I don't understand the bird's filter language as well as I do babel's but, well, all up testing now has all the bugs found thus far fixed in the rfc branch, interop looks like a go! anyone for FRR? _______________________________________________ Babel-users mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/babel-users
