problem with route after upgrading

[davidbrohall]

I just upgraded from fedora core 3 to development.

After the upgrade I get an error when I start the networkdevices:


Starting loopback: RTNETLINK answers: Invalid argument [ OK ]

Starting eth0: RTNETLINK answers: Invalid argument [ OK ]

Starting eth1: RTNETLINK answers: Network is unreachable
RTNETLINK answers: Invalid argument [ OK ]

ifup eth1
RTNETLINK answers: Invalid argument


When I run route -e it shows only eth0 and eth1 but no default route
/proc/net/route shows only 2 eth and no route


if i run route add default gateway <ip-addr> everything is as it should be.


I have tried to reconfigure all eth-settings and route-setting without any success.


What can have been changed from the fedora 3 to development version?
I think that some settings are wrong within network-script that makes route not start. Anyone got any idea?

Thanks
David Brohall

[mungoose]

As my equipment for clairvoyance is at the repair shop could you please enlighten me with what you did and how your network script and configuration files look like? Than it might be possible to asiist you in trouble shooting your set up.

[davidbrohall]

I have no access to the files right now, but my temporary sullotion was to remove ip in fron of "route add gateway..."

every command I use with "ip" doesn't work, and the network-scripting files uses "ip". Could there be any changes between fedora development and core 3 in the command ip?

Thank you for your help

[Grogan]

Anybody having this problem build their kernels with -Os (Optimize for Size, under "Configure standard kernel features for small systems")?

I had this same problem, with the exact same RTNETLINK error messages as in the first post in this thread after building a custom kernel in Fedora Core 4. Network interface was getting IP and DNS servers assigned from DHCP, but no gateway. I was doing "route add" manually after the system was up and it was working fine.

I build a lot of kernels, but this one had me stumped for a while. I tried enabling all the networking settings as in the supplied config file, but it wasn't working.

Yes, it was the gcc 4.0 compiler... a driver must have been getting subtly mangled with -Os. I have been compiling kernels with -Os long before it was ever an option in the config (since linux 2.4) and have taken it for granted. I've never had to build kernels with gcc 4.0 before.

[scottmuz]

Grogan I am getting the same RTNETLINK problem with with a custom built kernel. So am
I correct to understand that you don't get the problem if you have "Optimized for size" = N?

[dnar]

I had this using a .config from my last FC3 kernel.

I grabbed the FC4 config for my CPU and then tweaked it, recompile, all was good.

[Grogan]

Grogan I am getting the same RTNETLINK problem with with a custom built kernel. So am
I correct to understand that you don't get the problem if you have "Optimized for size" = N?

Yes, if you've selected "Optimize for Size", under "General Setup/ Configure standard kernel features (for small systems)" deselect it and recompile.

Edit: I'd probably do a "make clean" there first to be on the safe side. (the build system would probably be smart enough to recompile all objects after such a config change I'm sure, but it's going to pretty much take the same amount of time so might as well do it)

Also, for DHCP to work you must enable "Packet Socket" (say Y) under Device Drivers/Networking Support/Networking Options.