From: "John W. Linville" <linville@tuxdriver.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-wireless@vger.kernel.org, linux-hotplug@vger.kernel.org
Subject: Re: wireless device and udev
Date: Tue, 08 Dec 2009 14:29:40 +0000 [thread overview]
Message-ID: <20091208142940.GB15172@tuxdriver.com> (raw)
In-Reply-To: <20091207172616.7470ed2b@nehalam>
On Mon, Dec 07, 2009 at 05:26:16PM -0800, Stephen Hemminger wrote:
> The default udev persistent network rules based on hardware mac id doesn't
> work well when multiple SSID's are created on an access-point. The command
> iw phy phy0 interface add wlan1 type managed
>
> is supposed to make a device name wlan1, but udev sees that it has the same
> mac address as wlan0 and gets confused leaving the device named wlan1_rename
>
> It looks like wlanX is breaking assumptions of existing udev persistent network
> device name generation rules. Perhaps there needs to be special case for wlanX
> devices?
Yes, probably so. But what would it be? Factoring-in SSID is clearly
not right for the usual case (i.e. one interface on a mobile device).
I'm not sure what else one could use as a key.
What does udev do for bridge, bond, or vlan devices? Don't those
share MAC addresses with the underlying physical device?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next parent reply other threads:[~2009-12-08 14:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091207172616.7470ed2b@nehalam>
2009-12-08 14:29 ` John W. Linville [this message]
2009-12-08 15:24 ` wireless device and udev Marco d'Itri
2009-12-08 18:43 ` Stephen Hemminger
2009-12-08 18:50 ` Luis R. Rodriguez
2009-12-08 18:59 ` Stephen Hemminger
2009-12-08 19:51 ` Luis R. Rodriguez
2009-12-08 20:07 ` Marcel Holtmann
2009-12-08 18:52 ` John W. Linville
2009-12-08 19:29 ` Johannes Berg
2009-12-08 20:05 ` John W. Linville
2009-12-09 3:54 ` Andrey Borzenkov
2009-12-09 8:30 ` Johannes Berg
2009-12-09 15:05 ` John W. Linville
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=20091208142940.GB15172@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=shemminger@vyatta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).