Marty Landman wrote:
Newbie question here. I'm running Potato on an old box and it's nice and stable providing a web environment on my LAN.However the way I get networking going is to run the following commands after a reboot:modprobe tulip ifconfig eth0 inet up 192.168.0.222 \ netmask 255.255.255.0 broadcast 192.168.0.255 route add -net 192.168.0.0 netmask 255.255.255.0 gw 192.168.0.1 dev eth0 route add default gw 192.168.0.1 How can I avoid having to go through this? Thanks in advance, Marty
In a Debian Sid box that I have on my lan, I have the driver listed in /etc/modules:
#For Davicom Network card. tulip doesnot work
#network seems to work with tulip too :) 24Mar06
dmfe
And in /etc/network/interfaces (this box has a fixed IP address), I have:
$> cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.0.11
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.1
mtu 1500
up /etc/firewall-hs/fw-desktop-20051018.sh start
dns-nameservers x.y.z.n a.b.c.m
The last two lines are noteworthy. The line starting with "up" starts my
iptables based firewall script after this interface comes up. The last
line just specifies the dns nameserver (give by symbols above) that I
know from my DSL highspeed internet provider. Also, my home LAN router
has an ip address of 198.168.0.1, hence it is the gateway. You probably
do not need to give the mtu line.
The machine has only one LAN interface and it is detected as eth0. In your cause, if your machine has multiple interfaces, you would need to know what name is given to your tulip interface and replace "eth0" in the above configuration accordingly.
GL, ->HS