Am Mittwoch 11 Januar 2006 15:49 schrieb Jiri Benc: > - There should be only as few net_devices as needed. I. e. when the card > acts as a client to one AP, only one device is present. > - The type of a device (AP, client, WDS link, monitor, etc.) should be > specified in the usual way (by iwconfig mode or whatever will eventually > replace it). > - When you need a new device (e. g. because you want to connect to another > AP at the same time, or you want to add a new WDS link), you just invoke > some command and a new device will appear. Then you can configure the new > device in the usual way (iwconfig mode, etc.)
That proposal sounds fine to me, it gives users least headaches. > There are two problems regarding native 802.11 devices: I see a third problem - the in kernel protocols. Just do a quick fgrep -r ARPHRD_ over linux/net and you'll see what I mean. While moving away from the ethernet emulation, we have to touch a bunch of protocols, even ones we possibly cannot test, e.g. decnet. Even though I don't like the ethernet emulation hack, I'm not sure if it is worth the pain just to be able to show up as a real 802.11 device. Stefan - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
