From: Simon Kelley <simon@thekelleys.org.uk>
To: netdev@vger.kernel.org
Subject: Please explain this ARP behaviour.
Date: Wed, 26 Apr 2006 12:58:30 +0100 [thread overview]
Message-ID: <444F6066.8020805@thekelleys.org.uk> (raw)
Two machines, many configuration differences, I need to find which one
is causing this difference in behaviour:
Machine 1: (eth1 is on the correct 192.168.3.x network)
# ip neighbour add to 192.168.2.15 lladdr 00:0F:20:98:F8:86 nud \
reachable dev eth1
# cat /proc/net/arp
IP address HW type Flags HW address Mask
Device
192.168.0.4 0x1 0x2 00:00:F8:04:9B:69 * eth0
192.168.2.15 0x1 0x2 00:0F:20:98:F8:86 * eth1
192.168.2.148 0x1 0x2 00:10:A4:F2:CF:CB * eth1
# ip neighbour show
192.168.0.4 dev eth0 lladdr 00:00:f8:04:9b:69 nud reachable
192.168.2.15 dev eth1 lladdr 00:0f:20:98:f8:86 nud reachable
192.168.2.148 dev eth1 lladdr 00:10:a4:f2:cf:cb nud stale
Note that hand-created entry appears in /proc and ip .. show
Machine 2: (similarly correct network)
# ip neighbour add to 192.62.204.15 lladdr 00:0F:20:98:F8:86\
nud reachable dev eth1
IP address HW type Flags HW address Mask
Device
193.62.204.1 0x1 0x2 00:0F:20:98:F8:87 * eth1
# ip neighbour show
192.62.204.15 dev eth1 lladdr 00:0f:20:98:f8:86 nud reachable
193.62.204.1 dev eth1 lladdr 00:0f:20:98:f8:87 nud stale
Here, hand-created interface is in ip .. show, but missing from /proc
There is some reason to believe that the functional ARP behaves as
/proc/net/arp (ie the hand-created entry is ignored) but I don't have
absolute proof of that yet.
Machine 1 (works) is 2.6.12.2 hand compiled
Machine 2 (broken) is Ubunutu's 2.6.10-5-386, but this has possibly been
seen in Debian 2.6.16.2 as well.
Please could someone suggest where I look next?
Cheers,
Simon.
reply other threads:[~2006-04-26 11:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=444F6066.8020805@thekelleys.org.uk \
--to=simon@thekelleys.org.uk \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).