'ip addr flush dev eth0' enters an endless loop
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
iproute (Debian) |
Fix Released
|
Unknown
|
|||
iproute (Ubuntu) |
Fix Released
|
Low
|
Daniel Silverstone |
Bug Description
The title says it all. I ran this command by accident without sudo and had to
kill it after a while with ^C. Running with sudo goes normally. I'm using Hoary
vanilla.
In Debian Bug tracker #282492, Andreas Barth (aba) wrote : iproute: ip -4 neigh flush ... - not reproducible for me | #1 |
In Debian Bug tracker #282492, Wilfried Weissmann (wilfried-weissmann) wrote : iproute: "ip -4 neigh flush dev eth0" hangs up | #2 |
Hi,
I also have this problem. It only occurs with (debian i686) kernel
version 2.6.9 and above. This causes my fwbuilder startup script to hang...
The command is:
/sbin/ip -4 neigh flush dev lan
The problem is not new. I just kept on using kernel 2.6.8 which works fine.
iproute version is 20041019-2. strace is the same so I do not send it.
Greetings,
Wilfried
In Debian Bug tracker #282492, Wilfried Weissmann (wilfried-weissmann) wrote : | #3 |
hi,
kernel-
and the ip flush command do not hang anymore.
greetings,
wilfried
In Debian Bug tracker #282492, Ernesto Baschny [cron] (ernesto-cron-it) wrote : | #4 |
We had a setup with kernel-
20010824-8woody1 and the same problem as described. Then we upgraded to
the latest unstable versions:
kernel-
iproute 20041019-2
but still encounter the same problem: "ip -4 neigh flush dev eth0" hangs
up.
We noticed that it only happens if there are entries in the ARP-Table.
If the ARP cache is empty, it exits normally saying "Nothing to flush".
Our ARP-Cache is also being populated very quickly, maybe there is a
race-condition here?
If we leave the hung ip neigh flush dev eth0 running and in another
console issue something like:
# for a in `arp -n | awk '/^[0-9]/ { print $1; }'`; do arp -d $a; done
some times in a row (it cleans up all entries in the arp-cache), the
hung ip command awakes and finishes.
In Debian Bug tracker #282492, Wilfried Weissmann (wilfried-weissmann) wrote : | #5 |
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
In Debian Bug tracker #282492, Wilfried Weissmann (wilfried-weissmann) wrote : | #6 |
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
In Debian Bug tracker #282492, Wilfried Weissmann (wweissmann) wrote : multiple neighbour cache tables for AF_INET | #7 |
Hi,
The kernels 2.4.28+ and 2.6.9+ with IPv4 and ATM-CLIP enabled have bugs in
the neighbour cache code. neigh_delete() and neigh_add() only work properly
if one cache table per address family exist. After ATM-CLIP installed a
second cache table for AF_INET, neigh_delete() and neigh_add() only examine
the first table (the ATM-CLIP table if IPv4 and ATM-CLIP are compiled into
the kernel). neigh_dump_info() is also affected if the neigh_dump_table()
call fails.
This bug causes "ip neigh flush dev <some ethernet device>" to run into an
infinite loop when the arp cache is already populated (debian bug #282492).
"ip neigh delete ..." commands for non ATM-CLIP entries fail with an EINVAL.
This is because of the IPv4 neighbour table that is installed in arp.c is
never examined when sending delete commands.
I have attached a minimally tested patch for 2.4.28 that fixes this problem.
Greetings,
Wilfried
--
10 GB Mailbox, 100 FreeSMS http://
+++ GMX - die erste Adresse f�r Mail, Message, More +++
In Debian Bug tracker #282492, Herbert Xu (herbert-gondor) wrote : | #8 |
Wilfried Weissmann <email address hidden> wrote:
>
> The kernels 2.4.28+ and 2.6.9+ with IPv4 and ATM-CLIP enabled have bugs in
> the neighbour cache code. neigh_delete() and neigh_add() only work properly
> if one cache table per address family exist. After ATM-CLIP installed a
> second cache table for AF_INET, neigh_delete() and neigh_add() only examine
> the first table (the ATM-CLIP table if IPv4 and ATM-CLIP are compiled into
> the kernel). neigh_dump_info() is also affected if the neigh_dump_table()
> call fails.
Indeed, this has been the case for a very long time.
IMHO you need to give the user a way to specify which table they want
to operate on. If they don't specify one, then the current behaviour
of choosing the first table found is reasonble.
Cheers,
--
Visit Openswan at http://
Email: Herbert Xu ~{PmV>HI~} <email address hidden>
Home Page: http://
PGP Key: http://
In Debian Bug tracker #282492, YOSHIFUJI Hideaki / =?iso-2022-jp?B?GyRCNUhGIzFRTEAbKEI=?= (yoshfuji) wrote : | #9 |
In article <email address hidden> (at Sat, 29 Jan 2005 09:19:49 +1100), Herbert Xu <email address hidden> says:
> IMHO you need to give the user a way to specify which table they want
> to operate on. If they don't specify one, then the current behaviour
> of choosing the first table found is reasonble.
We have dev. Isn't is sufficient?
--yoshfuji
In Debian Bug tracker #282492, Herbert Xu (herbert-gondor) wrote : | #10 |
On Sat, Jan 29, 2005 at 07:46:05AM +0900, YOSHIFUJI Hideaki / ?$B5HF#1QL@ wrote:
> In article <email address hidden> (at Sat, 29 Jan 2005 09:19:49 +1100), Herbert Xu <email address hidden> says:
>
> > IMHO you need to give the user a way to specify which table they want
> > to operate on. If they don't specify one, then the current behaviour
> > of choosing the first table found is reasonble.
>
> We have dev. Isn't is sufficient?
It could be used for neigh_add/
to query whether a given table is the right one for a device.
For dump it isn't the same. However, perhaps it's not too important
to query a specific table.
Cheers,
--
Visit Openswan at http://
Email: Herbert Xu ~{PmV>HI~} <email address hidden>
Home Page: http://
PGP Key: http://
Rui Matos (tiagomatos) wrote : | #11 |
The title says it all. I ran this command by accident without sudo and had to
kill it after a while with ^C. Running with sudo goes normally. I'm using Hoary
vanilla.
In Debian Bug tracker #282492, lkcl (lkcl) wrote : iproute: removing modules, ifup down up down kill ip _eventually_ succeeds | #12 |
Package: iproute
Version: 20041019-3
Severity: normal
Followup-For: Bug #282492
one million and increasing attempts to flush eth0.
this is what i am using (in combination with fwbuilder) to attempt
to get round of the problem. it is not successful always but can be
eventually successful after killing /sbin/ip and re-running the script,
repeat until success.
#!/bin/sh
iptables -F
iptables -X
ifdown eth0
ifdown eth1
rmmod ip6table_filter
rmmod ip6_tables
rmmod ipt_LOG
rmmod ipt_state
rmmod ip_nat_tftp
rmmod ip_nat_snmp_basic
rmmod ip_nat_irc
rmmod ip_nat_ftp
rmmod ip_nat_amanda
rmmod iptable_nat
rmmod ip_conntrack_tftp
rmmod ip_conntrack_
rmmod ip_conntrack_irc
rmmod ip_conntrack_ftp
rmmod ip_conntrack_amanda
rmmod ip_conntrack
rmmod iptable_filter
rmmod ipt_REDIRECT
sleep 1
rmmod tulip
rmmod 3c59x
modprobe tulip
modprobe 3c59x
sleep 1
ifup eth0
ifup eth1
ip -4 neigh flush dev eth0
ip -4 neigh flush dev eth1
sleep 1
ifdown eth0
ifdown eth1
sleep 1
ifup eth0
ifup eth1
sh /etc/fwbuilder.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux highfield 2.6.11-1-686 #1 Fri May 20 07:34:54 UTC 2005 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages iproute depends on:
ii libatm1 2.4.1-16 shared library for ATM (Asynchrono
ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an
-- no debconf information
Ante Karamatić (ivoks) wrote : | #13 |
Confirmed. Loop takes CPU to 100% usage. Moving to normal severity. This isn't a
case in Breezy, only Hoary.
Rui Matos (tiagomatos) wrote : | #14 |
(In reply to comment #1)
> Confirmed. Loop takes CPU to 100% usage. Moving to normal severity. This isn't a
> case in Breezy, only Hoary.
If it isn't the case in Breezy then maybe it is a kernel bug. I've never done
this with 2.6.12 and am still running with 2.6.10 (because of other bugs) even
if my userspace is all the latest breezy. To sum it up: in hoary's 2.6.10-34
with all userspace being breezy I still get this behaviour.
Ante Karamatić (ivoks) wrote : | #15 |
No, this isn't a kernel issue. Tested on Hoary on 2.6.11.7.
In Debian Bug tracker #282492, Piotr Roszatycki (dexter) wrote : Re: iproute: "ip -4 neigh flush dev eth0" hangs up | #16 |
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 Roszatycki, Netia SA
: :' : mailto:<email address hidden>
`. `' mailto:<email address hidden>
`-
In Debian Bug tracker #282492, Herbert Straub (herbert) wrote : | #17 |
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. Some vendors added a check for getuid() != 0, but that
fails in secure environments with capabilities and no root user.
I'll probably just change it to try 10 times and give up.
I isolate his changes and create this patch
--- ip/ipneigh.c.ORIG 2005-08-17 22:11:06.000000000 +0200
+++ ip/ipneigh.c 2005-08-17 22:13:02.000000000 +0200
@@ -31,6 +31,7 @@
#include "ip_common.h"
#define NUD_VALID
(NUD_PERMANENT|
+#define MAX_ROUNDS 10
static struct
{
@@ -411,7 +412,7 @@
filter.rth = &rth;
- for (;;) {
+ while (round < MAX_ROUNDS) {
if (rtnl_wilddump_
RTM_GETNEIGH) < 0) {
@@ -437,6 +438,9 @@
}
}
+ printf("*** Flush not complete bailing out after %d rounds\n",
+ MAX_ROUNDS);
+ return 1;
}
if (rtnl_wilddump_
The modified iproute package for Ubuntu Hoary (and i think you can easy
rebuild it for Debian) are available under:
http://
More details in the Ubuntu Bug #9106
(https:/
Best regards
Herbert Straub
Debian Bug Importer (debzilla) wrote : | #18 |
Message-Id: <email address hidden>
Date: Mon, 22 Nov 2004 15:23:58 +0100
From: Piotr Roszatycki <email address hidden>
To: <email address hidden>
Subject: iproute: "ip -4 neigh flush dev eth0" hangs up
Package: iproute
Version: 20041019-0.1
Severity: normal
# ip addr
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,
link/ether 00:0d:9d:9d:b5:76 brd ff:ff:ff:ff:ff:ff
inet 195.114.160.200/26 brd 195.114.160.255 scope global eth0
inet6 fe80::20d:
valid_lft forever preferred_lft forever
3: sit0: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
10: tun0: <POINTOPOINT,
link/[65534]
inet 10.114.160.200 peer 10.0.0.1/32 scope global tun0
# strace ip -4 neigh flush dev eth0
execve("/sbin/ip", ["ip", "-4", "neigh", "flush", "dev", "eth0"], [/* 11 vars
*/]) = 0
uname({sys="Linux", node="ginger", ...}) = 0
brk(0) = 0x8069000
old_mmap(NULL, 4096, PROT_READ|
0xb7fe9000
access(
directory)
open("/
directory)
open("/
fstat64(3, {st_mode=
old_mmap(NULL, 100000, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7fd0000
close(3) = 0
access(
directory)
open("/
read(3, "\177ELF\
512
fstat64(3, {st_mode=
old_mmap(NULL, 73608, PROT_READ|
old_mmap(
0xf000) = 0xb7fcd000
old_mmap(
MAP_ANONYMOUS, -1, 0) = 0xb7fce000
close(3) = 0
access(
directory)
open("/
read(3, "\177ELF\
512
fstat64(3, {st_mode=
old_mmap(NULL, 4096, PROT_READ|
0xb7fbd000
old_mmap(NULL, 1289004, PROT_READ|
old_mmap(
0x12f000) = 0xb7fb2000
old_mmap(
MAP_ANONYMOUS, -1, 0) = 0xb7fba000
close(3) = 0
set_thread_
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1,
seg_not_present:0, useable:1}) = 0
munmap(0xb7...
Debian Bug Importer (debzilla) wrote : | #19 |
Message-ID: <email address hidden>
Date: Wed, 5 Jan 2005 22:37:16 +0100
From: Andreas Barth <email address hidden>
To: <email address hidden>
Subject: iproute: ip -4 neigh flush ... - not reproducible for me
tag 282492 + unreproducible help
thanks
Hi,
this problem is not reproducible for me, at least not with the current
version -1.
The bad thing is also that I don't have any idea how to fix it, so this
means that I need help.
Cheers,
Andi
--
http://
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
Debian Bug Importer (debzilla) wrote : | #20 |
Message-ID: <email address hidden>
Date: Tue, 11 Jan 2005 21:13:01 +0100
From: Wilfried Weissmann <email address hidden>
To: <email address hidden>
Subject: iproute: "ip -4 neigh flush dev eth0" hangs up
Hi,
I also have this problem. It only occurs with (debian i686) kernel
version 2.6.9 and above. This causes my fwbuilder startup script to hang...
The command is:
/sbin/ip -4 neigh flush dev lan
The problem is not new. I just kept on using kernel 2.6.8 which works fine.
iproute version is 20041019-2. strace is the same so I do not send it.
Greetings,
Wilfried
Debian Bug Importer (debzilla) wrote : | #21 |
Message-ID: <email address hidden>
Date: Wed, 19 Jan 2005 19:37:32 +0100
From: Wilfried Weissmann <email address hidden>
CC: <email address hidden>
Subject: Re: iproute: "ip -4 neigh flush dev eth0" hangs up
hi,
kernel-
and the ip flush command do not hang anymore.
greetings,
wilfried
Debian Bug Importer (debzilla) wrote : | #22 |
Message-ID: <email address hidden>
Date: Thu, 20 Jan 2005 13:00:00 +0100
From: "Ernesto Baschny [cron]" <email address hidden>
To: <email address hidden>
Subject: Re: iproute: "ip -4 neigh flush dev eth0" hangs up
We had a setup with kernel-
20010824-8woody1 and the same problem as described. Then we upgraded to
the latest unstable versions:
kernel-
iproute 20041019-2
but still encounter the same problem: "ip -4 neigh flush dev eth0" hangs
up.
We noticed that it only happens if there are entries in the ARP-Table.
If the ARP cache is empty, it exits normally saying "Nothing to flush".
Our ARP-Cache is also being populated very quickly, maybe there is a
race-condition here?
If we leave the hung ip neigh flush dev eth0 running and in another
console issue something like:
# for a in `arp -n | awk '/^[0-9]/ { print $1; }'`; do arp -d $a; done
some times in a row (it cleans up all entries in the arp-cache), the
hung ip command awakes and finishes.
Debian Bug Importer (debzilla) wrote : | #23 |
Message-ID: <email address hidden>
Date: Thu, 20 Jan 2005 19:18:00 +0100
From: Wilfried Weissmann <email address hidden>
CC: <email address hidden>
Subject: Re: iproute: "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
Debian Bug Importer (debzilla) wrote : | #24 |
Message-ID: <email address hidden>
Date: Tue, 25 Jan 2005 18:55:59 +0100
From: Wilfried Weissmann <email address hidden>
CC: <email address hidden>
Subject: Re: iproute: "ip -4 neigh flush dev eth0" hangs up
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
Debian Bug Importer (debzilla) wrote : | #25 |
Message-ID: <email address hidden>
Date: Fri, 28 Jan 2005 14:00:37 +0100 (MET)
From: "Wilfried Weissmann" <email address hidden>
To: <email address hidden>, <email address hidden>, <email address hidden>,
<email address hidden>
Subject: multiple neighbour cache tables for AF_INET
--=====
Content-Type: text/plain; charset="us-ascii"
Content-
Hi,
The kernels 2.4.28+ and 2.6.9+ with IPv4 and ATM-CLIP enabled have bugs in
the neighbour cache code. neigh_delete() and neigh_add() only work properly
if one cache table per address family exist. After ATM-CLIP installed a
second cache table for AF_INET, neigh_delete() and neigh_add() only examine
the first table (the ATM-CLIP table if IPv4 and ATM-CLIP are compiled into
the kernel). neigh_dump_info() is also affected if the neigh_dump_table()
call fails.
This bug causes "ip neigh flush dev <some ethernet device>" to run into an
infinite loop when the arp cache is already populated (debian bug #282492).
"ip neigh delete ..." commands for non ATM-CLIP entries fail with an EINVAL.
This is because of the IPv4 neighbour table that is installed in arp.c is
never examined when sending delete commands.
I have attached a minimally tested patch for 2.4.28 that fixes this problem.
Greetings,
Wilfried
--
10 GB Mailbox, 100 FreeSMS http://
+++ GMX - die erste Adresse f�l, Message, More +++
--=====
Content-Type: text/x-diff; name="neighbour
Content-
Content-
LS0tIGxpbnV4LTI
IDIwMDUKKysrIGx
IDEzOjIyOjA2IDI
dWN0IHNrX2J1ZmY
aWx5KQogCQkJY29
ZXJyID0gLUVJTlZ
MTggKzEzNTksMjg
CiAJCWlmIChuZG0
dGUodGJsLCBSVEF
CWlmKGVycikgewo
CQl9CisJCQllbHN
TlVMTCkKLQkJCXJ
b3V0OworCQl9CiA
LTFdKSwgZGV2KTs
VURfRkFJTEVELCA
CQljb250aW51ZTs
YWRfdW5sb2NrKCZ
CiAJCXJldHVybiB
dCBza19idWZmICp
Y3QgbmVpZ2hfdGF
bnQgZXJyID0gLUV
Debian Bug Importer (debzilla) wrote : | #26 |
Message-Id: <email address hidden>
Date: Sat, 29 Jan 2005 09:19:49 +1100
From: Herbert Xu <email address hidden>
To: <email address hidden> (Wilfried Weissmann)
Cc: <email address hidden>, <email address hidden>, <email address hidden>,
<email address hidden>
Subject: Re: multiple neighbour cache tables for AF_INET
Wilfried Weissmann <email address hidden> wrote:
>
> The kernels 2.4.28+ and 2.6.9+ with IPv4 and ATM-CLIP enabled have bugs in
> the neighbour cache code. neigh_delete() and neigh_add() only work properly
> if one cache table per address family exist. After ATM-CLIP installed a
> second cache table for AF_INET, neigh_delete() and neigh_add() only examine
> the first table (the ATM-CLIP table if IPv4 and ATM-CLIP are compiled into
> the kernel). neigh_dump_info() is also affected if the neigh_dump_table()
> call fails.
Indeed, this has been the case for a very long time.
IMHO you need to give the user a way to specify which table they want
to operate on. If they don't specify one, then the current behaviour
of choosing the first table found is reasonble.
Cheers,
--
Visit Openswan at http://
Email: Herbert Xu ~{PmV>HI~} <email address hidden>
Home Page: http://
PGP Key: http://
Debian Bug Importer (debzilla) wrote : | #27 |
Message-Id: <email address hidden>
Date: Sat, 29 Jan 2005 07:46:05 +0900 (JST)
From: YOSHIFUJI Hideaki / =?iso-2022-
To: <email address hidden>
Cc: <email address hidden>, <email address hidden>, <email address hidden>, <email address hidden>,
<email address hidden>, <email address hidden>
Subject: Re: multiple neighbour cache tables for AF_INET
In article <email address hidden> (at Sat, 29 Jan 2005 09:19:49 +1100), Herbert Xu <email address hidden> says:
> IMHO you need to give the user a way to specify which table they want
> to operate on. If they don't specify one, then the current behaviour
> of choosing the first table found is reasonble.
We have dev. Isn't is sufficient?
--yoshfuji
Debian Bug Importer (debzilla) wrote : | #28 |
Message-ID: <email address hidden>
Date: Sat, 29 Jan 2005 21:06:56 +1100
From: Herbert Xu <email address hidden>
To: "YOSHIFUJI Hideaki / ?$B5HF#1QL@" <email address hidden>
Cc: <email address hidden>, <email address hidden>, <email address hidden>, <email address hidden>,
<email address hidden>
Subject: Re: multiple neighbour cache tables for AF_INET
On Sat, Jan 29, 2005 at 07:46:05AM +0900, YOSHIFUJI Hideaki / ?$B5HF#1QL@ wrote:
> In article <email address hidden> (at Sat, 29 Jan 2005 09:19:49 +1100), Herbert Xu <email address hidden> says:
>
> > IMHO you need to give the user a way to specify which table they want
> > to operate on. If they don't specify one, then the current behaviour
> > of choosing the first table found is reasonble.
>
> We have dev. Isn't is sufficient?
It could be used for neigh_add/
to query whether a given table is the right one for a device.
For dump it isn't the same. However, perhaps it's not too important
to query a specific table.
Cheers,
--
Visit Openswan at http://
Email: Herbert Xu ~{PmV>HI~} <email address hidden>
Home Page: http://
PGP Key: http://
Debian Bug Importer (debzilla) wrote : | #29 |
Message-Id: <email address hidden>
Date: Fri, 01 Jul 2005 01:26:47 +0100
From: Luke Kenneth Casson Leighton <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: iproute: removing modules, ifup down up down kill ip _eventually_ succeeds
Package: iproute
Version: 20041019-3
Severity: normal
Followup-For: Bug #282492
one million and increasing attempts to flush eth0.
this is what i am using (in combination with fwbuilder) to attempt
to get round of the problem. it is not successful always but can be
eventually successful after killing /sbin/ip and re-running the script,
repeat until success.
#!/bin/sh
iptables -F
iptables -X
ifdown eth0
ifdown eth1
rmmod ip6table_filter
rmmod ip6_tables
rmmod ipt_LOG
rmmod ipt_state
rmmod ip_nat_tftp
rmmod ip_nat_snmp_basic
rmmod ip_nat_irc
rmmod ip_nat_ftp
rmmod ip_nat_amanda
rmmod iptable_nat
rmmod ip_conntrack_tftp
rmmod ip_conntrack_
rmmod ip_conntrack_irc
rmmod ip_conntrack_ftp
rmmod ip_conntrack_amanda
rmmod ip_conntrack
rmmod iptable_filter
rmmod ipt_REDIRECT
sleep 1
rmmod tulip
rmmod 3c59x
modprobe tulip
modprobe 3c59x
sleep 1
ifup eth0
ifup eth1
ip -4 neigh flush dev eth0
ip -4 neigh flush dev eth1
sleep 1
ifdown eth0
ifdown eth1
sleep 1
ifup eth0
ifup eth1
sh /etc/fwbuilder.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux highfield 2.6.11-1-686 #1 Fri May 20 07:34:54 UTC 2005 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages iproute depends on:
ii libatm1 2.4.1-16 shared library for ATM (Asynchrono
ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an
-- no debconf information
Debian Bug Importer (debzilla) wrote : | #30 |
Message-Id: <email address hidden>
Date: Wed, 17 Aug 2005 19:19:32 +0200
From: Piotr Roszatycki <email address hidden>
To: <email address hidden>
Subject: Re: iproute: "ip -4 neigh flush dev eth0" hangs up
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 Roszatycki, Netia SA
: :' : mailto:<email address hidden>
`. `' mailto:<email address hidden>
`-
Debian Bug Importer (debzilla) wrote : | #31 |
Message-ID: <email address hidden>
Date: Wed, 17 Aug 2005 23:18:08 +0200
From: Herbert Straub <email address hidden>
To: <email address hidden>
Subject: iproute: "ip -4 neigh flush dev eth0" hangs up
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. Some vendors added a check for getuid() != 0, but that
fails in secure environments with capabilities and no root user.
I'll probably just change it to try 10 times and give up.
I isolate his changes and create this patch
--- ip/ipneigh.c.ORIG 2005-08-17 22:11:06.000000000 +0200
+++ ip/ipneigh.c 2005-08-17 22:13:02.000000000 +0200
@@ -31,6 +31,7 @@
#include "ip_common.h"
#define NUD_VALID
(NUD_PERMANENT|
+#define MAX_ROUNDS 10
static struct
{
@@ -411,7 +412,7 @@
filter.rth = &rth;
- for (;;) {
+ while (round < MAX_ROUNDS) {
if (rtnl_wilddump_
RTM_GETNEIGH) < 0) {
@@ -437,6 +438,9 @@
}
}
+ printf("*** Flush not complete bailing out after %d rounds\n",
+ MAX_ROUNDS);
+ return 1;
}
if (rtnl_wilddump_
The modified iproute package for Ubuntu Hoary (and i think you can easy
rebuild it for Debian) are available under:
http://
More details in the Ubuntu Bug #15413
(https:/
Best regards
Herbert Straub
Changed in iproute: | |
assignee: | nobody → dsilvers |
status: | Unconfirmed → Confirmed |
Daniel Silverstone (dsilvers) wrote : | #32 |
Accepted:
OK: iproute_
-> Component: main Section: net
OK: iproute_
Format: 1.7
Date: Thu, 13 Apr 2006 11:41:34 +0100
Source: iproute
Binary: iproute-dev iproute
Architecture: source
Version: 20041019-4ubuntu2
Distribution: dapper
Urgency: low
Maintainer: Anibal Monsalve Salazar <email address hidden>
Changed-By: Daniel Silverstone <email address hidden>
Description:
iproute - Professional tools to control the networking in Linux kernels
iproute-dev - Development package for iproute
Changes:
iproute (20041019-4ubuntu2) dapper; urgency=low
.
* Ensure that flushing the neighbour cache does not infinite-loop if an
unprivileged process attempts the flush.
Also ensure the same is true of the address cache.
Closes: launchpad #16137
Files:
636af651750d2c
ec0575c797b7ea
Changed in iproute: | |
status: | Confirmed → Fix Released |
In Debian Bug tracker #282492, maximilian attems (maks-debian) wrote : tagging 282492 | #33 |
# Automatically generated email from bts, devscripts version 2.9.20
tags 282492 - help unreproducible
Changed in iproute: | |
status: | Confirmed → Unconfirmed |
In Debian Bug tracker #282492, maximilian attems (maks-debian) wrote : higher severity | #34 |
severity 282492 important
In Debian Bug tracker #282492, Alexander Wirt (formorer) wrote : This bug already has been fixed | #35 |
Hi,
I applied the patch from Herbert Straub some time ago, but missed to close
this bug.
Alex
Changed in iproute: | |
status: | Unconfirmed → Fix Released |
tag 282492 + unreproducible help
thanks
Hi,
this problem is not reproducible for me, at least not with the current
version -1.
The bad thing is also that I don't have any idea how to fix it, so this
means that I need help.
Cheers, home.arcor. de/andreas- barth/
Andi
--
http://
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C