FC5

[Alma J Wetzker]

Net Llama! wrote:
> On 06/10/2006 07:12 PM, Rick Sivernell wrote:
> 
>>What does /etc/sysconfig/network-scripts/ifcfg-eth0 and 
>>/etc/sysconfig/network-scripts/ifcfg-eth1 look like?
>>
>>[root at RSivernell ~]# more /etc/sysconfig/network-scripts/ifcfg-eth0
>># Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
>>DEVICE=eth0
>>BOOTPROTO=none
>>BROADCAST=192.168.0.255
>>HWADDR=00:50:FC:8F:6F:5A
>>IPADDR=192.168.0.40
>>NETMASK=255.255.255.0
>>NETWORK=192.168.0.0
>>ONBOOT=yes
>>GATEWAY=192.168.0.1
>>TYPE=Ethernet
>>USERCTL=no
>>IPV6INIT=yes
>>PEERDNS=yes
>>[root at RSivernell ~]#
>>
>>[root at RSivernell ~]# more /etc/sysconfig/network-scripts/ifcfg-eth1
>># nVidia Corporation CK8S Ethernet Controller
>>DEVICE=eth1
>>BOOTPROTO=none
>>BROADCAST=192.168.0.255
>>HWADDR=00:11:2f:7f:17:ec
>>IPADDR=192.168.0.60
>>NETMASK=255.255.255.0
>>NETWORK=192.168.0.0
>>ONBOOT=yes
>>GATEWAY=192.168.0.1
>>TYPE=Ethernet
>>USERCTL=no
>>IPV6INIT=yes
>>PEERDNS=yes
>>[root at RSivernell ~]#
>>
>>
>>What's the output from "route -n" when both eth0 and eth1 are up?
>>
>>[root at RSivernell ~]# route -n
>>Kernel IP routing table
>>Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
>>192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
>>192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
>>169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
>>0.0.0.0         192.168.0.1     0.0.0.0         UG    0      0        0 eth0
>>[root at RSivernell ~]# 
>>
>>What is 192.168.0.1 ?
>>gateway to router at lan side. A D Link > DL 624
>>
> 
> 
> This looks ok to my eyes.  What if you run this command?
> oute add ?host 192.168.0.1 eth1
> 
> The only other thing I can figure out is possibly the routing table is 
> borked when eth0 gets the default route at boot.  If you set eth0 not to 
> come up at boot, does that have any impact?  What does the routing table 
> look like if only eth1 comes up at boot?

This is starting to look vaguely familiar.  On my laptop with SuSE 10.0, 
the system tries to bring up the internal nic as eth0 and the wireless 
card as eth1.  If I do not have eth0 connected, my resolv.conf does not 
get setup correctly.  I end up needing to down both interfaces and then 
reload eth1 (ifup eth1) to get things to work.  It may very well involve 
the route table, but I have not spent the time to fully diagnose it.

     -- Alma