From: Paul Sladen (vserver_at_paul.sladen.org)
Date: Wed 09 Oct 2002 - 08:12:57 BST
On Tue, 8 Oct 2002, Justin M Kuntz wrote:
> Oct 8 18:29:42 kernel: NET: 199 messages suppressed.
> Oct 8 18:29:42 kernel: Neighbour table overflow.
> RX packets:6673856 errors:0 dropped:0 overruns:110 frame:0
> TX packets:229078704 errors:0 dropped:0 overruns:0 carrier:0
> RX bytes:809848397 (772.3 MB) TX bytes:1863256636 (1776.9 MB)
> There are a HUGE number of transmit packets in only 3 days of uptime.
The messages relating to these from Googleing are mostly related to `ARP'
requests (something to do with ``buckets being full'' :-). The /traffic/
out is not very high at all, although as you say the number of packets /is/,
lots of small `ARP' packets would be causing this.
I haven't found any firm answers and my next step would be reading the
kernel source to find what paths lead to the error. Somebody mentioned lots
of UDP packets being pushed at an interface that isn't fully up yet might
cause it? I haven't looked yet, but I'm guess you want to start grepping
This madness has been reported else-where, so is /probably not `vserver'
specific/. My best [and probably useless?] suggestion is changing the NIC
to a different card/brand and swapping the switch port if this is possible.
Check that it is auto-configuring OK aswell.
Hope that helps, keep us informed!
-- Nottingham, GB