Phantom eth1 detected

[mdg]

I have a small home network set up as follows:

 

Cable modem connected to Edimax router via WAN port

Mdk 9.2 box connected to router (LAN port)

XP box connected to router (LAN port)

All IP's are handled by DHCP

 

Internet sharing works and file sharing works from Mdk only - I can browse XP dirs from Mdk box, but can't get into Mdk from XP (but that's not the issue right now)

 

When I bootup Mdk, it loads both eth0 and eth1. I only have one NIC on either machine, so what is eth1?

Here's the result of ifconfig

[root:marc]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:04:61:53:EC:B6  
         inet addr:192.168.2.101  Bcast:192.168.2.255  Mask:255.255.255.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:74166 errors:0 dropped:0 overruns:0 frame:0
         TX packets:77247 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:100 
         RX bytes:92538833 (88.2 Mb)  TX bytes:7197295 (6.8 Mb)
         Interrupt:11 Base address:0x1000 

lo        Link encap:Local Loopback  
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:306 errors:0 dropped:0 overruns:0 frame:0
         TX packets:306 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0 
         RX bytes:20474 (19.9 Kb)  TX bytes:20474 (19.9 Kb)

 

And ifconfig eth1

[root:marc]# ifconfig eth1
eth1: error fetching interface information: Device not found

 

Bootup also takes a long time to bring up eth0 (eth1 is picked up immediately after)

 

Is eth1 maybe the router?

[aru]

And ifconfig eth1

[root:marc]# ifconfig eth1<!--QuoteEBegin-->eth1: error fetching interface information: Device not found<!--QuoteEBegin-->

That error message means that eth1 doesn't exist. I don't understand your question. Are you saying that during boot you get a message saying that eth1 is found? well, as per your output obviously it isn't. Maybe you would like to post the apropiate quote of dmesg to see if your system tries to configure a eth1 during boot.

[mdg]

I didn't find the relevant part in dmesg, but it was in the boot.log:

Mar  2 12:58:13 mguise network: Setting network parameters:  succeeded
Mar  2 12:58:13 hostname network: Bringing up loopback interface:  succeeded
Mar  2 12:58:17 hostname network: Bringing up interface eth0:  succeeded
Mar  2 12:58:17 hostname network: Bringing up interface eth1:  succeeded
Mar  2 12:58:17 hostname internet: Checking internet connections to start at boot succeeded
Mar  2 12:58:18 hostname portmap: portmap startup succeeded
Mar  2 12:58:20 hostname ntpd: ntpd startup succeeded

[aru]

Post the result of running this command:

 

~# for file in  /etc/sysconfig/network-scripts/ifcfg-eth*; do echo $file; cat $file; done

[mdg]

aru, as requested:

[root:marc]# for file in  /etc/sysconfig/network-scripts/ifcfg-eth*; do echo $file; cat $file; done
/etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=dhcp
IPADDR=192.168.2.101
NETMASK=255.255.255.0
NETWORK=192.168.2.0
BROADCAST=192.168.2.255
ONBOOT=yes
MII_NOT_SUPPORTED=yes
NEEDHOSTNAME=yes
/etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE=eth1
BOOTPROTO=dhcp
NETMASK=255.255.255.0
ONBOOT=yes
MII_NOT_SUPPORTED=yes
NEEDHOSTNAME=yes

[aru]

Since eth1 makes no sense to you, you have at least two options:

1. remove that file (/etc/sysconfig/network-scripts/ifcfg-eth)
   
2. Change the prameter ONBOOT=yes to ONBOOT=no in /etc/sysconfig/network-scripts/ifcfg-eth1
   

any of both are safe to your system. Next time you boot you won't see that message again(*)

 

 

(*) unless any missconfigured autoconfiguration program enable it again :mrgreen:

[mdg]

I deleted the file and rebooted - no "bringing up eth1" anymore. Thanks aru