>> Babeld is already monitoring netlink messages (see funciton filter_netlink >> in kernel_netlink), but it looks like this mechanism is not working in >> your particular case. I'll try to reproduce the issue, but I don't own >> a Raspberry Pi.
> Maybe the typical problem with IFF_UP and IFF_RUNNING? Some interfaces > use both, some use only IFF_UP. Babeld uses IFF_UP by default, IFF_RUNNING if run with -l. I should make it a per-interface option. Dave, what happens if you run *without* -l? Does babeld react immediately to "ifconfig down"? -- Juliusz _______________________________________________ Babel-users mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
