FC5 Network nightmare

[Jeff Vian]

On Fri, 2006-04-21 at 03:31 +0200, Antonio Montagnani wrote:
> On my box acting as a router I have two NIC
> 
> eth0 is the onboard NIC (marvell 1Gbit)
> eth1 is the additional 10Mbit NIC (realtek 8029) for modem connection.
> 
> Sometimes upon booting I cannot connect to the modem and also pinging
> it is impossible, I get an ureachabale host.
> I reboot the machine and it works...
> I made a short investigation and
>  when not working
> 
> /sbin/ifconfig
> eth0      Link encap:Ethernet  HWaddr 52:54:05:E5:82:46
>           inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
>           inet6 addr: fe80::5054:5ff:fee5:8246/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:242 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 b)  TX bytes:18577 (18.1 KiB)
>           Interrupt:19 Base address:0xec00
> 
> eth1      Link encap:Ethernet  HWaddr 00:11:D8:BF:9F:05
>           inet addr:192.168.254.1  Bcast:192.168.254.255  Mask:255.255.255.0
>           inet6 addr: fe80::211:d8ff:febf:9f05/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:61 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:129 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:5734 (5.5 KiB)  TX bytes:12325 (12.0 KiB)
>           Interrupt:20
> 
> 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:3854 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:3854 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:5355251 (5.1 MiB)  TX bytes:5355251 (5.1 MiB)
> 
> when working:
> 
> /sbin/ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:11:D8:BF:9F:05
>           inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
>           inet6 addr: fe80::211:d8ff:febf:9f05/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:10 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:1192 (1.1 KiB)  TX bytes:7983 (7.7 KiB)
>           Interrupt:19
> 
> eth1      Link encap:Ethernet  HWaddr 52:54:05:E5:82:46
>           inet addr:192.168.254.1  Bcast:192.168.254.255  Mask:255.255.255.0
>           inet6 addr: fe80::5054:5ff:fee5:8246/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:348 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:401 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:1 txqueuelen:1000
>           RX bytes:37595 (36.7 KiB)  TX bytes:39948 (39.0 KiB)
>           Interrupt:20 Base address:0xec00
> 
> 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:2575 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:2575 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:5500220 (5.2 MiB)  TX bytes:5500220 (5.2 MiB)
> 
> ppp0      Link encap:Point-to-Point Protocol
>           inet addr:87.8.156.42  P-t-P:192.168.100.1  Mask:255.255.255.255
>           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
>           RX packets:338 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:332 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:3
>           RX bytes:29436 (28.7 KiB)  TX bytes:24734 (24.1 KiB)
> 
> I see that HWadrr and inet6 address are reversed..
> what does it mean???? help please
> 
This means that for whatever reason, eth0 and eth1 are being assigned to
the cards interchangeably.
You need add an alias in /etc/modprobe.conf to designate which driver is
loaded for eth0 and which is loaded for eth1 so it stops flopping the
order.

The first interface loaded is named eth0 by default, unless there is an
alias line that designates the desired name for that card.
My modprobe.conf has a line with
   alias eth0 forcedeth
so the integrated adapter is always assigned the name eth0.


> --
> Antonio Montagnani
> Skype : antoniomontag
>