SIOCADDRT: No such process error when adding static IP information

[Veldkornet]

When adding a route eg: route add -net 172.16.0.0 netmask 255.255.240.0 gw 172.20.3.177 dev eth1
The following error is returned: SIOCADDRT: No such process

Also, if you add the route and static ip address to the network card via the NetworkManager Applet, the changes are lost after a reboot.

I am using integrated 2x nVidia Gigabit Lan cards on my ASUS M2N32-SLI Deluxe Wireless motherboard (http://www.asus.com/products.aspx?modelmenu=2&model=1163&l1=3&l2=101&l3=0&l4=0).

[Veldkornet (veldkornet)]

Note:

When I do the following "dmesg | grep -i eth0" or "dmesg | grep -i eth1"

I get the following:

[ 3.008533] forcedeth 0000:00:10.0: ifname eth0, PHY OUI 0x5043 @ 1, addr 00:17:31:e8:bf:b4
[ 40.416008] eth0: no IPv6 routers present
[ 233.114485] eth0: link down.
[ 239.473653] eth0: link up.

[ 3.528517] forcedeth 0000:00:11.0: ifname eth1, PHY OUI 0x5043 @ 1, addr 00:17:31:e8:c6:bc
[ 40.152008] eth1: no IPv6 routers present
[ 237.064804] eth1: link down.
[ 240.485189] eth1: link up.

[Veldkornet (veldkornet)]

Sorry to keep adding, but some more info:

uname -a:

Linux thealteredstate 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 GNU/Linux

[Veldkornet (veldkornet)]

and the lspci-vvnn.log

[Veldkornet (veldkornet)]

I've now runn the following

---------
sudo apt-get purge dhcp3-client
---------

This now seems to keep my static settings... although dhcp doesn't work anymore of course :-P

[Pascal De Vuyst (pascal-devuyst)]

Does a ping to the gw 172.20.3.177 work?
According to the man page of route the specified gateway must be reachable first. This usually means that you have to set up a static route to the gateway beforehand.

[Veldkornet (veldkornet)]

The addresses are irrelevant.

My point is that it won't let me add static anything. Only after I removed the dhcp3-client could I add anything.
Otherwise, all settings were lost after reboot.

[JC Hulce (soaringsky)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures