From: Carsten Otto <carsten.otto@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: possible arp table corruption [2.4.18]
Date: Wed, 7 Jul 2004 00:08:12 +0200 [thread overview]
Message-ID: <13e9886104070615087452e595@mail.gmail.com> (raw)
I switched to read("/proc/net/arp") in my script and basically have no
difference.
Today I found following "nice" bug:
134.130.48.70 0x1 0x2 00:E0:98:AD:01:97 * eth0
134.130.48.157 0x1 0x2 00:10:4B:4D:01:97 * eth0
134.130.48.157 0x1 0x2 00:10:4B:45:86:6C * eth0
These three entries appeared near the end of the output and had no
lines between them. Notice how the second MAC is composed from the
other two. The first and last entry is correct. If my database and
script etc. work correct, this (wrong) second combination occured at
least five times, but only one of them showed up today.
Where is the bug? What should I do to avoid this?
Thanks,
--
Carsten Otto
carsten.otto@gmail.com
http://c-otto.de
next reply other threads:[~2004-07-06 22:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 22:08 Carsten Otto [this message]
2004-07-07 7:23 ` possible arp table corruption [2.4.18] Bernd Eckenfels
-- strict thread matches above, loose matches on Subject: below --
2004-06-29 20:05 Carsten Otto
2004-06-29 21:15 ` Bernd Eckenfels
2004-06-29 22:29 ` 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=13e9886104070615087452e595@mail.gmail.com \
--to=carsten.otto@gmail.com \
--cc=linux-kernel@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