Date: Thu, 19 Nov 1998 11:54:43 -0500 (EST) From: Mikhail Teterin <mi@video-collage.com> To: questions@FreeBSD.ORG Subject: binding fails if there is FIN_WAIT2 on this port Message-ID: <199811191654.LAA13163@xxx.video-collage.com>
next in thread | raw e-mail | index | archive | help
Hello! I'm having the following problem, but can not say for sure if it's a bug due to my poor knowledge of TCP/IP. Example1: We have something like while (1) ssh -L 3129:host.on.fast.link:3128 host.on.fast.link sleep 3 end running on ttyv6 (better solutions, that will not need a tty are welcome). This allows to set HTTP_PROXY to localhost:3129 in, say, Netscape. Unfortunately, when ssh dies for some reason, such as modem disconnects for too long, the new instance of ssh can not bind to the port 3129, because it is "in use". The only mention of it in netstat's output is for a FIN_WAIT2 connection, which goes away when Netscape is told to look for proxy elsewhere or to use direct connection. Example2: Ftp server, with ftpd being spawned from xinetd. If the ftp client (from another host) dies, there may be a FIN_WAIT2 connection to the server's ftp port on the client. If I try to kill and restart xinetd on the server it will fail to bind to the ftp port. inetd does not have this problem and is not affected by some other machine having FIN_WAIT2 connection to its ftp port. I'd appreciate if someone could comment on this, since I'm not sure if this is really PR-able. TIA! -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811191654.LAA13163>