OK I need to get my second NIC set up as eth1...

[Captain Penguin]

I have a system running newly installed Slackware 7.1 (so I haven't updated any base software).

Slackware automatically configured my external NIC (which uses de4x5), so I am able to connect to the internet.

My second NIC (a Netgear card) uses the Tulip driver. This card is connected to the hub on my internal home network and will share the connection once it is working properly.

the first nic is on IRQ 11 I/O port 0x2400, and the second nic is on IRQ 11 I/O port 0x2800. They are both PCI cards.

When I run ifconfig it shows only eth0 and lo.

I have heard about insmod, modprobe, ifconfig eth1 up 192.. blah, and using the "route" program.

The trouble is I don't know what specifically needs to be done, what files need to be edited, etc.

Please help me out before I rip out my hair. If anymore info is needed I can provide...

[jscott]

This is at the end of my /etc/rc.d/rc.inet1 (Slack 8.0)


# Configure eth1 to point to private network
# Change these values to work with the private network
IPADDR="192.168.0.1"
NETMASK="255.255.255.0"
NETWORK="192.168.0.0"
BROADCAST="192.168.0.255"

echo "Attempting to configure eth1 as $IPADDR..."
/sbin/ifconfig -a eth1 $IPADDR
if [ ! $? = 0 ]; then
echo "Manual config of eth1 failed..."
else
echo "...Success!"
echo "Adding routing info for eth1..."
/sbin/route -N add -net $NETWORK netmask $NETMASK eth1
if [ ! $? = 0 ]; then
echo "...Failed to add route."
else
echo "...Success!"
fi
fi


Let me know if this works for you.

[Captain Penguin]

OK I appended that to the end of rc.inet1 and I get this message while booting up


Attempting to configure eth0 by contacting a DHCP server
eth0: media is TP
Attempting to configure eth1 as 192.168.0.1...
SIOCSIFADDR: No such device.
eth1: unknown interface: No such device
Manual config of eth1 failed...


I think you are heading in the right direction however!

[ 21 February 2002: Message edited by: Captain Penguin ]

[scanez]

Run modprobe tulip to load the driver for the second card. ALso add

alias eth1 tulip

to /etc/modules.conf (I believe that's how you load modules at boot with Slack...)

[SuperHornet]

I also had this problem with my dlink card and a 3com.
The dlink was eth1 with tulip and all of a sudden it was gone. I could start it manually with ifconfig. What I did was remove the dlink and place it in a differant PCI slot and WAMOO it worked.