From owner-freebsd-questions@FreeBSD.ORG Wed Jul 21 19:58:46 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FCA016A4CE for ; Wed, 21 Jul 2004 19:58:46 +0000 (GMT) Received: from internet.potentialtech.com (h-66-167-251-6.phlapafg.covad.net [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 480F343D45 for ; Wed, 21 Jul 2004 19:58:46 +0000 (GMT) (envelope-from wmoran@potentialtech.com) Received: from working.potentialtech.com (pa-plum-cmts1e-68-68-113-64.pittpa.adelphia.net [68.68.113.64]) by internet.potentialtech.com (Postfix) with ESMTP id 38E2869A3F; Wed, 21 Jul 2004 15:58:45 -0400 (EDT) Date: Wed, 21 Jul 2004 15:58:44 -0400 From: Bill Moran To: Thomas_Knight@adp.com Message-Id: <20040721155844.74dd1a29.wmoran@potentialtech.com> In-Reply-To: References: Organization: Potential Technologies X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: Scott@isdr.net cc: freebsd-questions@freebsd.org Subject: Re: VNC on different port X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 19:58:46 -0000 Thomas_Knight@adp.com wrote: > My configuration is as follows: > > ------- ----------- ----------------- ------ > | VNC | --- --- | FreeBSD | --- --- | Work Firewall | --- --- | ME | > ------- ----------- ----------------- ------ > > I am trying to redirect ports so I can get out through my works firewall > into my VNC Server. I can get it to work on port 8080 but not on 80 or 20 or > 21. My work only allows 20, 21, 22, 80 through the firewall. Please see the > example below. > > This does work: > redirect_port tcp 10.0.3.21:5900 166.70.126.172:8080 > This does not work: > redirect_port tcp 10.0.3.21:5900 166.70.126.172:80 > > Any one have any idea's? If your work uses a transparent proxy for port 80, it's going to see the VNC traffic as invalid HTTP data and probably mangle it or drop it. You'd actually be better off using ssh to do encrypted port tunnelling, since your firewall allows it already. Running VNC unencrypted across the Internet is dangerous. Either way, try one of the other available ports. Port 22 unlikely to be proxied in any case. -- Bill Moran Potential Technologies http://www.potentialtech.com