My LAN router (ASUS 86U with Asus-Merlin) connects to the Internet via a cable modem that has been set to bridge mode by my cable provider.
When I poll my own WAN IP from my LAN, then use a machine on the WAN to connect back to my LAN, it works seamlessly: i get a 37.xx.xx.xx address to access the router config pages and all attached machines.
However, the WAN IP that my router displays on its network status page is different from my "real" WAN ip - it's a private ip @ 100.xx.xx.xx, and my router gives me a "double NAT" warning on the DDNS config page.
My impression was that Double NAT only happens when the cable modem is in router mode - which, in my case, it isn't. Can anybody explain where this private ip still comes from? And how can I make the router correctly configure DDNS with my "real" WAN ip?
When I poll my own WAN IP from my LAN, then use a machine on the WAN to connect back to my LAN, it works seamlessly: i get a 37.xx.xx.xx address to access the router config pages and all attached machines.
However, the WAN IP that my router displays on its network status page is different from my "real" WAN ip - it's a private ip @ 100.xx.xx.xx, and my router gives me a "double NAT" warning on the DDNS config page.
My impression was that Double NAT only happens when the cable modem is in router mode - which, in my case, it isn't. Can anybody explain where this private ip still comes from? And how can I make the router correctly configure DDNS with my "real" WAN ip?