X-Spam-Check-By: sourceware.org
Message-ID: <242f7d730602010836m7f81fc56yb6303e6b8576dfc2@mail.gmail.com>
Date: Wed, 1 Feb 2006 08:36:58 -0800
From: Jon Dixon <solvang.j2@gmail.com>
To: cygwin@cygwin.com
Subject: Re: SSH Local Port Forwarding
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k11GbKc9027892

Hi Corinna,

   Thanks for all the consideration you have given this WinSock
problem.  As a suggestion, would it be possible to add an ssh command
line option, so the user could explicitly open the listening port in
exclusive mode.  This would alleviate the problem of trying to second
guess when to use SO_EXCLUSIVEADDRUSE and when to use SO_REUSEADDR.

     For example:
         ssh -L2001:server.com:23  -o "ExclusivePort yes"  server.com

Thanks again

Jon

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/