From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HNngH-0007kn-1i for garchives@archives.gentoo.org; Sun, 04 Mar 2007 10:11:05 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l24A8977018722; Sun, 4 Mar 2007 10:08:09 GMT Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l24A885i018701 for ; Sun, 4 Mar 2007 10:08:09 GMT Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HNnc3-0000BZ-Ne for gentoo-amd64@lists.gentoo.org; Sun, 04 Mar 2007 11:06:43 +0100 Received: from ip68-231-13-122.ph.ph.cox.net ([68.231.13.122]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 04 Mar 2007 11:06:43 +0100 Received: from 1i5t5.duncan by ip68-231-13-122.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 04 Mar 2007 11:06:43 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: persistent-net.rules Date: Sun, 4 Mar 2007 10:04:29 +0000 (UTC) Message-ID: References: <200703040045.31686.e0026053@student.tuwien.ac.at> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-13-122.ph.ph.cox.net User-Agent: Pan/0.125 (Potzrebie) Sender: news X-Archives-Salt: 0af6c161-4f5e-4afc-aa40-234e9f74463f X-Archives-Hash: 6bde0dc17975e14638386c241d862a5d Bernhard Auzinger posted 200703040045.31686.e0026053@student.tuwien.ac.at, excerpted below, on Sun, 04 Mar 2007 00:45:31 +0100: > does somebody know how to prevent the persistent-net.rules to be saved > during the shutdown process? > > The background is that I have a network interface with a faulty mac > adress (FF:FF:FF:FF:FF:FF) on a K8N Neo2 (nforce3 ultra). So the kernel > applys a random mac address to the network interface on every boot. At > the shutdown process a entry with the randomly generated mac address > will be written into /etc/udev/rules.d/70-persistent-net.rules. And > that's my problem, because at the next boot another mac address will be > applied to the network interface which does not match the one saved to > persistent-net.rules and udev does not provide an interface eth0. Interesting. I have different hardware, but use the macchanger module to change my MAC at every eth0 up, and don't have the problem here. udev must see the original MAC address on my hardware before macchanger gets to it, and thus set it up correctly. But if it's rewritten @ shutdown, why wouldn't it see the macchanger-randomized one then and thus get it wrong? So... three suggestions. One, see if emerging macchanger and configuring it will cure the problem. Maybe the system expects it if maccchanger is used thus explaining why it works with it here and providing a way to make it work there? Two, consider tweaking the related variables (RC_HOTPLUG, RC_COLDPLUG, RC_PLUG_SERVICES) in /etc/conf.d/rc, and see if you can udev to play nicely that way. (Here, I have RC_PLUG_SERVICES="! nt.eth0", allowing me better control of when it goes up, but it generally works without that, I just like and occasionally need the additional control.) Three, you may have to put a manual mknode somewhere in your scripts. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- gentoo-amd64@gentoo.org mailing list