[40312] in North American Network Operators' Group
RE: TCP session disconnection caused by Code Red?
daemon@ATHENA.MIT.EDU (Blaz Zupan)
Tue Aug 7 00:47:25 2001
Date: Tue, 7 Aug 2001 06:45:19 +0200 (CEST)
From: Blaz Zupan <blaz@amis.net>
To: James Smith <jsmith@PRESIDIO.com>
Cc: <nanog@merit.edu>
In-Reply-To: <171DAAD54475984F8F41345A0945DF9C05A307@hqexchange.presidio.com>
Message-ID: <20010807064424.A93751-100000@titanic.medinet.si>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
> I can see "connection refused" being caused by lack of resources (memory,
> not CPU) caused by ARP requests not being resolved and waiting to time out.
Ok, I can see that everbody is comming up with this idea. But this does not
explain why *all other* connections through this same router work just fine.
Only incoming connections from our upstream fail. And no, there were not many
outstanding ARP requests.
Blaz Zupan, Medinet d.o.o, Trzaska 85, SI-2000 Maribor, Slovenia
E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325
