Random datapoint: it does this on Road Runner cable modems in Austin, too
(2.2.17 or so did, anyway. Haven't had a monitor physically hooked up to my
old 486 gateway since I moved it to 2.4). Basically any cable modem that
acts like a hub instead of a router (letting all packets through instead of
just the one for the mac address it's connected to).
I made it go away somehow (~6 months back). Possibly deselecting all the ARP
stuff when I recompiled, I honestly don't remember at this point. 2.4 never
did it (that I saw), but I compiled that sucker myself and don't log into my
gateway much (it's a dumb ip masquerader running no daemons) so...
> In general these segments are extremely large and due to the
> nature of the users, can cause large amounts of arp broadcast
> traffic during peak times.
Forget peak times. It did this 24/7 for me.
Bloated the logs something fierce. I vaguely remember looking in the source
and finding the message and going "so why doesn't it just delete something
out of the neighbor table then?" Never did figure that one out. (It
happened when the machine wasn't actually in USE, just connected to the net
but otherwise idle. No connections masquerading through it, nothing...)
Rob
-
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/