On 2018-03-21 16:20, Peter Suetterlin wrote:
Carlos E. R. wrote:
On 2018-03-21 14:36, Peter Suetterlin wrote:
Carlos E. R. wrote:
On 2018-03-21 13:36, Peter Suetterlin wrote:
I circumvent this issue by running tinc on my most-used machines, and use the (fixed) VPN IP to connect ;^>
But I use ssh in order to not use an VPN. I use poor man vpn services.
I use both. One reason is that using tinc I can easily connect to hosts behind masquerading routers, and I have quite some of those....
But then the remote machine has to initiate the connection. If not, it is the same problem with ssh, it has to traverse the NAT router
Yes, that's what tinc does. You need *one* machine with an 'open' IP address (i.e., with a dns entry, but that can be dynamical), machines connect to it and form a network. tinc is the broker that will determine how to actually connect to the other machine.
E.g., for my home tinc network 'pitnet' the open machine is standing in Stockholm. Part of the machines in that network are standing in the Canary Islands, in my second home. If two of those machines communicate via the tinc network the connection does *not* go via Stockholm, but takes the direct route.
It is *extremely* convenient. Have a look at it: http://www.tinc-vpn.org/
(disclaimer: The current maintainer is a good friend....)
I'll have a look. In my case, I only reach a single machine, the rest are powered off. Now that I think, there is another one, the TV set, but I can't install anything there. I think I use telnet with that one, I don't remember this instant. And that single machine is not directly accessible from Internet. I need to punch a hole in the router doing NAT, by redirecting a port. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))