So any open source solution is going to come with some server SW and expect you to figure out where to run that server SW. That bit is the big reason you don't see something like teamviewer in the open source world, to get it to work that smoothly you MUST have a server that everyone connects to, and someone needs to pay for that. That is how teamviewer does it (though with their own protocol, not ssh, and a little logic on the server side to find and control who can access what tunnel). When doing it this way you just connect to the server (ssh in), and you can forward the port back from the server to your computer, for both ssh and/or VNC. This is basically how teamviewer makes it work. The simple way to do this in Linux is just ssh on boot with a remote tunnel to some third party server and just it sit with that connection open all the time.
If you want it to work without port forwards of any kind, then you need an outbound request to a server somewhere. It probably won't work if you're trying to support someone who is at starbucks or something. This is hit or miss, but for most home networks it will work. Like I said, you can use a upnp client to request that your router opens the port (most home router default settings allow anyone to request port forwards), this can be run just prior to booting or whatever to request that the ports are opened. But someone might link a package of scripts that does what I said above. And I think you don't see an integrated solution because there isn't much of a need, ssh just works so well. If this is an enterprise situation, you should just configure the system to do it in a smooth way, but like I said, usually ssh is plenty.Īnd finally, there is always teamviewer for Linux, you pay you get your third party server to help. In practice though you still need to get the user to tell you to tell you their IP, and I find it's just way easier to do the upnp to do the port forwards (I believe there are some GUI clients out there as well), and ssh into it, you can generally do anything (including VNC setup if it's required) over ssh. A VNC server is similarly easy to start on boot as well (but a moderate amount of setup) Sounds like this is to help family or something? A UPNP client can usually do the port forwards for you, and it can be wrapped in a script to do it on boot. What is the end goal here? Installing anything (even teamviewer) is going to require setup, and yes, you can meet all your requirements with VNC. But it's doable, is that really what you want that? With a GUI? VNC works fine, but using a desktop GUI for a system clunky from a phone. Can control Desktop from a Mobile Phone/Tablet.Same with the IP, discovering the IP requires a third party server, there are lots of ways of doing that, easiest is setting up DDNS. This is difficult, mostly because unless you can guarantee that UPnP works, this requires a third party server to act as the go between, and someone has to pay for that.
BEST TEAMVIEWER ALTERNATIVE 2019 INSTALL
0 kommentar(er)
