Simon Barber wrote:
The purpose of the wlap0ap or wlap0mgmt interface is to communicate
between hostapd/wpa_supplicant and the kernel. What travels over this
interface is not quite pure 802.11 management frames - there is some
meta-data with each frame, and a few special case messages. E.G.
trans
annes Berg
Sent: Monday, August 14, 2006 7:04 AM
To: netdev@vger.kernel.org
Cc: Jouni Malinen; Jiri Benc
Subject: Re: wlan#ap seems bogus
Johannes Berg wrote:
> Hence, I think it ought to be named 'wlan#mgmt' instead.
I see it's actually called wmgmt# now. Sorry. The rest of this mail
s
Jouni Malinen wrote:
How about we just add a new interface mode called MGT_MONITOR and
wpa_supplicant simply creates a new device via the regular sysfs mechanism,
and then sets that MGT_MONITOR mode via the relevant WEXT ioctl? iwconfig
doesn't even need to be taught about this mode except for di
On Mon, Aug 14, 2006 at 10:22:34AM +0200, Johannes Berg wrote:
> As far as I understand the entire point of the wlan#ap interface is to
> receive all management relevant management frames. (If that's wrong, reply
> now and don't read the rest)
>
> Hence, I think it ought to be named 'wlan#mgmt' in
Johannes Berg wrote:
Hence, I think it ought to be named 'wlan#mgmt' instead.
I see it's actually called wmgmt# now. Sorry. The rest of this mail
still holds though.
johannes
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
Mor
As far as I understand the entire point of the wlan#ap interface is to
receive all management relevant management frames. (If that's wrong, reply
now and don't read the rest)
Hence, I think it ought to be named 'wlan#mgmt' instead. However, I think
it's hard-coded existence is bogus.
How about w
