I've found that the latest snapshot does work:
./ip -4 neigh flush dev eth0
*** Flush not complete bailing out after 10 rounds
It doesn't hang up completly. I hope this solution can be backported to the
Debian's version. The bug is very annoying and important for me.
--
.''`.Piotr
I had the same situation with Ubuntu Hoary (iproute_20041019). I think
this is the same version as in Debian and also the 2.6.10 kernel.
Yesterday i inform Stehpen Hemminger at osdl.org about this problem and
he answer:
Thanks, this usually shows up when someone tries to run flush
as non-root.
I have the same result on a non-debian system with kernel 2.4.28 while
2.4.27 is still fine. 2.4.9 and 2.4.28 have the same changes in the
neighbour.c code so this is most likely a kernel issue.
hope this helps,
wilfried
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
We had a setup with kernel-image-2.6.9-2-k7 2.6.9-5 and iproute
20010824-8woody1 and the same problem as described. Then we upgraded to
the latest unstable versions:
kernel-image-2.6.10-1-k7 2.6.10-4
iproute 20041019-2
but still encounter the same problem: ip -4 neigh flush dev eth0 hangs
up.
allright, i got the same as ernesto. if an arp entry exists then the
command still hangs. the startup scripts must have been changed so the
bug is not triggered anymore during the boot process. :/
greetings,
wilfried
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
hi,
kernel-image-2.6.10-1-686 2.6.10-4 works for me. the fw-builder script
and the ip flush command do not hang anymore.
greetings,
wilfried
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
6 matches
Mail list logo
