Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare

[power_matz]

@stephenw10 I have the same issue here

[fireodo]

@power_matz said in Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare:

I have the same issue here

Hello,

can you try to add as check service: http://checkip.dns.he.net ? or: https://checkip.amazonaws.com/ ?

[stephenw10]

Try running in Diag > Command Prompt:

It should return the correct public IP as a string.

Is everyone hitting this using pppoe by chance?

[power_matz]

@fireodo I added both services. Without any success

[power_matz]

@stephenw10 Here is my output

[fireodo]

@power_matz said in Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare:

I added both services. Without any success

OHhh - so there must be, in your case, a other cause for not getting the pppoe0 adress ...
I have here also dyndns with pppoe but not with cloudflare as provider ...

[fireodo]

@stephenw10 said in Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare:

Is everyone hitting this using pppoe by chance?

I have pppoe here too but not cloudflare dyndns - i guess its something specific to cloudflare ...

[nation]

@stephenw10 same output here. it show my correct ip
i've tried the webpage also return the correct ip

@fireodo i've added both of sites, same result

[stephenw10]

Hmm, the error it's showing should be independent of the service in use. It tries to read the IP, checks its a valid IP address and fails that check.

I'm wondering if it's passing the wrong interface type after the pppoe changes hence asking if anyone is hitting it on a non-pppoe wan?

Also is anyone using using not the actual 'wan'? Like opt1, opt2 etc?

[power_matz]

@stephenw10 Just to clarify: I am still using the old module, not the new if_pppoe kernel module for PPPoE client

[stephenw10]

Ok. It may still be the issue though as the pppoe code was changed to allow both connection types.

[power_matz]

@stephenw10 Just configured another DynDNS Service and switched to the new if_pppoe kernel module. The problem is still there

[stephenw10]

Only after switching to if_pppoe?

Which interface are you using pppoe on? The actual 'wan' interface?

[power_matz]

@stephenw10 before and after switching. Just wanted to confirm that the new if_pppoe module is not the culprit.
I am using the 'wan' interface

[djstone]

Hello.
I am experiencing the same faulty behavior.
When debugging the PHP-Command in pfSense, it returns an IPv6 in my case.

[stephenw10]

When querying pppoe0?

[djstone]

@stephenw10
Yes.
Still quite common in Germany. (V)DSL so it's based on pppoe.

Dynamic DNS updates stopped working just as 2.8.0 was installed. Quite a bummer for me because I am heavily depended on that function.
I also tested it with the old pppoe driver and the new one - same behavior, despite I am not using cloudflare.

[stephenw10]

Do you only have an IPv6 address there?

I'm using PPPoE over VDSL here and it work fine. There must be something else in play.

[stephenw10]

Is your upstream gateway shown as online?

In 2.8.0 (and 25.03) dyndns update will fail if the gateway is offline.

[djstone]

@stephenw10
Nope, it's dual stack (IPv4 and IPv6)