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

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

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