Linux Archive

Linux Archive (http://www.linux-archive.org/)
-   Debian User (http://www.linux-archive.org/debian-user/)
-   -   renamed network interface eth0 to eth1 (http://www.linux-archive.org/debian-user/430549-renamed-network-interface-eth0-eth1.html)

Hugo Vanwoerkom 09-22-2010 09:11 PM

renamed network interface eth0 to eth1
 
Hi,

I couldn't figure out why the network wouldn't come up, untill I saw this:

hugo@debian:~$ dmesg | grep -i eth
[ 1.181349] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
[ 1.229553] 8139too Fast Ethernet driver 0.9.28
[ 1.231041] eth0: RealTek RTL8139 at 0x3000, 00:0a:e4:eb:04:59, IRQ 20
[ 9.727658] udev: renamed network interface eth0 to eth1
[ 21.532930] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
[ 32.464023] eth1: no IPv6 routers present

Why would udev rename the interface?

Hugo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: i7drdr$408$1@dough.gmane.org">http://lists.debian.org/i7drdr$408$1@dough.gmane.org

James Zuelow 09-22-2010 09:17 PM

renamed network interface eth0 to eth1
 
----Original Message----
From: Hugo Vanwoerkom [mailto:hvw59601@care2.com]
Sent: Wednesday, September 22, 2010 1:11 PM
To: debian-user@lists.debian.org
Subject: renamed network interface eth0 to eth1

> Hi,
>
> I couldn't figure out why the network wouldn't come up, untill I saw
> this:
>
> hugo@debian:~$ dmesg | grep -i eth
> [ 1.181349] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
> [ 1.229553] 8139too Fast Ethernet driver 0.9.28
> [ 1.231041] eth0: RealTek RTL8139 at 0x3000, 00:0a:e4:eb:04:59,
> IRQ 20 [ 9.727658] udev: renamed network interface eth0 to eth1
> [ 21.532930] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
> [ 32.464023] eth1: no IPv6 routers present
>
> Why would udev rename the interface?
>
> Hugo

It will do that if it thinks another interface should be eth0. Say you replaced a NIC or similar.

What does /etc/udev/rules.d/70-persistent-net.rules say?

James Z

--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4A09477D575C2C4B86497161427DD94C15B0D1F8AF@city-exchange07">http://lists.debian.org/4A09477D575C2C4B86497161427DD94C15B0D1F8AF@city-exchange07

Stephen Powell 09-22-2010 09:25 PM

renamed network interface eth0 to eth1
 
On Wed, 22 Sep 2010 17:11:22 -0400 (EDT), Hugo Vanwoerkom wrote:
>
> I couldn't figure out why the network wouldn't come up, untill I saw this:
>
> hugo@debian:~$ dmesg | grep -i eth
> [ 1.181349] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
> [ 1.229553] 8139too Fast Ethernet driver 0.9.28
> [ 1.231041] eth0: RealTek RTL8139 at 0x3000, 00:0a:e4:eb:04:59, IRQ 20
> [ 9.727658] udev: renamed network interface eth0 to eth1
> [ 21.532930] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
> [ 32.464023] eth1: no IPv6 routers present
>
> Why would udev rename the interface?

udev tries to keep the correspondence between ethernet device names and
MAC addresses the same. If the MAC address changes, you're likely to
get a device name change to eth1, since it is reserving eth0 for the
original MAC address. The MAC address may change under the following
conditions:

(1) Your network card goes bad, so you replace it with another network
card of the same or a different type.

(2) Your motherboard, which contains a built-in ethernet adapter, goes
bad and you have to replace it.

(3) You make an image backup of your hard disk on one PC, then restore
the image to another identically-configured PC.

(4) You physically move a hard disk from one PC to another.

If you only have one network interface, the quickest way to solve this
problem is to erase (rm) the file /etc/udev/rules.d/70-persistent-net.rules.
Upon reboot, a new one will be created. If you have more than one network
interface (not counting lo), it may be safer to edit the file and
change the MAC address from the old one to the new one.

--
.'`. Stephen Powell
: :' :
`. `'`
`-


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 2082907843.197626.1285190701223.JavaMail.root@md01 .wow.synacor.com">http://lists.debian.org/2082907843.197626.1285190701223.JavaMail.root@md01 .wow.synacor.com

Timo Juhani Lindfors 09-22-2010 09:34 PM

renamed network interface eth0 to eth1
 
Hugo Vanwoerkom <hvw59601@care2.com> writes:
> Why would udev rename the interface?

MAC address was changed. See /etc/udev/rules.d/70-persistent-net.rules


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 84r5glzcmn.fsf@sauna.l.org">http://lists.debian.org/84r5glzcmn.fsf@sauna.l.org

Camaleón 09-22-2010 09:43 PM

renamed network interface eth0 to eth1
 
On Wed, 22 Sep 2010 16:11:22 -0500, Hugo Vanwoerkom wrote:

(...)

> Why would udev rename the interface?

I've seen that behaviour when MAC address "changes".

The change can be triggered by the user (by replacing or adding a card)
or by a bug in the network driver (I remember that some years ago nvidia
nforce network module "forcedeth" was hit by a bug that continuosly
renamed the ethernet device -eth0, eth1, eth2, eth3...- on each reboot).

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2010.09.22.21.43.45@gmail.com">http://lists.debian.org/pan.2010.09.22.21.43.45@gmail.com

Chance Platt 09-22-2010 09:49 PM

renamed network interface eth0 to eth1
 
On Wed, 2010-09-22 at 16:11 -0500, Hugo Vanwoerkom wrote:

> hugo@debian:~$ dmesg | grep -i eth
> [ 1.181349] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
> [ 1.229553] 8139too Fast Ethernet driver 0.9.28
> [ 1.231041] eth0: RealTek RTL8139 at 0x3000, 00:0a:e4:eb:04:59, IRQ 20
> [ 9.727658] udev: renamed network interface eth0 to eth1
> [ 21.532930] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
> [ 32.464023] eth1: no IPv6 routers present
>
> Why would udev rename the interface?

I've experienced this happening when the kernel for whatever reason
reports to udev different identifiers for the network card. This can be
from using a different kernel, a kernel that is changing the interface's
MAC address for some reason, etc.

Check /etc/udev/rules.d/70-persistent-net.rules

Chance


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1285192197.6089.5.camel@localhost">http://lists.debian.org/1285192197.6089.5.camel@localhost

Hugo Vanwoerkom 09-22-2010 10:52 PM

renamed network interface eth0 to eth1
 
James Zuelow wrote:

----Original Message----
From: Hugo Vanwoerkom [mailto:hvw59601@care2.com]
Sent: Wednesday, September 22, 2010 1:11 PM
To: debian-user@lists.debian.org
Subject: renamed network interface eth0 to eth1


Hi,

I couldn't figure out why the network wouldn't come up, untill I saw
this:


hugo@debian:~$ dmesg | grep -i eth
[ 1.181349] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
[ 1.229553] 8139too Fast Ethernet driver 0.9.28
[ 1.231041] eth0: RealTek RTL8139 at 0x3000, 00:0a:e4:eb:04:59,
IRQ 20 [ 9.727658] udev: renamed network interface eth0 to eth1
[ 21.532930] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
[ 32.464023] eth1: no IPv6 routers present

Why would udev rename the interface?

Hugo


It will do that if it thinks another interface should be eth0. Say you replaced a NIC or similar.



But I haven't


What does /etc/udev/rules.d/70-persistent-net.rules say?


# PCI device 0x1106:0x3065 (via-rhine)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:04:61:77:98:dc", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth0"


# PCI device 0x10ec:0x8139 (8139too)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:0a:e4:eb:04:59", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"


# PCI device 0x14e4:0x4318 (b43)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:14:a4:4c:3c:d5", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"









--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: i7e1c2$sao$1@dough.gmane.org">http://lists.debian.org/i7e1c2$sao$1@dough.gmane.org

Hugo Vanwoerkom 09-22-2010 10:55 PM

renamed network interface eth0 to eth1
 
Stephen Powell wrote:

On Wed, 22 Sep 2010 17:11:22 -0400 (EDT), Hugo Vanwoerkom wrote:

I couldn't figure out why the network wouldn't come up, untill I saw this:

hugo@debian:~$ dmesg | grep -i eth
[ 1.181349] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
[ 1.229553] 8139too Fast Ethernet driver 0.9.28
[ 1.231041] eth0: RealTek RTL8139 at 0x3000, 00:0a:e4:eb:04:59, IRQ 20
[ 9.727658] udev: renamed network interface eth0 to eth1
[ 21.532930] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
[ 32.464023] eth1: no IPv6 routers present

Why would udev rename the interface?


udev tries to keep the correspondence between ethernet device names and
MAC addresses the same. If the MAC address changes, you're likely to
get a device name change to eth1, since it is reserving eth0 for the
original MAC address. The MAC address may change under the following
conditions:

(1) Your network card goes bad, so you replace it with another network
card of the same or a different type.

(2) Your motherboard, which contains a built-in ethernet adapter, goes
bad and you have to replace it.

(3) You make an image backup of your hard disk on one PC, then restore
the image to another identically-configured PC.

(4) You physically move a hard disk from one PC to another.

If you only have one network interface, the quickest way to solve this
problem is to erase (rm) the file /etc/udev/rules.d/70-persistent-net.rules.
Upon reboot, a new one will be created. If you have more than one network
interface (not counting lo), it may be safer to edit the file and
change the MAC address from the old one to the new one.



Thanks, very complete explanation. Will do.

Hugo





--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: i7e1gb$sao$2@dough.gmane.org">http://lists.debian.org/i7e1gb$sao$2@dough.gmane.org

Hugo Vanwoerkom 09-23-2010 01:33 PM

renamed network interface eth0 to eth1
 
Hugo Vanwoerkom wrote:

Hi,

I couldn't figure out why the network wouldn't come up, untill I saw this:

hugo@debian:~$ dmesg | grep -i eth
[ 1.181349] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
[ 1.229553] 8139too Fast Ethernet driver 0.9.28
[ 1.231041] eth0: RealTek RTL8139 at 0x3000, 00:0a:e4:eb:04:59, IRQ 20
[ 9.727658] udev: renamed network interface eth0 to eth1
[ 21.532930] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
[ 32.464023] eth1: no IPv6 routers present

Why would udev rename the interface?



Thanks for the helpful answers. Of course the NIC changed, what am I
saying? Acc. to my records this system was generated on 03/10/10 from a
lenny d-i on an 8VTAI mobo. After that it was upgraded repeatedly and
moved around via mondo. Then via another post:
http://lists.debian.org/debian-user/2010/09/msg01677.html
I installed the latest sid debian kernel and booted that on an acer
aspire laptop: changing the NIC and the MAC address.

Hugo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: i7fkvg$uht$1@dough.gmane.org">http://lists.debian.org/i7fkvg$uht$1@dough.gmane.org


All times are GMT. The time now is 03:36 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.