DynDNS and CURL troubles

[shmuu]

Hi, after an update from 1.2.3 to 2.0, I am now having trouble with my DynDNS.  I have digged around a little bit in the logs and in the code, I have tried reconfiguring the settings, but nothing so far has helped.  This was working previously on 1.2.3.  Since the update, I have been trying to keep my system up-to-date with the latest build in hope that this problem may be resolved, but so far, I've had no luck.

I am posting below my system log (with the ip address masked).  I would really, really appreciate it if someone could please point me in the right direction.

Thanks and best regards,

=======START LOG========

Jan 10 11:55:58 php: /services_dyndns_edit.php: DynDns: Running updatedns()
Jan 10 11:55:58 php: /services_dyndns_edit.php: DynDns: updatedns() starting
Jan 10 11:55:59 php: /services_dyndns_edit.php: DynDns: _detectChange() starting.
Jan 10 11:55:59 php: /services_dyndns_edit.php: DynDns: _checkIP() starting.
Jan 10 11:55:59 php: /services_dyndns_edit.php: DynDns debug information: 70.26.xxx.xxx extracted from checkip.dyndns.org
Jan 10 11:55:59 php: /services_dyndns_edit.php: DynDns: Current WAN IP: 70.26.xxx.xxx
Jan 10 11:55:59 php: /services_dyndns_edit.php: DynDns: No Cached IP found.
Jan 10 11:55:59 php: /services_dyndns_edit.php: DynDns debug information: DynDns: cacheIP != wan_ip. Updating. Cached IP: 0.0.0.0 WAN IP: 70.26.xxx.xxx Inital update.
Jan 10 11:55:59 php: /services_dyndns_edit.php: DynDns: DynDns _update() starting.
Jan 10 11:55:59 php: /services_dyndns_edit.php: Curl error occurred: bind failed with errno 49: Can't assign requested address
Jan 10 11:55:59 php: /services_dyndns_edit.php: DynDns: DynDns _checkStatus() starting.
Jan 10 11:55:59 php: /services_dyndns_edit.php: DynDns: Current Service: easydns
Jan 10 11:55:59 php: /services_dyndns_edit.php: phpDynDNS: PAYLOAD:
Jan 10 11:55:59 php: /services_dyndns_edit.php: phpDynDNS: (Unknown Response)
Jan 10 11:56:00 check_reload_status: syncing firewall

[Perry]

Is the wan interface ip a public or a natted ip?

[shmuu]

It's natted.  Actually, to make things worse, I've gotten lazy in putting this system together.  Essentially what I've done is connect the WAN interface to the modem/wireless appliance from my ISP and obtain an IP address through DHCP.  This did work on 1.2.3.

Incidentally, I've reconfigured the system to have pfsense WAN as the public IP and that seems to have helped.

Thanks for your help.

Any reason that this was not worrking with nat?  As before- it worked without trouble under the previous version.

[Perry]

Any reason that this was not working with nat?  As before- it worked without trouble under the previous version.

I stumble upon it and wasn't sure how it worked before and added it as a side note to another bug report
http://redmine.pfsense.org/issues/show/249

[eri--]

Should be fixed in newer snaps.