netdev
[Top] [All Lists]

Re: Neighbour Table Overflow

To: Frank Byrum <greatbridge.com@xxxxxxxxxxxxx>
Subject: Re: Neighbour Table Overflow
From: Mark Spencer <markster@xxxxxxxxxxxxxxxxx>
Date: Wed, 15 Nov 2000 16:39:07 -0600 (CST)
Cc: netdev@xxxxxxxxxxx
In-reply-to: <20001115.21335900@xxxxxxxxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
> 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.  

But why is the re-arp taking so long?  And I thought ARP entries lived
much longer than 15 seconds, more like a couple of minutes.  Can the time
be changed?  That's still not the solution, certainly.    Do arp entries
get their lives extended if they're used?

Perhaps what's happening is that the ethernet is getting overrun, and so
the ARP is getting dropped because the ethernet is flooded.  But shouldn't
an ARP have some sort of priority?

Mark


<Prev in Thread] Current Thread [Next in Thread>