route lost on reboot

[kamina]

I have a strange problem with my network. My primary network interface broke down, and I added a new card (3com 905 series). It get's an ip, netmask and dns fine, but does'nt set the router. After every boot I have to enter:

route add default gw xxx.249.31.254

A bit tough to get my wife to do it, I don't think she would even understand enough to sudo, or su - to root. Any idea what could solve the issue?

[Zipster]

Why don't ya put that command in
/etc/rc.local

use the full path to route eg /sbin/route ...

That will make it do it every bootup

[kamina]

I could try, though I don't have a static ip. I guess the dhcp will probably provide an ip that goes through the same gateway though, as it's quite a bit subnet 255.255.224.0).

[erroneus]

That's a weird problem. Surely there is some network setting to allow dhcp to set the default route. Somehow, perhaps, the original card's configuration is preventing that in some way?

[such007]

vi your /etc/sysconfig/network-scripts/ifcfg-ethX

add the line:

GATEWAY=xxx.249.31.254

this should solve the problem.

[kamina]

Originally Posted by erroneus

That's a weird problem. Surely there is some network setting to allow dhcp to set the default route. Somehow, perhaps, the original card's configuration is preventing that in some way?

This is what I would imagine too. I guess I'll fix it with this "bubblegum" solution for now, as the internal nic will be fixed under warrenty anyway.

[kamina]

If I want something to be run on startup like that, but as the user logged in, what can I do? I would like skype to start up with the computer as I never remember to start it up myself.

Can I just add " /usr/bin/skype" to the end of .bash_profile?

[such007]

Under desktop click preferences, more preferences, then select sessions. Select the startup tab then enter /usr/bin/... and it should start automatically for you.

[gavinw6662]

do you have a custom kernel?? Are you sure that there is some sort of module or support for that card in your kernel?? I recently had this problem on a freBSD system, turns out the module wasn't properly configured for the kernel.