pfSense

More info - tried adding DNSexit as an alternative provider and it doesn't work either (cached IP is 0.0.0.0 and 'save and force update' takes a long time before timing out as it does with no-ip).

Pertinent logs are:

Aug 24 16:22:25 php-fpm¹⁰¹⁴⁶: /services_dyndns.php: MONITOR: WAN_PPPOE is down, omitting from routing group WAN1First
Aug 24 16:22:25 php-fpm¹⁰¹⁴⁶: /services_dyndns.php: MONITOR: WAN_PPPOE is down, omitting from routing group WAN2First
Aug 24 16:22:25 php-fpm¹⁰¹⁴⁶: /services_dyndns.php: MONITOR: WAN_PPPOE is down, omitting from routing group WANBalanced
Aug 24 16:22:25 php-fpm¹⁰¹⁴⁶: /services_dyndns.php: MONITOR: WAN_PPPOE is down, omitting from routing group WAN1First
Aug 24 16:22:25 php-fpm¹⁰¹⁴⁶: /services_dyndns.php: MONITOR: WAN_PPPOE is down, omitting from routing group WAN2First
Aug 24 16:22:25 php-fpm¹⁰¹⁴⁶: /services_dyndns.php: MONITOR: WAN_PPPOE is down, omitting from routing group WANBalanced

...which led me to check the WAN connection. Here's where it gets strange - on the Status Dashboard, WAN has an IP address of 86.147.247.126 whereas in system->routing it's listed as having 172.16.12.35 - the dashboard address is the one in the right ballpark (the cached IP from before I upgraded to 2.2.4 was 86.147.125.146, and that's what i'd expect from a BT Infinity PPPoE connection) also the background colour to the description field in system-routing was grey for the WAN line, so I went in and disabled gateway monitoring on that line and the background went red (as i'd expect for a live connection) but the IP addresses didn't change either there or in the Status Dashboard, also the 'save and force update' didn't change it's failure state, so I went back in and re-edited to enable gateway monitoring, and the background is red still but no other change.

I think this points to Dynamic DNS failing as being a symptom of the WAN connection having some sort of abberation with respect to PPPoE IP versus some sort of observed IP on the 172.16 range?

OK, a further update...

Shortly after the last update, the whole pfsense instance crashed and couldn't be revived (couldn't get to the GUI, couldn't get any interface in the console to be 'up', and the config restore option flashed up a php error so fast it was barely readable). I've therefore just spent some time rebuilding from scratch a new instance (backups - who needs 'em!)

What i've found is:

- There is no specific problem with Dynamic DNS, it was a problem with my WAN connection that appeared to give routing problems over PPPoE which were only apparent when I rebooted, which may or may not have been coincidence with the 2.2.4 upgrade. Anyhow, setting DDNS with WAN2 (my alternate static BT Infinity PPPoE connection) on the rebuilt instance appears to work properly.
- There therefore may or may not be a problem with PPPoE negotiation and routing, as prior to the upgrade had both my WAN links working but post-upgrade WAN received a strange gateway IP and refused to route packets (it now appears).

Conclusion is that i'm now migrating all of my WAN services onto WAN2 and will spend the next few days working out whether it's an ISP issue with the modem etc on WAN or whether there is indeed an issue i'm chasing with pfSense. Hence after reading this you can probably close this bug unless you're suspicious of an issue with your PPPoE implementation.