Date: Fri, 6 Oct 2000 14:16:02 -0700 (PDT) From: jd@dynw.com To: freebsd-gnats-submit@FreeBSD.org Subject: kern/21791: Hang on FIN_WAIT_2 Message-ID: <20001006211602.3576C37B502@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 21791 >Category: kern >Synopsis: Hang on FIN_WAIT_2 >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Oct 06 14:20:00 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Jim Dogopoulos >Release: 4.1.1-S 3.5-S BSDi >Organization: dwc >Environment: >Description: Connecting to certain machines tcp stacks causes hang on FIN_WAIT_2, which never times out. >How-To-Repeat: telnet 216.105.145.50 80 and quit. It is a Novell-HTTP-Server/3.1R1 server. look at netstat, FIN_WAIT_2 will stay. It gets worse though, I wrote some code to initiate >2048 connections, which filled up the mbufs on the fbsd-3.5-s test machine (4.x will obviously behave differently), and permanently denied further connections until reboot. This could possibly be used as a local DoS attack from an ordinary user on a shell server, but at the least, the occasional hung FIN_WAIT_2s are annoying to look at... >Fix: Perhaps timeout FIN_WAIT_2 sometime? >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001006211602.3576C37B502>