[Babel-users] bug in finding the channel on ap-mode connections

[Juliusz Chroboczek]

> Anyway... in ethernet, adhoc or station mode, babel figures out the
> channel number of the interface ok, but on the ap-mode (master) mode,
> it logs stuff like this at startup and periodically thereafter.

It's the kernel answering EINVAL to SIOCGIWFREQ.  Is there a different API
that would work better?

Babeld will do the reasonable thing, which is to assume worst case
behaviour for this interface -- it interferes with all other wireless
interfaces.

> I don't know what happens on bridged interfaces.

The same worst-case assumption.  Only solution is to unbridge.

-- Juliusz