Re: [Babel-users] Debugging unreachable routes - IPv6 as next hop?
>> Using Lede 17.01 rc 2 and OpenWRT CC I get some unreachable routes. >> I'm somewhat puzzled. The setup contains 2 nodes sharing a wireless >> ad-hoc link. > .. this happened due to a poor wifi link. Good. Babel culls asymmetric links, since it's impossible to establish reliable communication without reliable feedback. Everything is working as designed. -- Juliusz ___ Babel-users mailing list Babel-users@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
Re: [Babel-users] Debugging unreachable routes - IPv6 as next hop?
> Sun Feb 19 17:15:45 2017 daemon.info babeld[1171]: Neighbour > fe80::227:22ff:fe2e:4153 dev wlan0 reach rxcost 256 txcost 65535 > rtt 0.000 rttcost 0 chan 1. It looks like an asymmetric link -- the local node hears neighbour 4153, but 4153 doesn't hear the local node. If you manage to reproduce that, could you please also show the log on the node that advertises the infinite txcost? (Note that this can happen if for some reason you're running two instances of babeld on the same node -- the two instances stomp on each other's packets, and get confused. Since OpenWRT/LEDE no longer uses a pidfile, there is no mechanism in babeld that prevent that from happening. Please check with ps.) -- Juliusz ___ Babel-users mailing list Babel-users@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
Re: [Babel-users] Debugging unreachable routes - IPv6 as next hop?
I have been chasing a similar set of bugs for months now. Routes would be unreachable for no reason I could see, updates to the kernel would fail[1]. How big is the total route table? Does it stay unreachable? Can you try reverting to babeld-1.7.1 for lede? ... I finally got heads down on it last week and I have a slew of debugging patches that I need to clean up for 1.8... and then I need to do a build for lede - but I haven't got around to it yet. Nor have I tried 1.7.x - I was trying to debug something elsewhere In particular I found that network manager was stomping on babel in my network. My test case is unfortunately not as simple as yours. But I was originally seeing some sort of interaction with odhcpd also. [1] Lastly there was a major bug in the wifi ATF fairness code for ath9k stomped last week, which could scribble on memory just about anywhere, and some fixes for odhcpd, and ubus landed also. ___ Babel-users mailing list Babel-users@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
