> Netlink message: [multi] (msg -> "" 0), [multi] (msg -> "found address on > interface eth1(3):
That's the output of ``babeld -d3'', which dumps every single activity that the daemon performs. ``babeld -d2'' should usually be more than enough -- it doesn't dump kernel-side activities (the "Netlink message" lines). If you're running babeld without debugging, you can at any time run sudo kill -USR $(cat /var/run/babeld.pid) which will cause babeld to dump its tables (neighbour table and RIB) on its standard error. Giving output such as My id 02:18:f3:ff:fe:a9:91:4e seqno 35482 Neighbour fe80::e291:f5ff:fecc:7a00 dev wlan0 reach ffbf rxcost 256 txcost 303 chan 6. ... 192.168.4.25/32 metric 0 (exported) ... 87.98.131.2/32 metric 1135 (1113) refmetric 704 id 02:18:f3:ff:fe:21:00:26 seqno 39058 chan (155,55,10) age 6 via wlan0 neigh fe80::218:f3ff:fe98:e534 nexthop 192.168.4.27 Finally, if everything else fails, recent versions of tcpdump and wireshark have support for decoding Babel packets. Run something like $ tcpdump -s 1500 -n -v -i wlan0 port 6696 -- Juliusz _______________________________________________ Babel-users mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
