Summary: | sys-apps/iproute2-2.6.23.20071016 - RTNETLINK: Invalid Argument when starting net | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ralf Folkerts <ralf.folkerts> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gentoo.org, gentoo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
/etc/conf.d/net
emerge --info |
Description
Ralf Folkerts
2008-03-17 08:43:30 UTC
Attach your /etc/conf.d/net here and post emerge --info output; thanks. Created attachment 146399 [details]
/etc/conf.d/net
Created attachment 146401 [details]
emerge --info
Hi,
here's my /etc/conf.d/net and the output of emerge --info. Sorry, I should at least have included the last.
Cheers,
_ralf_
Same here. After upgrading to iproute2-2.6.23.20071016 all interfaces are configured, but not brought up. Every call of /etc/init.d/net.* shows a lot of "RTNETLINK answers: Invalid argument"-Errors. Calling "ip link set lo up" from bash returns also a "RTNETLINK answers: Invalid argument"-error, "ifconfig lo up" works fine. I think this is only a bug in iproute2 and not related to any init-scripts. sys-apps/iproute2-2.6.23.20071016 should be masked meanwhile. Using this version on a remote box without physical access locks you out. I yesterday updated my @home System; on that maschine, the iproute2-2.6.23-20071016 indeed does work 1a. Not sure, maybe a Kernel-related issue (on the machine where the problem occured I tried Kernels 2.6.21-xen, 2.6.20-r2-xen, and 2.6.18-gentoo, i.e. 2 Xen Kernels and one rather old "normal" Kernel). On the @home-Machine I don't use Xen and it runs with Kernel 2.6.24-gentoo-r3. One more note: On my @home-System, to check my assumption the Problem is Kernel-related I just emerged & compiled a 2.6.19-gentoo-r5 Kernel. Upon booting this "old" Kernel I got exactly the same errors (i.e, RTNETLINK: invalid argument and no usable Interfaces) as on the Xen-Host @work. So it seems the "new" iproute2 needs either a more recent Kernel OR some feature turned on on an "old" Kernel... Confirmed here. Working configuration: sys-apps/iproute2-2.6.22.20070710 sys-kernel/xen-sources-2.6.20-r6 or: sys-apps/iproute2-2.6.23.20071016 sys-kernel/gentoo-sources-2.6.23-r8 Not working configuration: sys-apps/iproute2-2.6.23.20071016 sys-kernel/xen-sources-2.6.20-r6 Vincent I confirm also: everything works fine for me with: sys-apps/iproute2-2.6.22.20070710 sys-kernel/gentoo-sources-2.6.19-r5 and I get "RTNETLINK: Invalid Argument" errors if I upgrade to sys-apps/iproute2-2.6.23.20071016 (same kernel, which I cannot upgrade for other reasons) (In reply to comment #7) > Confirmed here. > Working configuration: > > sys-apps/iproute2-2.6.22.20070710 > sys-kernel/xen-sources-2.6.20-r6 > or: > sys-apps/iproute2-2.6.23.20071016 > sys-kernel/gentoo-sources-2.6.23-r8 > > Not working configuration: > > sys-apps/iproute2-2.6.23.20071016 > sys-kernel/xen-sources-2.6.20-r6 > > Vincent > re-open if iproute2-2.6.24.20080108 doesnt work |