since the GLDDNS isn’t capable of using the real IP address, it creates trouble when your device is behind another router. To get around this, I created glddns-behind-another-router.sh. Thanks to @SpitzAX3000 for the initial idea of updating the DDNS entry manually!
With this script can I create a network with a fixed IP to access my modem? without having that problem with the DDNS that keeps pulling the IP of this network that I created?
The following one-linear runs every 5 minutes to update your public IP WITHOUT installing any packages/scripts on the system and does NOT require enabling the GLDDNS service from the Web GUI at all!
It seems that it only works if you run the second command after the ip update, wireguard does not work, even though the real ip is correct in relation to ddns
I’m going to give up on having a specific network for my modem and keep glddns activated as it has never caused any problems except when the server is attacked.
By the way, you original question was only about GLDDNS pulling the wrong public up when GL device is connected to upstream router! So all what admon and I have provided was to help you to automate things.
Even if you are right, you are not completely right
My script utilizes sudo -g nonevpn which will force all traffic through WAN instead of VPN. I guess that’s what @japa182 is talking about.
What difference does it make ?! You’re sending a single http packet to bind an IP. Whether you send it through a tunnel or not, once it reaches the server with the valid parameters, you get an ok.
exactly, I use ddns to link my real IP to use my wireguard server on the mt6000, so I can access my router from other devices such as cell phones and notebooks and also use my mt3000 as a wireguard client on the wireguard server made on the mt6000