Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
Date:	13 Nov 2001 13:17:26 -0500
Message-ID:	<20011113181726.5229.qmail@lizard.curl.com>
From:	Jonathan Kamens <jik AT curl DOT com>
To:	jik AT curl DOT com
CC:	cygwin-developers AT cygwin DOT com
In-reply-to:	<20011113174525.4108.qmail@lizard.curl.com> (message from
	Jonathan Kamens on 13 Nov 2001 12:45:25 -0500)
Subject:	Re: "Address already in use" error from ssh with current Cygwin installation
References:	<20011113174525 DOT 4108 DOT qmail AT lizard DOT curl DOT com>

>  Date: 13 Nov 2001 12:45:25 -0500
>  From: Jonathan Kamens <jik AT curl DOT com>
>  
>  When I peruse fhandler_socket.cc, it appears to me that the code is
>  randomly assigning a local port number to a socket during connect.

On further examination, it appears that I was wrong.  The random port
number stuff is only used for AF_UNIX sockets, and in this case we're
dealing with an AF_INET socket, so that code shouldn't be relevant.

As far as I can tell, for AF_INET sockets, Cygwin lets WININET assign
the local port number if one isn't explicitly specified by the calling
program.  If that's correct, then is this problem a WININET bug --
it's assigning a local port number when that port number is already in
use?  And if so, then what has changed in the Cygwin DLL to cause this
problem to start showing up when it wasn't before?

I'm continuing to investigate, but if anybody has any ideas, please
let me know....

Thanks,

  jik

- Raw text -