netdev - Can not remove FAILED neigh entry??

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Tue, 17 Jun 2014 16:12:28 -0700
From:	Cong Wang <cwang@...pensource.com>
To:	netdev <netdev@...r.kernel.org>
Cc:	David Miller <davem@...emloft.net>,
	Stephen Hemminger <stephen@...workplumber.org>
Subject: Can not remove FAILED neigh entry??

Hi, all


I am wondering if the following behavior is expected, I can't
manually delete or flush a neigh entry:

[root@...alhost ~]# ip -s -s neigh show
192.168.122.1 dev eth0 lladdr 52:54:00:5e:f5:1e used 22/22/5 probes 4 STALE
[root@...alhost ~]#
[root@...alhost ~]# ip neigh del 192.168.122.1 dev eth0
[root@...alhost ~]# ip -s -s neigh show
192.168.122.1 dev eth0  used 34/34/17 probes 4 FAILED
[root@...alhost ~]# ip -s -s neigh flush all
Nothing to flush.
[root@...alhost ~]# ip -s -s neigh show
192.168.122.1 dev eth0  used 42/42/26 probes 4 FAILED
[root@...alhost ~]# sleep 60
[root@...alhost ~]# ip -s -s neigh show
192.168.122.1 dev eth0  used 130/130/113 probes 4 FAILED

I thought it would timeout (gc_stale_time) after it becomes FAILED,
but apparently it is still there after a long time. If this is what we expect,
then what's the right way to remove an entry from a neigh table manually?


Thanks!
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html