ER605 reports Local IP to DDNS instead of WAN IP
Hi,
I have 2 DDNS service providers configured and one of those is correctly sending the WAN IP (NO-IP) while the other one (DuckDNS) sends the Local IP.
I am pretty sure this has been working correctly until a few weeks ago before I replaced the ER605 V1 with the ER605 V2.
Could you please help with this?
Thank you
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thank you for your help.
I totally agree with your comments but I could not understand why it has been working before.
I have just realized that I re-inserted the Custom URL and accidentally introduced one new parameter ip=[IP].
This is not needed and it is why it was taking the wrong address.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @Clive_A ,
I attached the screenshots.
Note that the Public IP starts with 151.x.x.x in the router while I see the provider router IP in the services status (provider router --> ER605).
In any case NO-IP get the WAN IP while DuckDNS receives the router local IP.
This was working correctly before switching the ER605 from v1 to v2.
- Copy Link
- Report Inappropriate Content
Hi @Birillo
Thanks for posting in our business forum.
Birillo wrote
Hi @Clive_A ,
I attached the screenshots.
Note that the Public IP starts with 151.x.x.x in the router while I see the provider router IP in the services status (provider router --> ER605).
In any case NO-IP get the WAN IP while DuckDNS receives the router local IP.
This was working correctly before switching the ER605 from v1 to v2.
Because your WAN IP is not public. DDNS can report private IPs to the DDNS server.
Can you check your WAN interface IP address from the device info? Click it and on the popup page to your right.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
DuckDNS is updated via a URL and is passed the WAN IP address in the URL. As Clive says, the ER605 WAN has a private IP because its behind another NAT router.
I believe NO-IP uses the RFC 2136 compliant DDNS update method which sends a UDP update packet. This does not contain the actual IP, rather the update uses the source IP (from which the update is received) as the IP address to set the DDNS. Since this packet will be NAT'ed via your primary router, it will by implication always be sent from your true public IP
- Copy Link
- Report Inappropriate Content
Thank you for your help.
I totally agree with your comments but I could not understand why it has been working before.
I have just realized that I re-inserted the Custom URL and accidentally introduced one new parameter ip=[IP].
This is not needed and it is why it was taking the wrong address.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 797
Replies: 7
Voters 0
No one has voted for it yet.