Access to the grid behind a "gray" IP?

Question

Computer networks

The situation is as follows - there is some provider that issues only "gray" addresses. The client has its own grid, in which the NAS, several computers, tablets, etc. work.

It is required occasionally to somehow connect to this grid for administration.

It is clear that if there was a “white” address, it would be possible to forward the necessary ports, raise the VPN server to storage, etc., but what about the “gray” address?

The client is frankly poorly versed in IT, but is far away (i.e. the “drive up” option is associated with air travel).

Tell me how you can administer such an "inaccessible" grid?

Answer 1

Take a VPS, make a permanent VPN from the client to this VPS, make routes to its network.
further, most connect via VPN and see its network.
To set up all this, initially use the teamviewer.
Any VPN - openvpn, pptp, l2tp+ipsec

Answer 2

www.teamviewer.com/en/index.aspx

Answer 3

yuzat ipv6 through tunnel brokers.

Answer 4

To clarify everything (correct me if I'm wrong about something).
There are two concepts:
Further. There may be different combinations of these two properties. The most important thing is that, in general, a direct connection via a Gray IP from the Internet will not work (without using an auxiliary server with a White IP). At the same time, a direct connection to the Dynamic White IP is quite possible using DynoDNS.
The best (but not the easiest) solution to the Gray IP problem is to set up a VPN server on your VDS, which has a White IP. Also, you can use various paid and possibly free services like TeamViewer, Splashtop, LogMeIn-Hamachi, NetRouter, .... (depending on your needs)

Answer 5

I was also looking for solutions on this topic. Gray IP like a splinter in one place. LiderMaximum - you are a talker!
My case: there is an apartment with a white dynamic ip and a plot with a gray one. NAS, asterisk, video surveillance and openHab in both locations. It was necessary to connect all this for synchronization and monitoring. After digging around on the net and reading what smart uncles and aunts write, I decided in favor of a site-to-site VPN. Installed the pfsense distribution as a two-way router and set up an ipsec vpn tunnel. In an apartment where there is a white IP, pfsense listens to a knock on the tunnel from the other end, and as soon as it hears, everything connects and everything is fine. On the other end, pfsense, as the initiator of the tunnel connection. On the contrary, it does not work, because he sits behind a gray IP and cannot be reached from outside. But in all this blunder there is a jamb. If pfsense suddenly went out and rebooted behind a gray IP, then you have to go to the place and press the tunnel connection button in the ipsec settings.

Answer 6

www.ammyy.com/ru/
and so - all options are connected with a piece of iron.

Answer 7

DDNS and port forwarding on the router. At the same time, Synology NAS is supported out of the box.

Answer 8

How did you solve the problem?
Exactly the same task, though there is access to iron.

Answer 9

LiderMaximum "there are at least 3 solutions"
To the studio, please!

Answer 10

Forward ports in the same way as for white IP. Plus some DynDNS (the same no-ip), and go by domain name.

Answer 11

forward ports, well, put “snitch / whose” in the client grid (A program that periodically connects to a known accessible node, thereby giving out its location on the network. (Naturally you control the node)
As a snitch, you can use the old-school iperf in client mode, and start its script (at least on each client computer, and if it has Windows 7 or a UNIX-way operating system, then the script can be directly hung up on network connection / disconnection events without any problems, this is just the moment when the address change can occur)
. server you will always know the current IP, go as much as you
like.VPN is also a good idea, it all depends on how tightly you outsource.If you go to cars via RDP / VNC, then it's not worth it,
if you need to test the network, internal services, etc. then, only VPN.
PS: The bastard provider may also have a backbone NAT (although this is already history, but in some cities and towns I still meet local locales that look outside through the provider's direct NAT, being there inside - quite separate, but this is Hell and sadomia and not being discussed)

Answer 12

How are you going to connect - VNC, RDP, SSH?

Answer 13

I have such a problem with gray ip. The provider wrote: "Now a white IP is not issued to a "regular" subscriber! It IS NOW. But a static IP is issued. In the tunnel. Always the same. Static is issued by the ppp server when the connection is raised, or gray (172. NATS), or white, which is simply routed to the Internet. That is, if you need GUARANTEED access from the Internet, then only a static IP."

Answer 14

I use pointgsm.ru, make a white static ip address, register it for individuals

Answer 15

Use DDNS for remote access. You do not need to buy a static external IP, gray IPs issued by the provider are not at all an obstacle to organizing remote access.
Contrary to the generally accepted opinion and criticism of illiterate "wise men", there are at least 3 solutions that allow you to use DDNS in cases where gray IPs are issued by the provider.