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

[Dave Taht]

CeroWrt runs babel on ad-hoc, ethernet, and ap-mode connections
all at the same time by default.

We name interfaces a bit weirdly to make for easier iptables rules:
Ethernet is ge00 and se00 (wan, and lan in openwrt parlance), ap-mode
is usually on gw00, gw10, sw00, and sw10,
and ad-hoc is gw01 and gw11 (the first digit indicates the radio number,
the second the interface number, the first letter "[g]uest or
[s]ecure", second letter "[w]ireless or [e]thernet". This makes
writing a rule for "guests" or "secure" one pattern match instead of 4
rules.

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.

Couldn't determine channel of interface gw00: Invalid argument.
Couldn't determine channel of interface gw00: Invalid argument.
Couldn't determine channel of interface gw10: Invalid argument.
Couldn't determine channel of interface gw10: Invalid argument.
Couldn't determine channel of interface sw00: Invalid argument.
Couldn't determine channel of interface sw00: Invalid argument.
kernel_route(ADD): File exists
Couldn't determine channel of interface gw00: Invalid argument.
Couldn't determine channel of interface gw10: Invalid argument.
Couldn't determine channel of interface sw00: Invalid argument.
Couldn't determine channel of interface gw00: Invalid argument.
Couldn't determine channel of interface gw10: Invalid argument.
Couldn't determine channel of interface sw00: Invalid argument.
Couldn't determine channel of interface gw00: Invalid argument.
Couldn't determine channel of interface gw10: Invalid argument.
Couldn't determine channel of interface sw00: Invalid argument.
Couldn't determine channel of interface gw00: Invalid argument.
Couldn't determine channel of interface gw10: Invalid argument.
Couldn't determine channel of interface sw00: Invalid argument.
Couldn't determine channel of interface gw00: Invalid argument.
Couldn't determine channel of interface gw10: Invalid argument.
Couldn't determine channel of interface sw00: Invalid argument.

I don't know what happens on bridged interfaces. I'm not even sure
what it should do on a bridged interface, as most commonly what we see
are ethernet bridged to both 2.4 and 5ghz radios.


-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article