2020-06-17, 14:42
That doesn't sound right - the NAS and router should have different local IP addresses, presuming they're actually distinct devices (ie the NAS isn't a drive hooked up to your router).
We're getting a bit off-topic again here, but let's put some basics down as background.
Firstly your home network (local area network, or LAN). It should be created by your router, and have internal IP addresses in a format like 192.168.0.x , where x is somewhere between 1-255 and is individual for each device on the network. They are most commonly 192.168.x.y (or occasionally 10.x.y.z) in format where x, y and z are all 1-255 in range (at least for IPv4 networks, we'll ignore IPv6 ones for now). Those addresses are assigned by the domain name server (DNS) on your network, which is normally a part of your router functionality.
The router will also act as a gateway between your local network and the wider internet (WAN), and it will have a second IP address that is provided to it via your ISP (your service provider).
Similarly the network at your cabin will have an equivalent set-up, and our aim is to securely link a device on the cabin network back to the home network via the VPN.
What the VPN does is to sit as a device in your home network, and it will create its own small (virtual private) network to which your cabin PC connects through the internet by use of the client app. That should have a different IP address range, commonly 10.9.0.x or something like that) to the home network range. The VPN server acts in more or less the same way as the router does on your home network, but in this case it links devices on the VPN network into the home network. Basically the client installed on the cabin PC will use the cabin's internet connection to "dial out" to the VPN server across the internet, and use its pre-shared credentials and passwords etc to set up a secure tunnel between the cabin PC and the VPN server, thus joining the cabin PC onto your home network.
So if you are on the cabin PC without the VPN being active and you do the IP check linked above, it should show the public IP address of the router at the cabin (or whatever is providing your internet access - in your test before the cellphone providing the hotspot is doing that role). But when you enable the VPN and if everything sets up correctly then as you're effectively now part of the home network, that visible IP address should change to the public IP address of your home router. If you're not sure what that is, you can normally get it from the web dashboard of the home router, or else just access the site I linked above from another PC or device that's connected to the home network.
Be careful not to mix up the public IP addresses of the router with the local ones on your home network.
Hope that's a little clearer for you anyway...
We're getting a bit off-topic again here, but let's put some basics down as background.
Firstly your home network (local area network, or LAN). It should be created by your router, and have internal IP addresses in a format like 192.168.0.x , where x is somewhere between 1-255 and is individual for each device on the network. They are most commonly 192.168.x.y (or occasionally 10.x.y.z) in format where x, y and z are all 1-255 in range (at least for IPv4 networks, we'll ignore IPv6 ones for now). Those addresses are assigned by the domain name server (DNS) on your network, which is normally a part of your router functionality.
The router will also act as a gateway between your local network and the wider internet (WAN), and it will have a second IP address that is provided to it via your ISP (your service provider).
Similarly the network at your cabin will have an equivalent set-up, and our aim is to securely link a device on the cabin network back to the home network via the VPN.
What the VPN does is to sit as a device in your home network, and it will create its own small (virtual private) network to which your cabin PC connects through the internet by use of the client app. That should have a different IP address range, commonly 10.9.0.x or something like that) to the home network range. The VPN server acts in more or less the same way as the router does on your home network, but in this case it links devices on the VPN network into the home network. Basically the client installed on the cabin PC will use the cabin's internet connection to "dial out" to the VPN server across the internet, and use its pre-shared credentials and passwords etc to set up a secure tunnel between the cabin PC and the VPN server, thus joining the cabin PC onto your home network.
So if you are on the cabin PC without the VPN being active and you do the IP check linked above, it should show the public IP address of the router at the cabin (or whatever is providing your internet access - in your test before the cellphone providing the hotspot is doing that role). But when you enable the VPN and if everything sets up correctly then as you're effectively now part of the home network, that visible IP address should change to the public IP address of your home router. If you're not sure what that is, you can normally get it from the web dashboard of the home router, or else just access the site I linked above from another PC or device that's connected to the home network.
Be careful not to mix up the public IP addresses of the router with the local ones on your home network.
Hope that's a little clearer for you anyway...
