Messages in this thread | | | Date | Wed, 7 Jul 2004 00:08:12 +0200 | From | Carsten Otto <> | Subject | Re: possible arp table corruption [2.4.18] |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |