[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: network interfaces not persistent on nslu2/arm



Am Mittwoch, 27. August 2008 schrieb Bob Cox:
> On Tue, Aug 26, 2008 at 21:18:25 +0200, Rainer Dorsch (rdorsch@web.de) 
wrote:
> > Hello,
> >
> > I have an usb ethernet adapter in my nslu2. I wanted to keep the network
> > interfaces persistent with udev:
> >
> > nslu2:~# cat /etc/udev/rules.d/z25_persistent-net.rules
> > # This file was automatically generated by the /lib/udev/write_net_rules
> > # program, probably run by the persistent-net-generator.rules rules file.
> > #
> > # You can modify it, as long as you keep each rule on a single line.
> >
> > # Unknown net device (/class/net/eth0) (ixp400_eth)
> > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:18:39:28:f2:a9",
> > NAME="eth0"
> >
> > # USB device 050d:0121 (pegasus)
> > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:05:1b:00:5a:39",
> > NAME="eth1"
> >
> >
> > This does not work for me:
>
> [snip]
>
> > Does anybody have an idea what could go wrong here?
>
> Not sure if this helps, but the ifrename package may be worth
> investigating.
>
> http://packages.debian.org/etch/ifrename
>
> An article picked at random from a google search:
> http://www.enterprisenetworkingplanet.com/netos/article.php/3586546
>

Bob,

thanks for the links. I was under the impression that ifrename is not needed 
when I have udev.

That is also how I read

http://www.debian-administration.org/articles/502

"There are several different ways of managing the naming of devices if you're 
using a dynamic /dev system such as udev or hotplug - but the simplest system 
which works for most cases is provided by the ifrename package."

Never mind, if udev does not work, I will use ifrename as a fallback :-)

Rainer

-- 
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07157-734133
email: rdorsch@web.de
jabber: rdorsch@jabber.org
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F  8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/


Reply to: