Slightly OT: I have posted getstats.sh on the Homenet wiki. This is an adaptation of a script that I created as a troubleshooting tool for OpenWrt. The script collects a standard set of info and outputs it to a single file for easy review. You can also pass in additional commands as arguments on the command line.
I added the commands mentioned in this thread to make it more useful for debugging hnetd problems. It's at: http://www.homewrt.org/doku.php?id=getstats_script - I would be pleased to include any additional commands that might be helpful. Rich > On Aug 5, 2016, at 7:37 AM, Juliusz Chroboczek > <[email protected]> wrote: > >> Thanks for the suggestion, but no change. > > It's difficult to debug remotely, since you're not giving the relevant > information. (Which interfaces are the routers connected over? How are > they configured?) > > Did you install the "ip" OpenWRT package? (Check with "opkg status ip".) > We've seen silent failures when busybox ip was being used with hnetd. > > If that's not the issue, I suggest checking whether the routing table is > sane and whether babeld and the kernel agree on the routing table > (ip route show, killall -USR1 babeld and check /var/log/babeld.log). > I also suggest checking the neighbour cache (ip -6 neigh show). > > -- Juliusz > > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
