trying to write a startup script

psytae · 09-09-2004, 12:37 PM

Ok here is the deal I am fairly new to Linux but have found Debian to be a great OS to use.

Im in college and right now Im using Debian in a Lab environment as a server, with about 7 other groups using different server OSes including Win 2003 server and Win 2000 server, and we are setting up a mini internet in the lab.

We got routing to work on the Debian Server using static routes in the lab using the route add command, but everyday we come into the lab to get the routing table back up we have to do the following commands to get the routing table up and running agian between the networks.

Code:

route add -net 192.168.1.0 netmask 255.255.255.0 gw 10.9.64.101
route add -net 192.168.3.0 netmask 255.255.255.0 gw 10.9.64.103
route add -net 192.168.4.0 netmask 255.255.255.0 gw 10.9.64.104
route add -net 192.168.5.0 netmask 255.255.255.0 gw 10.9.64.105
route add -net 192.168.6.0 netmask 255.255.255.0 gw 10.9.64.160
route add -net 192.168.7.0 netmask 255.255.255.0 gw 10.9.64.107
route add -net 192.168.8.0 netmask 255.255.255.0 gw 10.9.64.108

and we get the following Routing Table

Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.7.0     10.9.64.107     255.255.255.0   UG    0      0        0 eth0
192.168.6.0     10.9.64.160     255.255.255.0   UG    0      0        0 eth0
192.168.5.0     10.9.64.105     255.255.255.0   UG    0      0        0 eth0
192.168.4.0     10.9.64.104     255.255.255.0   UG    0      0        0 eth0
192.168.3.0     10.9.64.103     255.255.255.0   UG    0      0        0 eth0
192.168.2.0     *               255.255.255.0   U     0      0        0 eth1
192.168.1.0     10.9.64.101     255.255.255.0   UG    0      0        0 eth0
192.168.8.0     10.9.64.108     255.255.255.0   UG    0      0        0 eth0
10.9.64.0       *               255.255.252.0   U     0      0        0 eth0
default         10.9.64.1       0.0.0.0         UG    0      0        0 eth0

Im wanting to write and implement a start up script that will input the route commands into the kernel on boot up instead of us having to do it everytime we reboot the server. Can anyone help me out with this?

m_yates · 09-09-2004, 01:00 PM

There is a guide to creating a startup script here: http://www.desktop-linux.net/debian-rclocal.htm

HappyTux · 09-09-2004, 01:06 PM

Should be as easy as adding a file like this in the /etc/init.d directory called say routes.

Code:

#!/bin/sh
echo "Adding routes ..."
route add -net 192.168.1.0 netmask 255.255.255.0 gw 10.9.64.101
route add -net 192.168.3.0 netmask 255.255.255.0 gw 10.9.64.103
route add -net 192.168.4.0 netmask 255.255.255.0 gw 10.9.64.104
route add -net 192.168.5.0 netmask 255.255.255.0 gw 10.9.64.105
route add -net 192.168.6.0 netmask 255.255.255.0 gw 10.9.64.160
route add -net 192.168.7.0 netmask 255.255.255.0 gw 10.9.64.107
route add -net 192.168.8.0 netmask 255.255.255.0 gw 10.9.64.108
echo "Done adding routes ..."

Then chmod +x /etc/init.d/routes and now edit the file /etc/init.d/bootmisc.sh and near the bottom add this.

Code:

if [ -f /etc/init.d/routes ]; then
    ./etc/init.d/routes
fi

All steps as root of course.

psytae · 09-09-2004, 07:01 PM

Im curious what the difference is between what HappyTux's suggested with:

Quote:

edit the file /etc/init.d/bootmisc.sh and near the bottom add this.

Code:

 if [ -f /etc/init.d/routes ]; then
    ./etc/init.d/routes
fi

and what the link m_yates' led me to said to do with

Quote:

Next, link the new local file by running:

update-rc.d local defaults 80

to add the script to the runlevel startups?

HappyTux · 09-09-2004, 07:31 PM

Quote:

Originally posted by psytae
Im curious what the difference is between what HappyTux's suggested with:

and what the link m_yates' led me to said to do with

to add the script to the runlevel startups?

Not much really they both should achieve the same result. The only thing being you are not really making a true startup script for that to be true you would have to have sections in the file for a start, stop, restart that you could use with say a /etc/init.d/routes start command that a normal startup script has. That is the reason I suggested the bootmisc.sh file because it is a place for miscellaneous items you want started on boot so seems like the perfect place to put it and since it is one of the last scripts run the networking is going to be up already.

zuralin · 09-09-2004, 09:17 PM

Shouldn't this all be done by editing /etc/network/interfaces?