#VNC VS SSH OVERHEAD INSTALL#
#VNC VS SSH OVERHEAD PASSWORD#
#VNC VS SSH OVERHEAD PC#
#VNC VS SSH OVERHEAD FREE#

Being in a DMZ forwards all incoming ports to the computer. Know that I had my son log into his router IP 192.168.1.1 and change to put his computer in the DMZ host Demilitarized zone with a check box under the security tab in his router software.

#VNC VS SSH OVERHEAD PC#

It will forward all this to my son's PC because of the DMZ Host setting. For Mint 8 Helena the VNC client is 'freds' is a valid username on my sons's PC '71.112.167.184' would be the external public IP address or hostname of my son's router's WAN/Internet port. Therefore: If I want to connect to my son's PC after the tunnel was established, all I need to do is to connect my VNC client to 'localhost:1', because that's where my son's desktop will now be waiting. My local TCP port 5901 will be forwarded to my son's internal IP address (ie 192.168.1.66), and there to TCP port 5900. I don't have a rule configured like that in my router). The router takes it and this to port 22 of my son's PC (This is generic. p 22: The TCP port I am connecting on my router. Here above is a non-secure simple starter command without the use of crypto 'blowfish' to get logged into a simple terminal window (CLI command line interface) on the remote machine.

#VNC VS SSH OVERHEAD PASSWORD#

there are some good tutorials on 'SSH tunneling', you can find them with Google.Ĭode: Select all ssh -2 -C -p 22 -L 5901:192.168.1.66:5900 password freds_password It will forward all this to my wife's PC because of the rule I setup. Therefore: If I want to connect to my wife's PC after the tunnel was established, all I need to do is to connect my VNC client to 'localhost:1', because that's where my wife's desktop will now be 'remotelogin' is a valid username on my wife's PC 'remotehost' would be the external IP address or hostname of my router's WAN/Internet port. My local TCP port 5901 will be forwarded to my wife's internal IP address, and there to TCP port 5900. The router takes it and then forwards this to port 22 of my wife's PC (I have a rule configured like that in my router). p 8888: The TCP port I am connecting on my router. With this parameter my office's firewall knows 'Oh yes, this is SSH v.2.

I need this or the firewall at my work place won't let me out. It's very fast (less overhead over slow connections) but still deemed secure. c blowfish-cbc: Selects the 'blowfish' crypto-algorithm. When I connect she gets a pop-up that informs her of my presence (this is standard). My wife's PC has 'vino' running all the time. I do it like this:Ĭode: Select all ssh -c blowfish-cbc -2 -C -p 8888 -L 5901:192.168.1.2:5900 when my wife needs my help I can type above sequence (or rather: I just click on the app launcher I created on my Linux desktop at work) and whooooosh, I am connected to her desktop at home and I see what she has on her screen, and I am thus able to help her. The problem with most xDSL and cable subscriptions is that the address changes in regular intervals, so unless there is a fixed IP address or a DNS hostname you can always use, there is no way of finding your grandma remotely.

#VNC VS SSH OVERHEAD FREE#

from free DNS providers such as 'dyns.cx' and many others). In order to be able to reach her from outside I'd also suggest either a fixed IP address or a 'dynamic DNS' address (e.g. The vino server will be listening on port 5900, and I will thus assume that your grandma's IP address on her LAN is '192.168.1.2' This would save you from having to mess too much with her config files. But the alternate port can usually be configured on the router you'd then just configure a 'port-forwarding' so that the non-standard port gets forwarded to her port 22. There are just too many script kiddies out there who keep hammering on port 22 when they find a machine with this port open. Also, I'd suggest not to use the default port of 22 for SSH, but something else. The biggest problem is to configure her LAN equipment (router?) properly so you can get through. With proper tunneling you can easily get through to her. that's a VNC server for her currently running X11 session. From here onwards it's very easy as SSH is able to tunnel anything else via its connection.

#VNC VS SSH OVERHEAD INSTALL#

BlahBlah_X wrote: How can I set this up? You should install openssh-server on her machine and make sure that SSH connections can get through.

Vnc vs ssh overhead