1 |
> >>Why do though all the hassle of setting up a VPN when you can use SSH to |
2 |
> >>provide a secure tunnel into the network and use that instead? Works |
3 |
> >>fine for me. |
4 |
> >> |
5 |
> >># ssh -L5900:hostname:5900 username@××××××××.tld |
6 |
> >># vncviewer localhost:0 |
7 |
> > |
8 |
> > Okay, now show me the instance where you want box->internet->box->vnc server. |
9 |
> |
10 |
> That does provide a tunnel between two boxes. It's quick and simple to |
11 |
> setup and can be used by any ssh client, regardless of the system. |
12 |
> Whether you're on Unix or Linux. You can even do it using Windows using |
13 |
> PuTTY. |
14 |
> |
15 |
> It's good to know in case if you need access but don't have a box that |
16 |
> can't do VPN, or there's a problem with the VPN. |
17 |
> |
18 |
> If you want to open it up for some reason to another box, you can use |
19 |
> the gateway switch (-g) and SSH will listed to all incoming connections |
20 |
> on that port on the remote computer. |
21 |
> |
22 |
> # ssh -g -L5900:remote:5900 username@server:port |
23 |
> |
24 |
> > If you set up openvpn on your ssh server, you easily can tunnel across it. |
25 |
> > Doing that with ssh would add another tunnel. Takes 5 minutes to set up. |
26 |
> |
27 |
> I'm not disagreeing with you, but a VPN can add a whole level of |
28 |
> complexity and setup, whereas if you just want to remotely access a VNC |
29 |
> server across the Internet, SSH works great and has added security built in. |
30 |
> |
31 |
> If you want to access more than VPN, i.e. SMB, or need the remote |
32 |
> computer to 'appear' on the local network for some reason, VPN is fine - |
33 |
> go ahead and use it. |
34 |
> |
35 |
> KISS - keep it short and simple. |
36 |
> |
37 |
> -- |
38 |
> Jonathan Wright ~ mail at djnauk.co.uk |
39 |
|
40 |
Ok, thanks for the help everyone! |
41 |
|
42 |
- Grant |
43 |
|
44 |
-- |
45 |
gentoo-user@g.o mailing list |