Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare

[TheBigS]

I have the same issue. I tried it with the new if_pppoe module and with the old. Both are not working. I got this message.

For me it looks like, pfSense is not able to resolve the WAN IP address.

[stephenw10]

Also with Cloudflare?

[nation]

I have enabled new if_ppoe module and verbose logging. The result is the same.

[stephenw10]

You are using the default http://checkip.dyndns.org in check IP services?

If you just visit http://checkip.dyndns.org does it show you the correct IP?

That is working fine for me in 2.8 using pppoe. I'm not using Cloudflare but it seems to be failing before it ever gets to trying to update that.

[TheBigS]

@stephenw10 I tried the default and set up my own check service, and of course both are reporting the correct IP address. I am using a custom DDNS service (ipv64.net). I had no problems with it with 2.7.x. So that's why I think it's a problem with the 2.8 release.

[stephenw10]

How do you have it configured?

[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