trouble adding static route to fedora 11
 

I need a static route setup on fedora 11 to allow a remote site to work. I can add the static route using:

route add -net 192.1.2.0 netmask 255.255.255.0 gw 192.1.1.152

but after reboot it the static route is lost. I have tried /etc/rc.d/rc.local and also added the static route through the network gui but neither have worked. Where would I need to add this to have it started each time the system is booted??

Hello,

Haven't used Fedora in a bit, but have a look in /etc/sysconfig/network-scripts/route-eth0 after you set your static route and see if the changes are made. Of course, change the interface to whatever you are using. Make your changes reflect in that file, and your static route will be defined.

Cheers,

Josh

The changes are there, but the route is still not being started. I created a file in /etc/init.d named routes to automatically add the routes but it's getting an error stating: "SIOCADDRT: no such process". However, if I run the exact same command once the server is started, it adds the route with no problem.

are you using the "networkmanager" or the older and still installed but turned off "network"
on this WAY PAST it's End Of Life fedora 11 .( 16 is in testing )

networkmanager auto set it up on boot
network is manual

I know this is going to bug the living sh*t out of you, but my server is running Fedora 11 :D

I think I'll revert my server from Fedora 14 to Fedora 11. Things were better in the "old" days :cool:

True that. But here's the catch... If you do revert, you are going to have to hand-update EVERYTHING.... Even the kernel. Fedora 11's end of life ended a while ago...... So unless you either really want to do this, or have a damn good reason for going to Fedora 11, then stick with an updated version that gets its updates. I hand update what I need to on my server for the experience, and also because I'm weird. So if you do, what's your reason? :p

I believe it's using network manager.

When you mentioned NetworkManager I did some searching and ended up finding this (http://forums.fedoraforum.org/showthread.php?t=219788). Creating the /etc/NetworkManager/dispatcher.d/02-setuproutes file worked perfectly. Thanks for the help.

Glad to hear you got it figured out man. I knew it had something to do with a script within NetworkManager.

I'm just joking. It would take way too much effort to go backwards. On the other hand, it would irritate JohnVV :hattip:

true .

but most of the time the person who is using the EOL fedora had / has no idea that they are using a EOL version

the rest DO know the risks ( or SHOULD know the risks )
most of the time the risk is small but not always .

Awe, we are all getting along.... Cute.

Anyways.... I'm done thread jacking for today. To the OP - Good luck. John and The Bassinator - I'm not saying anything....

there's still some truth to that. things are kept being added till it's so bloated at times, troubleshooting a small p[roblem takes ages. haha