Where to add route command in files to make it stay on every bootup?

Hello,

I would like to add:

"route add 192.168.0.1 gw 30.38.72.50" to SuSE so that it's not required to be typed every time the system is rebooted.

I scavenged the net and it seems like within /ect/rc.d/boot.local I should be able to add the command and it be loaded with the OS.

Was this a correct notion or is boot.local not for commands like route?

I have seen other threads of various forums mention rc.local and I do not have this file. I attempted to do write that route command into boot.local and it didn't change anything.

It depends on your distribution (and maybe version thereof).

What is your distribution and version?

What does cat /etc/issue show?

What does uname -a show?

SuSE 10.1,

It's actually a work computer that I won't have access to till tomorrow morning. I will be sure to post results so I can get this thing solved.

Thanks.

uname -a : linuxhost1 2.6.16.13-4-default #1 "time" UTC 2006 i686 i686 i386 GNU/Linux

The other command just told me I was running SUSE 10.1

OK - I don't use Suse but a quick Google search took me to the following page:

http://linuxmafia.com/pub/linux/suse...chapter10.html

It looks by the way as as if the site might be a handy one to book mark if you're doing Suse.

Section 10.4 from the above link says:

10.4 Setting up static routing We've discussed network configurations and what routing is used for. Now you're ready for setting up routing in SuSE Linux. YaST allows you to specify a default router in the format that you used to configure an interface. This is fine for a leaf node in a simple network. However, if the network has more than one router, or you actually want to set up a router, you'll need more than this. You need to specify a routing table. Even if YaST doesn't provide a way to set up a routing table, the SuSE Linux distribution has a fairly easy way to do this. The file /etc/route.conf contains a routing table, which will be set up by the script /sbin/init.d/route whenever a networking runlevel (by default runlevels two and three) is reached. Following is a very simple routing table such as is found in /etc/route.conf. # # /etc/route.conf for hosts in 'Network A' # # In this file you can configure your static routing... # # This file is read by /sbin/init.d/route. # # # Destination Dummy/Gateway Netmask Device # 192.168.0.0 0.0.0.0 255.255.255.128 eth0 default 192.168.0.1 This routing table is typical for a simple network host. It could be any host in Network A from Figure 9-2. As you can see, comment lines start with a hash sign (#) in the first column. Comment lines and empty lines are ignored when the route script sets up the kernel routing table. The other lines represent routing table entries. The format is very close to the output of the route command, as we demonstrate in Chapter 9. The first column specifies a destination. This can be either a network address, a host address, or the string default for the default gateway. Whether the given address is a host or a network is determined by the netmask given in the third column. The network mask for a host is always 255.255.255.255. Everything else specifies a network route. Network route means a route to a network, whereas a host route is a route to a single host. The second column gives either the IP address of the router, which should be used to reach the destination given in the first column, or the special value 0.0.0.0, which means that all traffic headed to the destination will be given to1 the device specified in the last column. If a gateway address is given, the device specification is optional. To clearly illustrate this, we refer back to Figure 9-2 and have a look at the entries of the routing tables of the hosts and routers in this network.

hmmmm... I can't seem to locate any file called route.conf in /etc/

Let me go look again.

If you didn't have any statically defined routes you might not need it. You can create it from scratch. All the lines starting with "#" are comments so you can leave them out (or you can just cut and paste from the earlier post).

If I do create this file, will I need to do anything in addition to make the system use it?

second day using SUSE, and first time in about 6-7 years. I'm getting the hang of it...slowly.

nevermind-I am crazy

I thought for some reason I had more/less files when I was logged into root.

Uhh yeah forget that last thing I said, I think i am going crazy

OK - so if you say forget the last thing you said which is to nevermind the question that means you DO want an answer to the question?

The answer is yes - you'll likely have to stop and start networking to make it take effect. However, if you've already statically set the route with "route add" at command line there's no hurry to do it. I would definitely plan to boot the box after making the change so you could verify the static route comes back in after a reboot. (e.g. Don't just wait for the next time it crashes - you might have forgotten by then and tear your hair out wondering why your networking suddenly is an issue.)

made the file, made the command.

Nothing happened after reboot ;(

I've also been trying to use the Yast Routing GUI because it has a "expert configuration" portion where you can do the same thing.

The thing is, if I check the box to enable expert config, add my "expert" routing and then hit finish....next time I open up the routing tool the box is unchecked and my settings never go through!!!

"made the file, made the command"

By file I assume you mean the one from the link I posted.

What "command" have you "made"?

Sorry, I began to confuse another trick I was trying to do.

ok: so I made the file route.conf and I placed it in the /etc/ folder per the website you linked.

In the final I only wrote

30.38.72.50 0.0.0.0 255.255.255.0 eth0
192.168.0.1 30.38.72.50 255.255.255.255 eth0

saved the file, rebooted and when using the route -n command I find that nothing has changed.

check out the /etc/sysconfig/network/routes file