eth1 getting moved to eth0

[Martin]

On Fri, 2004-09-17 at 09:46, Bill Nottingham wrote:
> Martin (martin at lnuxpwrd.net) said: 
> > if have two network interfaces, eth0 which i want to be
> > the hardwired motherboard device, and eth1 which should
> > be the wireless device.  it has been working fine for some
> > months, but something got corrupted and I just can't get
> > things working again.
> > 
> > the wireless device wants to come up on eth0, despite
> > what's in /etc/modeprobe.conf and /etc/sysconfig/hwconf.
> > 
> > all the files in /etc/sysconfig/networking and network-scripts
> > seems to be correct... that is have eth0 where i expect and
> > eth1 where i expect.
> > 
> > Am I missing some other configuration files that controls which
> > interface gets bound to eth0 or eth1?
> 
> Is HWADDR specified in the correct ifcfg files?

yes, i've tried removing them and then putting them back.

here is additional info that might provide some clues:

from boot.log:

Sep 17 12:37:45 laptop network: Bringing up interface eth0:  succeeded
Sep 17 12:37:45 laptop ifup: cannot change name of eth0 to eth1: Device
or resource busy
Sep 17 12:37:45 laptop ifup:
Sep 17 12:37:45 laptop ifup: interface 'eth0' not found
Sep 17 12:37:45 laptop ifup:
Sep 17 12:37:45 laptop ifup: cannot change name of eth0 to eth1: Device
or resource busy
Sep 17 12:37:45 laptop ifup: cannot change name of eth0 to eth1: Device
or resource busy
Sep 17 12:37:45 laptop ifup:
Sep 17 12:37:45 laptop ifup: interface 'eth0' not found
Sep 17 12:37:48 laptop smartd: smartd startup succeeded
Sep 17 12:37:45 laptop ifup: Device eth1 has different MAC address than
expected, ignoring.
Sep 17 12:37:45 laptop ifup:
Sep 17 12:37:45 laptop ifup: cannot change name of eth0 to eth1: Device
or resource busy
Sep 17 12:37:45 laptop network: Bringing up interface eth1:  failed


is it normal for it to try to switch from eth0 to eth1? 

if i rmmod ipw2100; modprobe ipw2100 then it comes up as eth1.





from hwconf:
-
class: NETWORK
bus: PCI
detached: 0
device: eth0
driver: e100
desc: "Intel Corp.|82801BD PRO/100 VE (MOB) Ethernet Controller"
network.hwaddr: 08:00:46:A3:33:B9
vendorId: 8086
deviceId: 103d
subVendorId: 104d
subDeviceId: 8140
pciType: 1
pcidom:    0
pcibus:  2
pcidev:  8
pcifn:  0
-
class: NETWORK
bus: PCI
detached: 0
device: eth1
driver: ipw2100
desc: "Intel Corp.|PRO/Wireless LAN 2100 3B Mini PCI Adapter"
network.hwaddr: 00:04:23:5C:81:52
vendorId: 8086
deviceId: 1043
subVendorId: 8086
subDeviceId: 2596
pciType: 1
pcidom:    0
pcibus:  2
pcidev:  b
pcifn:  0
-

does the ordering matter in this file?


ifconfig -a output (truncated). nothing listed for eth1:

eth0      Link encap:Ethernet  HWaddr 00:04:23:5C:81:52
          inet addr:10.192.26.88  Bcast:10.192.255.255  Mask:255.255.0.0
          inet6 addr: fe80::204:23ff:fe5c:8152/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6029 errors:0 dropped:0 overruns:0 frame:0
          TX packets:191 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:648109 (632.9 Kb)  TX bytes:17563 (17.1 Kb)
          Interrupt:9 Base address:0x1000 Memory:d0201000-d0201fff

[root at laptop devices]# more ifcfg-eth1
# Intel Corp.|PRO/Wireless LAN 2100 3B Mini PCI Adapter
DEVICE=eth1
ONBOOT=yes
BOOTPROTO=dhcp
USERCTL=no
PEERDNS=yes
TYPE=Wireless
IPV6INIT=no
HWADDR=00:04:23:5c:81:52
NETMASK=
DHCP_HOSTNAME=
IPADDR=
DOMAIN=
GATEWAY=
ESSID=
CHANNEL=1
MODE=Auto
RATE=Auto


[root at laptop devices]# more ifcfg-eth0
# Intel Corp.|82801BD PRO/100 VE (MOB) Ethernet Controller
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=dhcp
TYPE=Ethernet
USERCTL=no
PEERDNS=yes
IPV6INIT=no
HWADDR=08:00:46:A3:33:B9