Re: VNC on different port
[EMAIL PROTECTED] wrote: How would I set up the encrypted port tunneling? Something like: ssh -L 5900:your.host.name:5900 your.host.name should work. You can then connect to port 5900 on the local machine, and it will be forwarded to your.host.name. Note also that you can forward X11 connections like this as well. The ssh man page has more. With your setup, you'll still need the nat forwarding on the FreeBSD firewall, unless you're able to ssh directly to the machine running vnc. Thomas G. Knight ADP - Data Center Team [EMAIL PROTECTED] (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:[EMAIL PROTECTED] Sent: Wednesday, July 21, 2004 1:59 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: VNC on different port [EMAIL PROTECTED] 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
VNC on different port
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? Thanks, Thomas ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VNC on different port
[EMAIL PROTECTED] 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: VNC on different port
How would I set up the encrypted port tunneling? Thomas G. Knight ADP - Data Center Team [EMAIL PROTECTED] (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:[EMAIL PROTECTED] Sent: Wednesday, July 21, 2004 1:59 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: VNC on different port [EMAIL PROTECTED] 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
