Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Tue, 8 Jan 2002 14:48:58 -0500 From: Jason Tishler To: cygwin@cygwin.com Cc: CyberZombie , gotoh@taiyo.co.jp Subject: Re: How do I use a socks server with cygwin? Message-ID: <20020108194857.GE2136@dothill.com> Mail-Followup-To: cygwin@cygwin.com, CyberZombie , gotoh@taiyo.co.jp References: <20011220132712.GB2396@dothill.com> <3C22012F.2040407@mediaone.net> <20011220190116.GA1472@dothill.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011220190116.GA1472@dothill.com> User-Agent: Mutt/1.3.24i On Thu, Dec 20, 2001 at 02:01:20PM -0500, Jason Tishler wrote: > On Thu, Dec 20, 2001 at 09:18:07AM -0600, CyberZombie wrote: > > Can you elaborate how you did this? > > Once the Hummingbird SOCKS proxy software is installed, all that you need > to do is create a socks.cnf file. See attached for a sample. This it! > You are done! It's that easy! > > If you are looking for just a ssh/SOCKS solution then try the following: > > http://www.imasy.or.jp/~gotoh/ssh/connect.c > > This is what I used before I found the generic Hummingbird solution. Thanks to the @Home to Comcast conversion, I have obtained empirical evidence that Shun-ichi GOTO's ssh specific solution is *much* better than the Hummingbird generic SOCKS solution (at least for ssh). Even though I use the Hummingbird solution for everything else, I was still using connect because I perceived it to be faster, have less latency, and be more robust. Although, given the generally poor performance of my company's SOCKS server, it was hard to be sure. I forgot to change my .ssh/config file to reflect my new IP address due to the @Home conversion. Hence, for the last few days I was unknowingly using Hummingbird instead of connect. I was very unhappy with the horrible performance. Then I realized that I was not using connect. Once I fixed my .ssh/config file and started using connect again, my SOCKS/ssh performance returned to the pre-conversion levels. I would like to publicly thank Shun-ichi GOTO for providing this valuable tool. Jason -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/