From owner-freebsd-net Tue Feb 5 6:32:16 2002 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 2BF6D37B433 for ; Tue, 5 Feb 2002 06:32:11 -0800 (PST) Received: from localhost (kame201.kame.net [203.178.141.201]) by shuttle.wide.toshiba.co.jp (8.11.6/8.9.1) with ESMTP id g15EVv359385; Tue, 5 Feb 2002 23:31:58 +0900 (JST) Date: Tue, 05 Feb 2002 23:31:52 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Ian Dowse Cc: freebsd-net@FreeBSD.ORG Subject: Re: `options INET6' allows duplicate IPv4 binding In-Reply-To: <200201211436.aa82109@salmon.maths.tcd.ie> References: <200201211436.aa82109@salmon.maths.tcd.ie> User-Agent: Wanderlust/2.7.5 (Too Funky) Emacs/21.1 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 31 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, >>>>> On Mon, 21 Jan 2002 14:36:35 +0000, >>>>> Ian Dowse 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