During the install of beta1, I noticed a message concerning
neighbour table overflow on vc4. It was suggested by alan that
this is a misconfiguration of the loop back device.
do you get this behavior consistently and repeatably on your installs ...? I've
not seen this message except during stressful network conditions (ie NFS server
timeouts during install...)
I had several of these tonight during a Winston Beta-1 custom graphical
install. The machine is at home on a small 10/100 hub with a few others; there
wouldn't be high network traffic here. The install also hung at "Performing
post-install configuration" and I'm entering a separate bug for that.
I get that message every time ( during install ). It appears after the X server
Still there in beta2.
I think alan cox said on the testers-list that this due
to some misconfiguration in the kernel.
Do you see this in beta 5?
ifconfig lo 127.0.0.1 netmask 255.0.0.0 up
route add -net 127.0.0.0
then it will be happy
Still seeing this in beta5.
A bit hard to do those commands alan suggested on install !
And I still see it in RC1.
I appears as the last line on VT3 ( or VT4 , where messages like
"<3> some kernel message" appear ) after the anaconda GUI is loaded
Alan, shouldn't the kernel add the network route automatically? In any case,
"route add -net 127.0.0.1" is complaning about SIOCADDRT: Invalid argument (with
standard route command).
The kernel will add the route if you ifconfig the device appropriately
CVS adds the 127.0.0.0 network route now. Let us know if you see this problem in
the next beta you get.
no post-fix reports of this error ... please reopen if still a problem ...
It still happens with Redhat Linux 7.0 (Guiness) i386.
On install from CD when the X server is started,
the message appears on VT4 (<4>neighbour table overflow)
Doesn't happen anymore with Florence beta2.