Package: udev
Version: 0.105-4

After replacing NIC broken by thunderstorm, eth has moved from eth0 to eth2.
(It took me close to 1 hour to rectify the situation: not having any
network, because the system does not follow suit.)

udev seems to be the culprit: what was eth0 (single eth) becomes eth2
after change of MAC address.
To be noted:
dmesg still shows eth0
ifconfig shows nothing (no, not eth2)



Details:

This is what I get from dmesg:
...
ACPI: Processor [CPU1] (supports 16 throttling states)
8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
8139cp 0000:00:09.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
8139cp 0000:00:09.0: Try the "8139too" driver instead.
8139too Fast Ethernet driver 0.9.27
ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 18 (level, low) -> IRQ 169
eth0: RealTek RTL8139 at 0xd800, 00:02:44:90:97:27, IRQ 169
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
...
And there is no other eth:
$ dmesg | grep eth
eth0: RealTek RTL8139 at 0xd800, 00:02:44:90:97:27, IRQ 169
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
$

ifconfig says
# ifconfig
lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:12 errors:0 dropped:0 overruns:0 frame:0
         TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:600 (600.0 b)  TX bytes:600 (600.0 b)
#

ifconfig does not 'up' eth0
dhclient eth0 fails

Lucky, I read "man ifconfig" which gave me an idea:
# ifconfig -a
eth2      Link encap:Ethernet  HWaddr 00:02:44:90:97:27
         BROADCAST MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
         Interrupt:169 Base address:0xd800

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:12 errors:0 dropped:0 overruns:0 frame:0
         TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:600 (600.0 b)  TX bytes:600 (600.0 b)

sit0      Link encap:IPv6-in-IPv4
         NOARP  MTU:1480  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
#

And it does work !:
# dhclient eth2
Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
[...]
Listening on LPF/eth2/00:02:44:90:97:27
Sending on   LPF/eth2/00:02:44:90:97:27
Sending on   Socket/fallback/fallback-net
DHCPREQUEST on eth2 to 255.255.255.255 port 67
DHCPACK from 192.168.116.200
bound to 192.168.116.101 -- renewal in 432000 seconds.


There are several flaws in this behaviour:
1. A user swapping out the NIC will usually not be able to reconnect on his own.
2. Logically, there is no reason to move the/any only NIC away from eth0.
3. It is confusing that dmesg recognizes eth0, but udev moves it up to eth2.
       Both ought to be identical, preferably eth0.
4. ifconfig should at least show the 'hidden' NIC.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to