delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2006/02/01/11:37:21

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 DOT j2 AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: SSH Local Port Forwarding
MIME-Version: 1.0
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
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/


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019