On Tue, 2007-04-10 at 14:05 +0200, Patrick McHardy wrote: > > I know too little about wireless to judge really this. My opinion is > that if it is possible to add and configure an interface (even if > only for simple cases) without knowledge about driver internals by > setting a few parameters, it would probably make sense to use > RTM_NEWLINK as well. If a userspace daemon or complex knowledge of > driver internals is needed, it probably should stay seperated. It still is though we're moving towards the userspace daemon thing. > So simply put: if I can implement support for > "ip wireless add dev wlan0 mode managed essid ... key ..." > in less than 100 lines and get a working connection afterwards, it > seems worth it. For completely open networks (no "key ...") or just WEP (static key) it could probably be done, but I don't see how right now. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
