From: "Jouni Malinen" <jkm@devicescape•com>
To: Johannes Berg <johannes@sipsolutions•net>
Cc: Jiri Benc <jbenc@suse•cz>, netdev@vger•kernel.org
Subject: Re: wlan#ap seems bogus
Date: Mon, 14 Aug 2006 08:58:47 -0700 [thread overview]
Message-ID: <20060814155847.GC1196@instant802.com> (raw)
In-Reply-To: <44E032CA.4040107@sipsolutions.net>
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' instead. However, I think
> it's hard-coded existence is bogus.
>
> 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 display
> purposes...
Isn't this already done? I don't remember what happened with client mode
case, but at least hostapd is requesting the management interface
dynamically at startup time.
> Also, like I mentioned previously, the device naming can be changed by the
> user and there's no guarantee that wlan0ap corresponds to wmaster0. Etc. But
> if wpa_supplicant simply created the device itself, it could give it any
> name, say wlan0_mgt (if it was controlling wlan0), but if that name is
> already taken it simply appends a number or something until it hits a device
> name that's still free (or gives up after 100 tries or so...) :)
Same here.. hostapd gets the ifindex from kernel and doesn't care about
the name.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2006-08-14 15:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 8:07 [wireless] bunch of questions and notes on d80211 Johannes Berg
2006-08-14 8:10 ` bcm43xx for d80211 softirq loop Johannes Berg
[not found] ` <44E0300D.1000402-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2006-08-14 8:21 ` Johannes Berg
2006-08-14 13:27 ` Michael Buesch
2006-08-14 8:12 ` [d80211 rfc] link master interface from wiphy Johannes Berg
2006-08-14 12:01 ` Dan Williams
2006-08-16 17:05 ` Jiri Benc
2006-08-17 7:18 ` Johannes Berg
2006-08-14 8:13 ` [PATCH] d80211: fix some 0 vs. NULL comparisons Johannes Berg
2006-08-14 13:20 ` Johannes Berg
2006-08-14 15:48 ` Jouni Malinen
2006-08-14 8:15 ` [PATCH] d80211: get rid of the WME bitfield Johannes Berg
2006-08-14 16:12 ` Jouni Malinen
2006-08-15 7:11 ` Johannes Berg
2006-08-14 8:16 ` ieee80211_japan_5ghz / firmware etc.?? Johannes Berg
2006-08-14 8:16 ` ieee80211_set_encryption Johannes Berg
2006-08-14 15:53 ` ieee80211_set_encryption Jouni Malinen
2006-08-14 8:18 ` network manager confused with bcm43xx-d80211? Johannes Berg
2006-08-14 11:46 ` Dan Williams
2006-08-14 12:28 ` Johannes Berg
2006-08-14 12:48 ` Larry Finger
2006-08-14 12:54 ` Johannes Berg
2006-08-14 8:19 ` d80211 and sta_aid for AP functionality Johannes Berg
2006-08-17 18:21 ` Jiri Benc
2006-08-14 8:22 ` wlan#ap seems bogus Johannes Berg
2006-08-14 14:04 ` Johannes Berg
2006-08-14 18:53 ` Simon Barber
2006-08-15 7:22 ` Johannes Berg
2006-08-14 15:58 ` Jouni Malinen [this message]
2006-08-14 16:04 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060814155847.GC1196@instant802.com \
--to=jkm@devicescape$(echo .)com \
--cc=jbenc@suse$(echo .)cz \
--cc=johannes@sipsolutions$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox