Bug#282492: iproute: "ip -4 neigh flush dev eth0" hangs up

2005-01-19 Thread Wilfried Weissmann
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]

Bug#282492: iproute: "ip -4 neigh flush dev eth0" hangs up

2005-01-20 Thread Wilfried Weissmann
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".

Bug#282492: iproute: "ip -4 neigh flush dev eth0" hangs up

2005-01-25 Thread Wilfried Weissmann
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 "unsubscrib

Bug#282492: multiple neighbour cache tables for AF_INET

2005-01-28 Thread Wilfried Weissmann
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 exa

Bug#282492: iproute: "ip -4 neigh flush dev eth0" hangs up

2005-01-11 Thread Wilfried Weissmann
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 2004101

Bug#277534: still able to reproduce this bug?

2007-03-06 Thread Wilfried Weissmann
On Sarge + Backports I worked around this issue by setting udev rules: # ignore partitions of disk within dmraid volumes BUS=="ide", KERNEL=="hd[ge][0-9]*", OPTIONS+="ignore_device", OPTIONS+="last_rule" On Testing I do get "trying to access beyond the end of device" errors. I do not use the u