On Thu, 2007-08-02 at 10:18 +0100, Andy Green wrote: > Somebody in the thread at some point said: > > >> Because of this NM can't create ad-hoc networks because it does it while > >> the device is up. > >> Any ideas? > > > > Fix NM? > > It can easily try it one way and if it fails, try the other. > > NM has some other things that needed fixing last time I looked at it... > it thought it knew better than I did if a wireless interface was in > Monitor mode that I "really wanted it" to be in Managed. Monitor mode is inconsistently implemented across drivers. If the device is in monitor mode, I assume you're not actually using it for any traffic or anything? NM has to set the mode on the device (adhoc or infra) before doing any connection stuff, and NM also used to set the mode to infra before scanning, because older cards don't deliver good scan results when in adhoc mode. Plus, NM scans periodically and keeps the card up during that time. It's only with mac80211 and prism54 that you really have to take the card down to change from infra -> adhoc or back. That's a _new_ requirement, even if it is a valid one. I think it's fine, but expecting existing NM to magically support that is sorta wrong. Doesn't mean we shouldn't change it though. For example, if the device isn't being used, NM is still scanning on the device, but the device doesn't actually need to (a) be up or (b) be put into infra mode between the periodic scans. dan - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
