Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    39 Posts 7 Posters 4.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by stephenw10

      Are you using the new if_pppoe module?

      If you enable verbose logging on the dyndns client do you see more?

      1 Reply Last reply Reply Quote 0
      • T
        TheBigS
        last edited by

        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.

        30b36656-4eab-4c68-9e95-c2dd9ff29cfb-grafik.png

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

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Also with Cloudflare?

          1 Reply Last reply Reply Quote 0
          • N
            nation
            last edited by

            I have enabled new if_ppoe module and verbose logging. The result is the same.b14eeee7-d0b2-409b-8a65-54d4c29dcbc4-image.png

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              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.

              T 1 Reply Last reply Reply Quote 0
              • T
                TheBigS @stephenw10
                last edited by

                @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.

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  How do you have it configured?

                  P 1 Reply Last reply Reply Quote 0
                  • P
                    power_matz @stephenw10
                    last edited by

                    @stephenw10 I have the same issue here

                    fireodoF 1 Reply Last reply Reply Quote 0
                    • fireodoF
                      fireodo @power_matz
                      last edited by 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/ ?

                      Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
                      SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
                      pfsense 2.8.0 CE
                      Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

                      P 1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        Try running in Diag > Command Prompt:

                        Screenshot from 2025-06-03 13-05-23.png

                        It should return the correct public IP as a string.

                        Is everyone hitting this using pppoe by chance?

                        P fireodoF 2 Replies Last reply Reply Quote 0
                        • P
                          power_matz @fireodo
                          last edited by

                          @fireodo I added both services. Without any success

                          fireodoF 1 Reply Last reply Reply Quote 0
                          • P
                            power_matz @stephenw10
                            last edited by

                            @stephenw10 Here is my output Bildschirmfoto 2025-06-03 um 14.29.52.jpg

                            1 Reply Last reply Reply Quote 0
                            • fireodoF
                              fireodo @power_matz
                              last edited by

                              @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 ...🤔

                              Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
                              SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
                              pfsense 2.8.0 CE
                              Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

                              1 Reply Last reply Reply Quote 0
                              • fireodoF
                                fireodo @stephenw10
                                last edited by

                                @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 ... 🤔

                                Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
                                SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
                                pfsense 2.8.0 CE
                                Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

                                1 Reply Last reply Reply Quote 0
                                • N
                                  nation
                                  last edited by

                                  @stephenw10 same output here. it show my correct ip8303b1e7-bae0-4d44-a1e4-715311b3f78a-image.png
                                  i've tried the webpage also return the correct ip
                                  43cd85b9-6cf4-4e73-9def-531038010f4b-image.png
                                  @fireodo i've added both of sites, same result
                                  b8262768-6ba7-4612-8138-af1738c7c214-image.png

                                  1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    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?

                                    P 1 Reply Last reply Reply Quote 0
                                    • P
                                      power_matz @stephenw10
                                      last edited by

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

                                      1 Reply Last reply Reply Quote 0
                                      • stephenw10S
                                        stephenw10 Netgate Administrator
                                        last edited by

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

                                        P 1 Reply Last reply Reply Quote 0
                                        • P
                                          power_matz @stephenw10
                                          last edited by

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

                                          1 Reply Last reply Reply Quote 0
                                          • stephenw10S
                                            stephenw10 Netgate Administrator
                                            last edited by

                                            Only after switching to if_pppoe?

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

                                            P 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.