I have noticed something like this which seems to be related to the ARP
cache entry expiring and so the packet can not be delivered. This
usually happens somewhere between 12 and 15 seconds. If you hardcode the
ARP entries the problems goes away.
BTW, how long does an ARP entry live in the cache?
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 11/15/00, 1:33:20 PM, Mark Spencer <markster@xxxxxxxxxxxxxxxxx> wrote
regarding Neighbour Table Overflow:
> I've been running some tests on an x86 Linux based router with basically
> an AMD 486 DX4-100 processor and two PCNet32 ethernet controllers.
> The kernel on the router is 2.2.17 with "optimize as router".
> For these tests, I'm using netperf (tcp stream test) running on two PC's,
> and asking the router in the middle to forward the packets between the
> After delivering packets successfully for about 15 seconds, the unit will
> cease to respond to packets for several seconds. The only clue that I
> have to the source of the problem is that I receive the message
> table overflow". My understanding of the neighbour table is that it is
> used primarily for ARP'ing. If so, this is a surprising message since
> router should only be aware of one machine on each subnet, and indeed if
> cat /proc/net/arp I see only the two machines.
> Does anyone have any suggestions at what to look for?