Networking Follies

Charles Curley charlescurley at charlescurley.com
Sun Jul 9 14:19:08 UTC 2006


On Sun, Jul 09, 2006 at 06:23:06AM -0400, Garry T. Williams wrote:
> On Saturday 08 July 2006 22:51, Charles Curley wrote:
> > On Sat, Jul 08, 2006 at 07:00:01PM -0400, Garry T. Williams wrote:
> 
> [snip]
> 
> > > You want to install the initscripts update.  It should eliminate
> > > the devXXXX interfaces.
> > 
> > I did so, and rebooted. The system came up and ran the network
> > initscript. I got a connection on eth0. I did not check to see if
> > eth1 was set up correctly.
> > 
> > I then turn on NM. It broke my connection. eth1 had been replaced
> > with a mutant device name:
> > 
> > dev1804289383 Link encap:Ethernet  HWaddr 00:10:C6:C0:AA:26
> >           UP 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)
> 
> Bummer.  All I can say is that these were eliminated for me after I
> installed an update to initscripts.
> 
> [snip]
> 
> > The initscripts update did not eliminate the mutant device names. It
> > did, however, eliminate my ethernet device. Imagine my ecstasy.


I do have /etc/iftab:

[root at dragon ~]# cat /etc/iftab
# Assign if devices. man iftab

eth0      mac 00:13:CE:70:53:C8
eth1      mac 00:10:C6:C0:AA:26

Last night, I shut the beastied down, rather than suspend it. This
morning I fired it up. I noticed that the init scripts complained of
not finding the e100 device. So:

  [ccurley at dragon ~]$ su -
  Password:
  Today is Setting Orange, the 44th of Confusion, 3172. Keep the Lasagna flying!
  [root at dragon ~]# ifconfig
  eth0      Link encap:Ethernet  HWaddr 00:13:CE:70:53:C8
			inet addr:192.168.1.4  Bcast:192.168.1.255  Mask:255.255.255.0
			inet6 addr: fe80::213:ceff:fe70:53c8/64 Scope:Link
			UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
			RX packets:327 errors:0 dropped:0 overruns:0 frame:0
			TX packets:294 errors:0 dropped:0 overruns:0 carrier:0
			collisions:0 txqueuelen:1000
			RX bytes:38529 (37.6 KiB)  TX bytes:24129 (23.5 KiB)
			Interrupt:11 Memory:c0204000-c0204fff

  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:313 errors:0 dropped:0 overruns:0 frame:0
			TX packets:313 errors:0 dropped:0 overruns:0 carrier:0
			collisions:0 txqueuelen:0
			RX bytes:29125 (28.4 KiB)  TX bytes:29125 (28.4 KiB)

  [root at dragon ~]# lsmod | grep e100
  e100                   35909  0
  mii                     5697  1 e100
  [root at dragon ~]# rmmod e100
  [root at dragon ~]# modprobe e100
  [root at dragon ~]# ifconfig
  eth0      Link encap:Ethernet  HWaddr 00:13:CE:70:53:C8
			inet addr:192.168.1.4  Bcast:192.168.1.255  Mask:255.255.255.0
			inet6 addr: fe80::213:ceff:fe70:53c8/64 Scope:Link
			UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
			RX packets:358 errors:0 dropped:0 overruns:0 frame:0
			TX packets:316 errors:0 dropped:0 overruns:0 carrier:0
			collisions:0 txqueuelen:1000
			RX bytes:41750 (40.7 KiB)  TX bytes:28552 (27.8 KiB)
			Interrupt:11 Memory:c0204000-c0204fff

  eth1      Link encap:Ethernet  HWaddr 00:10:C6:C0:AA:26
			UP 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)

  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:323 errors:0 dropped:0 overruns:0 frame:0
			TX packets:323 errors:0 dropped:0 overruns:0 carrier:0
			collisions:0 txqueuelen:0
			RX bytes:29448 (28.7 KiB)  TX bytes:29448 (28.7 KiB)

In /var/log/messages, I see two sets of messages for eth1:

Jul  9 07:18:44 dragon kernel: e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
Jul  9 07:18:44 dragon kernel: e100: Copyright(c) 1999-2005 Intel Corporation
Jul  9 07:18:45 dragon kernel: e100: eth0: e100_probe: addr 0xc0205000, irq 11, MAC addr 00:10:C6:C0:AA:26

Jul  9 07:20:48 dragon kernel: e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
Jul  9 07:20:48 dragon kernel: e100: Copyright(c) 1999-2005 Intel Corporation
Jul  9 07:20:48 dragon kernel: e100: eth1: e100_probe: addr 0xc0205000, irq 11, MAC addr 00:10:C6:C0:AA:26
Jul  9 07:20:49 dragon kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready

I see that the second initializtion has the ADDRCONF(NETDEV_UP)
line. the first one does not. I searched for it.

I begin to suspect an initscripts bug.

> 
> Perhaps starting over with system-config-network would sort this out.

I copied the existing setup to new directories to preserve the old
setup:

[root at dragon sysconfig]# cp -rp networking/ networking.old
[root at dragon sysconfig]# cp -rp network-scripts/ network-scripts.old

Using system-config-network, I deleted the two devices and added them
back again. After much diffing, I was able to get the setup for the
wireless device back to where it will work. I tested using "service
network stop" and "service network start" rather than rebooting. Wehn
I finally got both devices working correctly, I ran a diff:

  [root at dragon sysconfig]# diff -r networking/ networking.old
  diff -r networking/devices/ifcfg-eth1 networking.old/devices/ifcfg-eth1
  10d9
  < HWADDR=00:10:c6:c0:aa:26
  diff -r networking/profiles/default/ifcfg-eth1 networking.old/profiles/default/ifcfg-eth1
  10d9
  < HWADDR=00:10:c6:c0:aa:26
  [root at dragon sysconfig]# diff -r network-scripts network-scripts.old
  diff -r network-scripts/ifcfg-eth1 network-scripts.old/ifcfg-eth1
  10d9
  < HWADDR=00:10:c6:c0:aa:26

And that suggests a place to look in the code, but I'm out of time for
hacking this morning. And I should test this by rebooting before I do
any hacking.

-- 

Charles Curley                  /"\    ASCII Ribbon Campaign
Looking for fine software       \ /    Respect for open standards
and/or writing?                  X     No HTML/RTF in email
http://www.charlescurley.com    / \    No M$ Word docs in email

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20060709/5da3c8a8/attachment-0002.bin 


More information about the users mailing list