ddns is not getting new external cgnat wan ip

[lgkahn]

it was working previously but even manually running the script the ddns is not sensing an ip change and when i run it still is pulling in the old external ip..

only method to have it correctly get the changed external ip is to reboot the router..

any ideas.. my qnap nas on the same network is sensing the ip change so i know it is possible..


(it is getting an external wan ip not internal but not the current one unless i reboot)

 

[lgkahn]

internal wan ip is 100.64.0.1
extern is 129.222.44.119

router is showing incorrect one of 129.222.44.167 (the last one)

 

[lgkahn]

its a gt-ax11000 pro running 3004.388.7_0_rog

tried newer388.8 beta 1 ... same issue.

 

[lgkahn]

as someone else posted in another thread if i goto the web interface and hit apply on the wan page it brings wan down and comes back up with correct external wan ip..

so how can i programatically schedule a call say every 3 hours via chron to force it to bring down and back up the wan interface and then manually call the ddns script (as a workaround) unless this can be fixed the correct way..'

ie

 

[Tech9]

How is this DDNS working behind CGNAT?

 

[lgkahn]

Why their is no reason it can't work . Outgoing connections are allowed and I need the DNS to work so I can allow connections.from the correct IP.

 

[Tech9]

It needs public WAN IP. Your WAN IP is private, assigned by another router upstream.

 

[lgkahn]

No.it.doesn't. Read the docs the are settings at for external vs.internal wan.IP in.the.ddns docs.specificially for this issue.and my.other routers and other devices get.the.actual IP.fine. in addition if you read.my post it IS getting an external wan.ip. The internal.is.totally.different. you are.barking up the wrong tree. That Is not.my.issue. it.is just not.updating when.it changes.without a wan up/down event or reboot.

 

[Tech9]

DDNS won't work behind CGNAT. The public IP you see is shared between many subscribers. The subscribers are assigned private IP addresses by the ISP DHCP. You can't use this shared public IP for any personal purposes unless the ISP has special port forwarding service. The ISP runs a firewall and by default it will refuse unsolicited inbound connections. If your thread title is correct - what you are trying to do is useless. The firmware settings for external IP detection are used when your main router is behind ISP provided modem/router and you have no bridge option.