DynDNS claims cannot determine WAN IP when WAN is RFC1918

mfld

Edit:

Seeing same thing on a whitebox I just upgraded. NOT limited to SG-1100. Filed in redmine.

Current Base System
23.01.b.20230106.0600
Latest Base System
23.01.b.20230106.0600

WAN IPv4 is RFC1918 (in a hotel)

DynDNS not updating anymore. DNS lookups work. CheckIP service is resolvable, reachable and works:

curl -s http://checkip.dyndns.com
<html><head><title>Current IP Check</title></head><body>Current IP Address: 209.3.185.234</body></html>

Log claims it cannot figure the IPv4 address via the checkip service:

Jan 12 05:13:23 	php-fpm 	381 	/services_dyndns_edit.php: Dynamic DNS (demobox.mfld-pub.net) There was an error trying to determine the public IP for interface - wan (mvneta0.4090 ).
Jan 12 05:13:23 	php-fpm 	381 	/services_dyndns_edit.php: Dynamic DNS (demobox.mfld-pub.net): running get_failover_interface for wan. found mvneta0.4090
Jan 12 05:13:23 	php-fpm 	381 	/services_dyndns_edit.php: Dynamic DNS cloudflare (demobox.mfld-pub.net): Public IP address could not be extracted from Check IP Service
Jan 12 05:13:22 	php-fpm 	381 	/services_dyndns_edit.php: Dynamic DNS cloudflare (demobox.mfld-pub.net): _checkIP() starting.
Jan 12 05:13:22 	php-fpm 	381 	/services_dyndns_edit.php: Dynamic DNS: updatedns() starting
Jan 12 05:13:22 	php-fpm 	381 	/services_dyndns_edit.php: Configuration Change: admin@172.16.110.101 (Local Database): Dynamic DNS client configured.
Jan 12 05:13:00 	php-fpm 	4335 	/services_dyndns.php: Dynamic DNS (demobox.mfld-pub.net) There was an error trying to determine the public IP for interface - wan (mvneta0.4090 ).
Jan 12 05:13:00 	php-fpm 	4335 	/services_dyndns.php: Dynamic DNS (demobox.mfld-pub.net): running get_failover_interface for wan. found mvneta0.4090
Jan 12 05:13:00 	php-fpm 	4335 	/services_dyndns.php: Dynamic DNS cloudflare (demobox.mfld-pub.net): Public IP address could not be extracted from Check IP Service

jimp

Curious. It works for me with a custom service (https://checkip.amazonaws.com) but not the default one.

I think I see why, though. Looks like a simple fix.

jimp

Fix is in:

https://github.com/pfsense/pfsense/commit/1e7eb5d1186dbc4c31f49af5e3ce72d9797b48ba

You can install the System Patches package and then create an entry for 1e7eb5d1186dbc4c31f49af5e3ce72d9797b48ba to apply the fix or wait for the next snapshot.

mfld

@jimp said in DynDNS claims cannot determine WAN IP when WAN is RFC1918:

1e7eb5d1186dbc4c31f49af5e3ce72d9797b48ba

1e7eb5d1186dbc4c31f49af5e3ce72d9797b48ba

Indeed resolves it!

Thanks