From: Matthias Andree <matthias.andree@gmx.de>
To: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Cc: linux-net@vger.kernel.org
Subject: [2.4.2X] "Undeletable" ARP entries?
Date: Wed, 20 Aug 2003 13:32:08 +0200 [thread overview]
Message-ID: <20030820113208.GA11163@merlin.emma.line.org> (raw)
Hi,
I have strange ARP behaviour here, that I can reproduce. Might be a
kernel bug.
SHORT: I can use the "arp" tool to set an ARP entry that the "arp" tool
cannot delete and that hides from "ip"'s view. I know a workaround (at
the very end of the mail).
LONG:
Use either of:
SuSE 2.4.20 kernel for 8.2 (k_athlon-2.4.20-96)
or 2.4.22-rc2-ac1
(I haven't tried any other version)
Use this tool:
$ arp -V
net-tools 1.60
arp 1.88 (2001-04-04)
+I18N
AF: (inet) +UNIX +INET +INET6 +IPX +AX25 +NETROM +X25 +ATALK -ECONET -ROSE
HW: (ether) +ETHER +ARC +SLIP +PPP +TUNNEL +TR +AX25 +NETROM +X25 +FR -ROSE -ASH +SIT +FDDI +HIPPI -HDLC/LAPB
Now type (192.168.4.4 isn't available, I would like to use it as SNAT
source):
$ arp -Ds 192.168.4.4 eth1 pub
This entry cannot be deleted:
$ arp -d 192.168.4.4
SIOCDARP(priv): Network is unreachable
(even if a route for 192.168.4.4 is set, the entry isn't removed)
$ arp -d 192.168.4.4 pub
SIOCDARP(pub): No such file or directory
The interesting part is: The address doesn't show up in netlink,
$ ip -s neigh show nud all | grep 4.4
$
(no output)
/proc/net/arp excerpt:
IP address HW type Flags HW address Mask Device
192.168.4.4 0x1 0xc 00:00:00:00:00:00 * eth1
This doesn't work either:
$ ip neigh d 192.168.4.4 dev eth1
RTNETLINK answers: Invalid argument
$ ip neigh flush dev eth1
Nothing to flush.
This appears to be a kernel bug, unless I missed documentation on how to
remove such an ARP entry.
WORKAROUND:
$ ip addr add 192.168.4.4 dev eth1
$ ip addr del 192.168.4.4 dev eth1
Now the arp entry is gone, probably as a side effect of taking down
resources related to 192.168.4.4.
HOWEVER: the ARP entry was supposed to be permanent, so it may be
another bug that the entry is gone after removing an IP alias.
Anyone got ideas or patches to try?
--
Matthias Andree
next reply other threads:[~2003-08-20 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 11:32 Matthias Andree [this message]
2003-08-20 11:34 ` Matthias Andree
2003-08-20 14:56 ` Casey Carter
2003-08-20 16:25 ` Matthias Andree
2003-08-20 17:33 ` Bernd Eckenfels
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030820113208.GA11163@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®