Date: Wed, 21 Jul 2004 17:24:33 -0400 From: Thomas_Knight@adp.com To: freebsd-questions@freebsd.org Cc: Scott@isdr.net Subject: RE: VNC on different port Message-ID: <CFF33B8F292FB244B09B77BAE221FF00F0B858@ROSEEXCHMF>
next in thread | raw e-mail | index | archive | help
How would I set up the encrypted port tunneling?
Thomas G. Knight
ADP - Data Center Team
thomas_knight@adp.com
(801) 956-7449
Don't worry if you're a kleptomaniac, you can always take something for it.
-- Unknown
-----Original Message-----
From: Bill Moran [mailto:wmoran@potentialtech.com]
Sent: Wednesday, July 21, 2004 1:59 PM
To: Thomas_Knight@adp.com
Cc: freebsd-questions@freebsd.org; Scott@isdr.net
Subject: Re: VNC on different port
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CFF33B8F292FB244B09B77BAE221FF00F0B858>