Stefan Schweizer wrote: > Andy Green wrote: >> ifconfig wlan0 down >> >> Then after changing the mode, bring it up and set the channel. > > why can it not do that automatically when issueing the mode monitor command? > > Seems usability has not yet reached wireless configuration - where it is imo > much needed. It's really a userspace issue... libpcap could be given the primitives so tcpdump or whatever can set the mode and bring the interface up. On the same subject, why is scanning done by a separate app (iwlist) from iwconfig? Why is scanning specially modal in the stack (or even worse the device firmware) when there are enough primitives lying around to do it from userspace? I guess the answer is it got started like that and now people are using it that way changing is harder. BTW apropos of nothing let me note that the try #13 injection patches apply to current wireless-dev with only a single fuzz, and are available right here: [PATCH Try#lucky13 1/3] mac80211: Monitor mode radiotap injection docs http://www.spinics.net/lists/linux-wireless/msg03055.html [PATCH Try#lucky13 2/3] cfg80211: Radiotap parser http://www.spinics.net/lists/linux-wireless/msg03056.html [PATCH Try#lucky13 3/3] mac80211: Monitor mode radiotap-based packet injection http://www.spinics.net/lists/linux-wireless/msg03054.html -Andy - 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
