Return-path: Received: from charlotte.tuxdriver.com ([70.61.120.58]:49594 "EHLO smtp.tuxdriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754966AbZLHOaK (ORCPT ); Tue, 8 Dec 2009 09:30:10 -0500 Date: Tue, 8 Dec 2009 09:29:40 -0500 From: "John W. Linville" To: Stephen Hemminger Cc: "Luis R. Rodriguez" , linux-wireless@vger.kernel.org, linux-hotplug@vger.kernel.org Subject: Re: wireless device and udev Message-ID: <20091208142940.GB15172@tuxdriver.com> References: <20091207172616.7470ed2b@nehalam> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20091207172616.7470ed2b@nehalam> Sender: linux-wireless-owner@vger.kernel.org List-ID: 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.