I believe that picture is correct. There’s an assumption about the ISP router part. I have no actual details on that, but I assume it must be something like that - I’m on BT fibre if that helps.
So the WAN IP address listed on my router dashboard is the same as listed in myip.com.
myip.com lists a host which is a different IP range
there is a gateway shown in the details of the router dashboard for the wan connection which is also a different IP range.
So I think the host is maybe the WAN side of the ISP router and the gateway is the LAN side of the ISP router
I used the router tools traceroute, connection - WAN and destination - my new domain.
The result was 30 hops and it displayed the WAN IP address of my router so I think the I have a way from the internet to my router now and I just have to setup the port forwarding - which is currently not successful oooooph!
I type my domain into the address bar of a browser and I get “the site can’t be reached page”
So not sure at the mo where it’s not working.
I tried the quick and dirty upnp router setup through the synology nas just to get some temporary mappings/rules created in the router that should have commonly used ports for the nas, but no joy.
Writing the reply as I try things. Disabled all the upnp & nat-pmp settings and manually created rules using the ports listed from the upnp and hey presto! it’s working w00t!
Disabled it now and need to make sure all my security settings are good in the NAS. Having ports open direct to the nas i guess means it could be targetted fairly soon and often by bots or whatever else is out there.
Maybe I can schedule the activation of the port mappings so they are only active when I need them or turn them off/on though an app on a phone.
It’s fun when it all starts to work
Thanks for your help