wireless: recap of current issues (compatibility)

[John W. Linville]

Compatibility
=============

The netlink configuration mechanism needs compatibility code to
translate wireless extension ioctls into netlink transactions.

We need to be an 802.11 stack (i.e. drivers need to handle 802.11
frames).  Ethernet emulation is bound to paint us into a corner
eventually (if it hasn't already).

We need an ethernet<->802.11 translational bridging interface for
compatibility, and to enable 802.1 bridging with ethernet.  This could
be a configuration setting for a wlan interface.  It might be limited
to wlan interfaces in station (or WDS) mode?

802.11 framing may break older protocols (e.g. DECnet).  I don't
see this as a big problem, as I imagine such installations aren't
rolling-out lots of WiFi...if I'm wrong, will the translational
bridging code resolve this issue?

Should a default wlan device be created at WiPHY init?  Should it
enable translational bridging?  I'm inclined against this, but is it
worthwhile for compatibility?  Could/should this be a configuration
option for the stack?

How about if WiPHY initialization triggered a netlink broadcast?
Then a daemon could monitor those broadcasts and create whatever wlan
devices (ethernet emulation, rfmon, none at all) that the daemon was
configured to create.  How would this effect modprobe behaviour?
-- 
John W. Linville
linville@xxxxxxxxxxxxx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/