FC2 2nd network card not recognized

[lvanek]

I was very lucky in upgrading from RH9 to FC2. Everything worked except a few things (Nvidia card, dual boot issue which were both worked around). Home network was another matter. I have eth0 connected via cable modem to internet provider. eth1 connected to local network (192.169.1.1).

2nd card is not being detected by FC2. Old RH9 files are still configured for it on the system. System tells me it doesnt seem to be present during bootup.

Routing table:

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
66.190.54.0 * 255.255.254.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default c66.190.54.1.jv 0.0.0.0 UG 0 0 0 eth0

the "system-control-network" tool does not seem to be very functional, perhaps because of legacy RH9 files.
It seems to confuse the mapping of the actual devices with the aliiases. etho is a 3c905-TX /TX 3-com card & eth1 is a Linksys NC100 10/100.

Im trying to avoid a fresh install everytime there is an issue, I actually use my Linux system (not a toy).
I uncertain which files to edit manually, since I dont trust the system-control-network tool. I would appreciate any suggestions. Thanks in advance.

check /etc/modprobe.conf, make sure there are proper aliases:
alias eth0 module_name
alias eth1 module_name
also, if you want to edit the files manually (due to lack of trust), edit /etc/sysconfig/netwok-scripts/ifcfg-eth0 and ifcfg-eth1

[lvanek]

Thanks for advice. Yes indeed we had:

....
alias eth0 3c59x
alias eth1 3c59x
....
....

changed to:

alias eth0 3c59x
alias eth1 tulip

contents of /etc/sysconfig/hwconf relating to the NETWORK are:

============
...
...
class: NETWORK
bus: PCI
detached: 0
device: eth0
driver: tulip
desc: "Linksys|NC100 Network Everywhere Fast Ethernet 10/100"
network.hwaddr: 00:04:5A:88:4C:9F
vendorId: 1317
deviceId: 0985
subVendorId: 1317
subDeviceId: 0574
pciType: 1
pcidom: 0
pcibus: 2
pcidev: b
pcifn: 0
-
class: NETWORK
bus: PCI
detached: 0
device: eth1
driver: 3c59x
desc: "3Com Corporation|3c905C-TX/TX-M [Tornado]"
network.hwaddr: 00:04:75:73:91:0F
vendorId: 10b7
deviceId: 9200
subVendorId: 10b7
subDeviceId: 1000
pciType: 1
pcidom: 0
pcibus: 2
pcidev: a
pcifn: 0
...
...

====================

This is clearly wrong as I am using the 3-com on eth0 now as I write this. Can I edit this file also?

/etc/sysconfig/network-scripts/ifcfg-eth0 looks like this:

===============

# Linksys|NC100 Network Everywhere Fast Ethernet 10/100
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=dhcp
TYPE=Ethernet
USERCTL=no
PEERDNS=yes
IPV6INIT=no
HWADDR=00:04:75:73:91:0f

==================

odd, eth0 is using the 3-com card.

NOTE: there is no /etc/sysconfig/network-scripts/ifcfg-eth1 file present and no directory in /sys/class/net/ for eth1.

I blame all this on the "system-control-network" tool which seems to change things unpredictably when
I try to correct things using it.

you need to create the file ifcfg-eth1. make it similar to the eth0 file but make changes where necessary. and yes you can change the hardware file, but I don't think it will have much of an affect.

[lvanek]

update:

Out of desparation I went thru the upgrade process again. Needless to say it didnt ask for many files..BUT it did register the two NIC cards again. ifcfg-ethx files needed some editing but finally my routing table looks like this:

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
66.190.54.0 * 255.255.254.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default c66.190.54.1.jv 0.0.0.0 UG 0 0 0 eth0

All I think I need to do now is add the special route that windos clients need. On RH9 I did:

/sbin/route add -host 255.255.255.255 dev eth1

To get this to happen at boot I added that line to file:

/etc/rc.d/init.d/dhcpd

Will this work at boot time for FC2 or is there a better way?