Return-path: Received: from py-out-1112.google.com ([64.233.166.176]:9031 "EHLO py-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757282AbXLGTVH (ORCPT ); Fri, 7 Dec 2007 14:21:07 -0500 Received: by py-out-1112.google.com with SMTP id u77so1708974pyb for ; Fri, 07 Dec 2007 11:21:06 -0800 (PST) Message-ID: <8e6f94720712071121n234d9d23idaaf49d76b2fe227@mail.gmail.com> (sfid-20071207_192111_569909_7AC5FCEA) Date: Fri, 7 Dec 2007 14:21:00 -0500 From: "Will Dyson" To: "Luis R. Rodriguez" Subject: Re: What's wrong if wlan0 device is not reacting? Cc: lynx.abraxas@freenet.de, linux-wireless@vger.kernel.org, "Dan Williams" , "Michael Wu" , "Andrea Merello" In-Reply-To: <43e72e890712061714i3427f558p9b94390955b0a817@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <20071206170858.GA2008@drago> <8e6f94720712061052p105a9e82v290afb011765ba04@mail.gmail.com> <20071206214807.GB1811@drago> <43e72e890712061714i3427f558p9b94390955b0a817@mail.gmail.com> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Dec 6, 2007 8:14 PM, Luis R. Rodriguez wrote: > Using compat-wireless-2.6 I get my wmaster0 as 'eth3' actually and I > think that's making network manager angry (my wlan0 is actually > wlan0_rename too). You've got an old set of udev network device rename rules. The master interface has the same MAC address as the real interface, and it is created first. So the old udev rule (which only keys on the MAC address) renames it to eth3. Then the real interface is created, udev sees that it has already renamed an interface with that MAC and gives it the wlan0_rename name. If you delete the generated rename rules, it should create the correct ones on the next boot. Alternately, you could add a ATTRS{type}="1" selector to your current rule. Debian puts these autogenerated udev rules in /etc/udev/rules.d/z25_persistent-net.rules. Other distributions may vary slightly. -- Will Dyson