Date: Tue, 05 Feb 2002 23:31:52 +0900 From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp> To: Ian Dowse <iedowse@maths.tcd.ie> Cc: freebsd-net@FreeBSD.ORG Subject: Re: `options INET6' allows duplicate IPv4 binding Message-ID: <y7vheowdmp3.wl@condor.jinmei.org> In-Reply-To: <200201211436.aa82109@salmon.maths.tcd.ie> References: <200201211436.aa82109@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, >>>>> On Mon, 21 Jan 2002 14:36:35 +0000, >>>>> Ian Dowse <iedowse@maths.tcd.ie> said: > I was just trying to track down a weird behaviour I had observed > involving VNC and sshd. When a user logs in via sshd, their $DISPLAY > would often end up being the same as that of an existing Xvnc > session: >> sockstat | grep 6013 |grep '\*' > root sshd 25710 7 tcp4 *:6013 *:* > userX Xvnc 51102 0 tcp4 *:6013 *:* > root sshd 25710 6 tcp46 *:6013 *:* > As you can see, sshd has successfully bound its tcp4 socket to the > same wildcard address as Xvnc was already using, but sshd does not > set any of the SO_REUSE* options. It seems that this is caused by > the following code in in_pcb.c: Sorry for the delayed response, you are basically correct (I believe sshd should set SO_REUSEADDR, but that is not relevant to this problem). We (the KAME developers) have recognized this bug, and are now trying to fix it. I guess we can send a patch in a week or so. Thanks for your report, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?y7vheowdmp3.wl>