Doug Poland wrote:
Okay, I see how I can use ssh/sshd running on the FreeBSD gateways onDarren Pilgrim said:I want to setup VNC on some Windows machines so I can access them over the internet, but I need to secure the connection in a way that will work with NAT'ing firewalls on both ends of the connection. How can I do this? I was thinking of setting up a tunnel between the two firewalls. On the local end, the tunnel starts at a given port on the firewall, which is connected to a port on the remote firewall that forwards to the VNC port on the remote machine. How would I go about doing this? Is there a better option?I recommend you use the TightVNC form of VNC. Read the info on this link: http://www.uk.research.att.com/vnc/sshvnc.html then read the ssd man page paying close attention to the -L switch. If you have particular problems after this leg work, then ask again.
each end of the connection to make the remote VNC port accessible via a
port on the local gateway. However, their setup requires that the
remote machine have a routable IP address, doesn't it? Modifying the model on the page you sent me:
local machine (me) ----- gateway1
10.2.3.4/24 `ssh -g -L 5900:10.1.2.3:5900 gateway2`
runs vncviewer |
internet
|
gateway2 ----- remote machine
running sshd 10.1.2.3/24
running vnc server
on port 5900
Since the IP address I'm forwarding is non-routable, what happens? What happens to the source IP address, which is also non-routable and, to gateway2, non-local?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
