Dynamic DNS (ZoneEdit) and multi WAN



  • Hi,
    I have some problem to get pfSense to update the IP for my second WAN on the ZoneEdit-service.

    The first WAN setup works great, but when adding a new configuration for my second WAN it's not able to update the IP.

    Here is what the syslog says.
    First it checks and updates the first WAN IP and after that it fails to update the second WAN IP.

    Jul 18 23:20:04 	php: /services_dyndns_edit.php: DynDns: DynDns _checkStatus() starting.
    Jul 18 23:20:04 	php: /services_dyndns_edit.php: DynDns: Current Service: zoneedit
    Jul 18 23:20:04 	php: /services_dyndns_edit.php: DynDns: _checkIP() starting.
    Jul 18 23:20:04 	php: /services_dyndns_edit.php: DynDns debug information: 10.0.0.1 extracted from local system.
    Jul 18 23:20:04 	php: /services_dyndns_edit.php: phpDynDNS: updating cache file /conf/dyndns_wanzoneedit.cache: 10.0.0.1
    Jul 18 23:20:04 	php: /services_dyndns_edit.php: phpDynDNS: (Success) IP Address Updated Successfully!
    Jul 18 23:20:29 	php: /services_dyndns_edit.php: DynDns: Running updatedns()
    Jul 18 23:20:29 	php: /services_dyndns_edit.php: DynDns: updatedns() starting
    Jul 18 23:20:29 	php: /services_dyndns_edit.php: DynDns: _detectChange() starting.
    Jul 18 23:20:29 	php: /services_dyndns_edit.php: DynDns: _checkIP() starting.
    Jul 18 23:20:29 	php: /services_dyndns_edit.php: DynDns debug information: 10.0.0.2 extracted from local system.
    Jul 18 23:20:29 	php: /services_dyndns_edit.php: DynDns: Current WAN IP: 10.0.0.2
    Jul 18 23:20:29 	php: /services_dyndns_edit.php: DynDns: No Cached IP found.
    Jul 18 23:20:29 	php: /services_dyndns_edit.php: DynDns debug information: DynDns: cacheIP != wan_ip. Updating. Cached IP: 0.0.0.0 WAN IP: 10.0.0.2 Inital update.
    Jul 18 23:20:29 	php: /services_dyndns_edit.php: DynDns: DynDns _update() starting.
    

    Is it possible I've found a bug, or maybe just misconfiguration by me? :)

    Edit:
    Current version: 2.0-BETA3
          Built On: Sun Jul 18 02:17:40 EDT 2010



  • Is it really 10.0.0.1 on one WAN and 10.0.0.2 on the other? The main difference between how the two WANs should work is when the second is updated its update goes out the WAN it's associated with. I've tested a lot of scenarios with several of the providers we support on a box with 3 WANs and about a dozen dynamic DNS hostnames across a handful of providers. All of those work fine now. I don't have a ZoneEdit account though, I signed up for one a few hours ago but it hasn't been confirmed. Whenever it is, I'll try it. I suspect there's something wrong there with ZoneEdit.



  • Hi,
    Thank you for your reply!
    No, 10.0.0.1|2 is not the actually IP's.
    Worth noticing tough is that all my WAN IP's is on the same subnet and uses the same gateway from my ISP.

    I haven't done any configurations to the firewall rules at all. Only thing I have changed is adding all the WAN's in to one group (in the Routing -> Groups menu section).



  • @twan:

    Worth noticing tough is that all my WAN IP's is on the same subnet and uses the same gateway from my ISP.

    That won't work correctly, each must have a unique gateway.

    Not sure if ZoneEdit works in general with multi-WAN or not, my account still hasn't been approved.



  • @cmb:

    That won't work correctly, each must have a unique gateway.

    Well, multi-wan worked great on 1.2.3 with the same gateway on all interfaces. Will this not work any more? Or what do i need to do to make that work?



  • @twan:

    Well, multi-wan worked great on 1.2.3 with the same gateway on all interfaces. Will this not work any more? Or what do i need to do to make that work?

    No it didn't, that has never been a supported configuration. pf's route-to must send traffic to a unique gateway IP for each WAN. It won't work correctly any other way. If you have multiple WANs with the same gateway only one will get used at a time, though which one can vary.


Log in to reply