From: Casey Carter <ccarter@cs.uiuc.edu>
To: Matthias Andree <matthias.andree@gmx.de>
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>,
linux-net@vger.kernel.org
Subject: Re: [2.4.2X] "Undeletable" ARP entries?
Date: Wed, 20 Aug 2003 09:56:50 -0500 [thread overview]
Message-ID: <3F438C32.3070705@cs.uiuc.edu> (raw)
In-Reply-To: <20030820113208.GA11163@merlin.emma.line.org>
Matthias Andree wrote:
>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
>
>
>
Try "arp -i eth1 -d 192.168.4.4 pub"
--
Casey Carter
Casey@Carter.net
ccarter@cs.uiuc.edu
AIM: cartec69
next prev parent reply other threads:[~2003-08-20 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 11:32 [2.4.2X] "Undeletable" ARP entries? Matthias Andree
2003-08-20 11:34 ` Matthias Andree
2003-08-20 14:56 ` Casey Carter [this message]
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=3F438C32.3070705@cs.uiuc.edu \
--to=ccarter@cs.uiuc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=matthias.andree@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.