Johannes Berg wrote: > Fair enough. Then the question however remains whether wireless should > try to do all things it needs in one or try leveraging multiple things > from other places. Thoughts? 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. 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. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
