Re: arp table overflow due to windows worm

2004-10-17 Thread Russell Coker
On Mon, 18 Oct 2004 07:08, Rick Moen <[EMAIL PROTECTED]> wrote: > Quoting Jason Lunz ([EMAIL PROTECTED]): > > The entire neighbor cache was completely rewritten recently, and I > > believe it was prompted by exactly this sort of situation. > > Just wanted to mention: That "neigbour table overflow"

Re: arp table overflow due to windows worm

2004-10-17 Thread Rick Moen
Quoting Jason Lunz ([EMAIL PROTECTED]): > The entire neighbor cache was completely rewritten recently, and I > believe it was prompted by exactly this sort of situation. Just wanted to mention: That "neigbour table overflow" error can also be caused by inadvertantly removing the localhost line

Re: arp table overflow due to windows worm

2004-10-17 Thread Jason Lunz
[EMAIL PROTECTED] said: > 135 is closed in both directions. However, I get the message "Neighbour > table overflow" on the firewall (debian stable w/ kernel 2.4.27) and the > entire network comes to a standstill. The cpu load isn't even close to a ... > Should it really be possible for a single inf