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

    Upgrade to 22.05 has killed my pppoe WAN

    Scheduled Pinned Locked Moved General pfSense Questions
    36 Posts 4 Posters 5.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 seeing errors in the logs when you try to connect?

      Like this perhaps in the ppp log:

      Cannot attach to ng_ether message: Invalid argument.

      It looks likely that the upgrade didn't complete as expected given the logs.
      Check the output of pkg info -x pfSense. Are there any packages still showing 22.01?

      Steve

      O 1 Reply Last reply Reply Quote 0
      • O
        orangehand @stephenw10
        last edited by orangehand

        @stephenw10
        From ppp log:
        Jun 29 16:33:01 ppp 79227 [igb0] Cannot attach to ng_ether message: Invalid argument.
        Jun 29 16:33:01 ppp 79227 [wan_link0] PPPoE: Error creating ng_pppoe node on igb0:
        Jun 29 16:33:01 ppp 79227 [wan_link0] PPPoE node for link is not initialized
        Jun 29 16:33:01 ppp 79227 [wan_link0] Link: DOWN event
        Jun 29 16:33:01 ppp 79227 [wan_link0] LCP: Down event
        Jun 29 16:33:01 ppp 79227 [wan_link0] Link: reconnection attempt 5 in 2 seconds

        From pkg info:
        pfSense-22.01
        pfSense-Status_Monitoring-1.7.11_4
        pfSense-base-22.05
        pfSense-default-config-serial-22.05
        pfSense-kernel-pfSense-22.05
        pfSense-pkg-Status_Traffic_Totals-2.3.2_2
        pfSense-pkg-acme-0.7.1_1
        pfSense-pkg-bandwidthd-0.7.4_5
        pfSense-pkg-freeradius3-0.15.7_33
        pfSense-pkg-iperf-3.0.2_5
        pfSense-pkg-ntopng-0.8.13_10
        pfSense-pkg-openvpn-client-export-1.6_4
        pfSense-pkg-squid-0.4.45_8
        pfSense-pkg-squidGuard-1.16.18_20
        pfSense-pkg-sudo-0.3_6
        pfSense-pkg-suricata-6.0.4_1
        pfSense-rc-22.05
        pfSense-repo-22.05_2
        pfSense-upgrade-1.0_26
        php74-pfSense-module-0.76

        How do I fix this please Steve?

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

          Right so it's still running the 22.01 meta package for some reason.

          I assume it's not offering you an update in the gui?

          If you run pfSense-upgrade -d at the command line does it offer anything?

          Otherwise you can try running pkg-static upgrade and it should then see the updated meta package.

          Steve

          O 1 Reply Last reply Reply Quote 0
          • O
            orangehand @stephenw10
            last edited by

            @stephenw10
            so pfSense -upgrade -d from the gui cmd gives:

            Updating repositories metadata...
            Updating pfSense-core repository catalogue...
            Fetching meta.conf: . done
            Fetching packagesite.pkg: . done
            Processing entries: .. done
            pfSense-core repository update completed. 14 packages processed.
            Updating pfSense repository catalogue...
            Fetching meta.conf: . done
            Fetching packagesite.pkg: .......... done
            Processing entries: .......... done
            pfSense repository update completed. 540 packages processed.
            All repositories are up to date.

            The following 61 package(s) will be affected (of 0 checked):

            New packages to be INSTALLED:
            graphite2: 1.3.14 [pfSense]
            harfbuzz: 4.1.0 [pfSense]
            lua54: 5.4.2 [pfSense]
            php74-libbe: 0.1.4 [pfSense]

            Installed packages to be UPGRADED:
            bash: 5.1.12 -> 5.1.16 [pfSense]
            bind-tools: 9.16.23 -> 9.16.26 [pfSense]
            clamav: 0.104.1,1 -> 0.104.2,1 [pfSense]
            db5: 5.3.28_7 -> 5.3.28_8 [pfSense]
            devcpu-data: 20211109 -> 20220221 [pfSense]
            dnsmasq: 2.86,1 -> 2.86_3,1 [pfSense]
            dpinger: 3.0 -> 3.2 [pfSense]
            filterdns: 2.0_5 -> 2.0_6 [pfSense]
            fontconfig: 2.13.94_1,1 -> 2.13.94_2,1 [pfSense]
            gdbm: 1.22 -> 1.23 [pfSense]
            graphviz: 2.44.1_17 -> 2.50.0 [pfSense]
            hostapd: 2.9_4 -> 2.10 [pfSense]
            iperf3: 3.10.1_1 -> 3.11 [pfSense]
            libgd: 2.3.1,1 -> 2.3.3,1 [pfSense]
            links: 2.20.2_1,1 -> 2.25,1 [pfSense]
            mpd5: 5.9_6 -> 5.9_7 [pfSense]
            mysql57-client: 5.7.36 -> 5.7.37_1 [pfSense]
            ndpi: 4.0.d20210818,1 -> 4.2.d20220210,1 [pfSense]
            nginx: 1.20.2_1,2 -> 1.20.2_9,2 [pfSense]
            nss: 3.73 -> 3.76 [pfSense]
            ntopng: 5.0.d20210923,1 -> 5.2.d20220314,1 [pfSense]
            ntp: 4.2.8p15_3 -> 4.2.8p15_5 [pfSense]
            openvpn: 2.5.4_1 -> 2.6.0_8 [pfSense]
            pfSense: 22.01 -> 22.05 [pfSense]
            pfSense-pkg-sudo: 0.3_6 -> 0.3_7 [pfSense]
            php74-bz2: 7.4.26 -> 7.4.28 [pfSense]
            php74-ctype: 7.4.26 -> 7.4.28 [pfSense]
            php74-filter: 7.4.26 -> 7.4.28 [pfSense]
            php74-ftp: 7.4.26 -> 7.4.28 [pfSense]
            php74-gettext: 7.4.26 -> 7.4.28 [pfSense]
            php74-intl: 7.4.26 -> 7.4.28 [pfSense]
            php74-json: 7.4.26 -> 7.4.28 [pfSense]
            php74-ldap: 7.4.26 -> 7.4.28 [pfSense]
            php74-opcache: 7.4.26 -> 7.4.28 [pfSense]
            php74-pcntl: 7.4.26 -> 7.4.28 [pfSense]
            php74-pdo_sqlite: 7.4.26 -> 7.4.28 [pfSense]
            php74-pfSense-module: 0.76 -> 0.81 [pfSense]
            php74-posix: 7.4.26 -> 7.4.28 [pfSense]
            php74-readline: 7.4.26 -> 7.4.28 [pfSense]
            php74-session: 7.4.26 -> 7.4.28 [pfSense]
            php74-shmop: 7.4.26 -> 7.4.28 [pfSense]
            php74-simplexml: 7.4.26 -> 7.4.28 [pfSense]
            php74-sockets: 7.4.26 -> 7.4.28 [pfSense]
            php74-sqlite3: 7.4.26 -> 7.4.28 [pfSense]
            php74-sysvmsg: 7.4.26 -> 7.4.28 [pfSense]
            php74-sysvsem: 7.4.26 -> 7.4.28 [pfSense]
            php74-sysvshm: 7.4.26 -> 7.4.28 [pfSense]
            php74-xmlreader: 7.4.26 -> 7.4.28 [pfSense]
            php74-xmlwriter: 7.4.26 -> 7.4.28 [pfSense]
            postgresql13-client: 13.5 -> 13.6 [pfSense]
            py38-libzfs: 1.1.2021100100 -> 1.1.2022021400 [pfSense]
            smartmontools: 7.2_3 -> 7.3 [pfSense]
            socat: 1.7.4.2 -> 1.7.4.3 [pfSense]
            squid: 4.15 -> 5.4.1 [pfSense]
            sudo: 1.9.8p2 -> 1.9.10 [pfSense]
            suricata: 6.0.4 -> 6.0.4_3 [pfSense]
            vnstat: 2.8 -> 2.9 [pfSense]

            Number of packages to be installed: 4
            Number of packages to be upgraded: 57

            The process will require 9 MiB more space.

            **** WARNING ****
            Reboot will be required!!
            Proceed with upgrade? (y/N) Aborting...

            Then after running pkg-static upgrade I get "up to date" in the Update section as per this screenshot
            Screenshot 2022-06-30 at 09.24.08.png

            Running the pfSense-upgrade via ssh doesn't seem to solve it either:
            sudo pfSense-upgrade -d
            Password:

            Updating repositories metadata...
            Updating pfSense-core repository catalogue...
            Fetching meta.conf: . done
            Fetching packagesite.pkg: . done
            Processing entries: .. done
            pfSense-core repository update completed. 14 packages processed.
            Updating pfSense repository catalogue...
            Fetching meta.conf: . done
            Fetching packagesite.pkg: .......... done
            Processing entries: .......... done
            pfSense repository update completed. 540 packages processed.
            All repositories are up to date.

            The following 61 package(s) will be affected (of 0 checked):

            New packages to be INSTALLED:
            graphite2: 1.3.14 [pfSense]
            harfbuzz: 4.1.0 [pfSense]
            lua54: 5.4.2 [pfSense]
            php74-libbe: 0.1.4 [pfSense]

            Installed packages to be UPGRADED:
            loads of packages and
            pfSense: 22.01 -> 22.05 [pfSense]
            and loads more

            Number of packages to be installed: 4
            Number of packages to be upgraded: 57

            The process will require 9 MiB more space.

            **** WARNING ****
            Reboot will be required!!
            Proceed with upgrade? (y/N) y

            Removing vital flag from php74...
            Downloading upgrade packages...
            Updating pfSense-core repository catalogue...
            pfSense-core repository is up to date.
            Updating pfSense repository catalogue...
            pfSense repository is up to date.
            All repositories are up to date.
            Checking for upgrades (57 candidates): .......... done
            Processing candidates (57 candidates): .......... done
            Checking integrity... done (0 conflicting)
            The following 61 package(s) will be affected (of 0 checked):

            New packages to be INSTALLED:
            graphite2: 1.3.14 [pfSense]
            harfbuzz: 4.1.0 [pfSense]
            lua54: 5.4.2 [pfSense]
            php74-libbe: 0.1.4 [pfSense]

            Installed packages to be UPGRADED:
            bash: 5.1.12 -> 5.1.16 [pfSense]
            bind-tools: 9.16.23 -> 9.16.26 [pfSense]
            clamav: 0.104.1,1 -> 0.104.2,1 [pfSense]
            db5: 5.3.28_7 -> 5.3.28_8 [pfSense]
            devcpu-data: 20211109 -> 20220221 [pfSense]
            dnsmasq: 2.86,1 -> 2.86_3,1 [pfSense]
            dpinger: 3.0 -> 3.2 [pfSense]
            filterdns: 2.0_5 -> 2.0_6 [pfSense]
            fontconfig: 2.13.94_1,1 -> 2.13.94_2,1 [pfSense]
            gdbm: 1.22 -> 1.23 [pfSense]
            graphviz: 2.44.1_17 -> 2.50.0 [pfSense]
            hostapd: 2.9_4 -> 2.10 [pfSense]
            iperf3: 3.10.1_1 -> 3.11 [pfSense]
            libgd: 2.3.1,1 -> 2.3.3,1 [pfSense]
            links: 2.20.2_1,1 -> 2.25,1 [pfSense]
            mpd5: 5.9_6 -> 5.9_7 [pfSense]
            mysql57-client: 5.7.36 -> 5.7.37_1 [pfSense]
            ndpi: 4.0.d20210818,1 -> 4.2.d20220210,1 [pfSense]
            nginx: 1.20.2_1,2 -> 1.20.2_9,2 [pfSense]
            nss: 3.73 -> 3.76 [pfSense]
            ntopng: 5.0.d20210923,1 -> 5.2.d20220314,1 [pfSense]
            ntp: 4.2.8p15_3 -> 4.2.8p15_5 [pfSense]
            openvpn: 2.5.4_1 -> 2.6.0_8 [pfSense]
            pfSense: 22.01 -> 22.05 [pfSense]
            pfSense-pkg-sudo: 0.3_6 -> 0.3_7 [pfSense]
            php74-bz2: 7.4.26 -> 7.4.28 [pfSense]
            php74-ctype: 7.4.26 -> 7.4.28 [pfSense]
            php74-filter: 7.4.26 -> 7.4.28 [pfSense]
            php74-ftp: 7.4.26 -> 7.4.28 [pfSense]
            php74-gettext: 7.4.26 -> 7.4.28 [pfSense]
            php74-intl: 7.4.26 -> 7.4.28 [pfSense]
            php74-json: 7.4.26 -> 7.4.28 [pfSense]
            php74-ldap: 7.4.26 -> 7.4.28 [pfSense]
            php74-opcache: 7.4.26 -> 7.4.28 [pfSense]
            php74-pcntl: 7.4.26 -> 7.4.28 [pfSense]
            php74-pdo_sqlite: 7.4.26 -> 7.4.28 [pfSense]
            php74-pfSense-module: 0.76 -> 0.81 [pfSense]
            php74-posix: 7.4.26 -> 7.4.28 [pfSense]
            php74-readline: 7.4.26 -> 7.4.28 [pfSense]
            php74-session: 7.4.26 -> 7.4.28 [pfSense]
            php74-shmop: 7.4.26 -> 7.4.28 [pfSense]
            php74-simplexml: 7.4.26 -> 7.4.28 [pfSense]
            php74-sockets: 7.4.26 -> 7.4.28 [pfSense]
            php74-sqlite3: 7.4.26 -> 7.4.28 [pfSense]
            php74-sysvmsg: 7.4.26 -> 7.4.28 [pfSense]
            php74-sysvsem: 7.4.26 -> 7.4.28 [pfSense]
            php74-sysvshm: 7.4.26 -> 7.4.28 [pfSense]
            php74-xmlreader: 7.4.26 -> 7.4.28 [pfSense]
            php74-xmlwriter: 7.4.26 -> 7.4.28 [pfSense]
            postgresql13-client: 13.5 -> 13.6 [pfSense]
            py38-libzfs: 1.1.2021100100 -> 1.1.2022021400 [pfSense]
            smartmontools: 7.2_3 -> 7.3 [pfSense]
            socat: 1.7.4.2 -> 1.7.4.3 [pfSense]
            squid: 4.15 -> 5.4.1 [pfSense]
            sudo: 1.9.8p2 -> 1.9.10 [pfSense]
            suricata: 6.0.4 -> 6.0.4_3 [pfSense]
            vnstat: 2.8 -> 2.9 [pfSense]

            Number of packages to be installed: 4
            Number of packages to be upgraded: 57

            The process will require 9 MiB more space.

            Downloading pkg...

            No packages are required to be fetched.
            Integrity check was successful.

            Removing unnecessary packages...
            Checking integrity... done (0 conflicting)
            Nothing to do.
            Activating boot environment default... done.
            System is going to be upgraded. Rebooting in 10 seconds.

            Broadcast Message from nstjh@pfSense.orangehand.lan
            (/dev/pts/0) at 9:31 BST...

            System is going to be upgraded. Rebooting in 10 seconds.

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

              Hmm, so it looks like it was offering you the upgrade but you initially refused it?

              Did you then run it and it is now showing up to date pkgs?

              Crucially it was showing the updated mpd5 which is required for PPPoE:

              mpd5: 5.9_6 -> 5.9_7 [pfSense]

              Steve

              O 1 Reply Last reply Reply Quote 0
              • O
                orangehand @stephenw10
                last edited by

                @stephenw10

                I’m sorry I may have confused myself. Output of pfSense-upgrade in the gui seems to show that all is now up to date. But still no pppoe wan connection can be made. Should I give up, reinstall and restore a backup?

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

                  That's probably quicker if you're able to do that.

                  Steve

                  O 2 Replies Last reply Reply Quote 0
                  • O
                    orangehand @stephenw10
                    last edited by

                    @stephenw10
                    Clean install and restore seems to have got me back up and running. Changed the file system to ZFS.

                    In order to restore + which I previously had should I just request another lab key? Or should I use the previous one if I can find it?

                    Thanks for all your help Steve; the moral of the story is to have a cheap router ready to rock so you can plug pfsense downstream of it and thus retain functionality. Zen's FritzBox has set me in good stead in this instance.

                    1 Reply Last reply Reply Quote 0
                    • O
                      orangehand @stephenw10
                      last edited by

                      @stephenw10
                      Oddly I cannot paste in a key. It's on 2.6 CE, but the register page does not allow pasting - says it already knows the device. Can you advise please?

                      Screenshot 2022-07-01 at 13.40.55.png

                      O 1 Reply Last reply Reply Quote 0
                      • O
                        orangehand @orangehand
                        last edited by

                        @orangehand
                        Sorry - ignore. I hadn't spotted it in the upgrade drop down!

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

                          Like it says there, your device is already registered, you don't need to register again. the NDI doesn't change when you reinstall.

                          Steve

                          O 1 Reply Last reply Reply Quote 0
                          • O
                            orangehand @stephenw10
                            last edited by

                            @stephenw10 So I am back at 22.01 where I was. I'd like to go up to 22.05. What chance do you think of the same chaos ensuing? Am understandably nervous!

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

                              Well I've updated countless things from 22.01 to 22.05 without issue. Including CE > Plus upgraded boxes. So I wouldn't expect any issues. You can never be 100% though since you hit something last time.

                              O 1 Reply Last reply Reply Quote 0
                              • O
                                orangehand @stephenw10
                                last edited by

                                @stephenw10
                                Same again. No WAN post upgrade to 22.05
                                This is a mess!
                                Any ideas?

                                O 1 Reply Last reply Reply Quote 0
                                • O
                                  orangehand @orangehand
                                  last edited by

                                  @orangehand
                                  I’ve got a spare physical port. Might it be worth trying to move the wan interface to it?

                                  O 1 Reply Last reply Reply Quote 0
                                  • O
                                    orangehand @orangehand
                                    last edited by

                                    @orangehand
                                    Just tried igb2. Simply changed WAN to it in interface assignments. Haven’t rebooted. No dice

                                    O 1 Reply Last reply Reply Quote 0
                                    • O
                                      orangehand @orangehand
                                      last edited by

                                      @orangehand
                                      Rebooted. No change

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

                                        You see the same error? Same output from pkg info -x pfSense?

                                        I note you have Squid running, I wonder if that is getting stuck reinstalling.

                                        O 1 Reply Last reply Reply Quote 0
                                        • O
                                          orangehand @stephenw10
                                          last edited by

                                          @stephenw10

                                          Shell Output - pkg info -x pfSense
                                          pfSense-22.01
                                          pfSense-Status_Monitoring-1.7.11_4
                                          pfSense-base-22.05
                                          pfSense-default-config-serial-22.05
                                          pfSense-kernel-pfSense-22.05
                                          pfSense-pkg-Status_Traffic_Totals-2.3.2_2
                                          pfSense-pkg-acme-0.7.1_1
                                          pfSense-pkg-bandwidthd-0.7.4_5
                                          pfSense-pkg-iperf-3.0.2_5
                                          pfSense-pkg-ntopng-0.8.13_10
                                          pfSense-pkg-openvpn-client-export-1.6_4
                                          pfSense-pkg-pfBlockerNG-devel-3.1.0_4
                                          pfSense-pkg-squid-0.4.45_8
                                          pfSense-pkg-squidGuard-1.16.18_20
                                          pfSense-pkg-sudo-0.3_7
                                          pfSense-pkg-suricata-6.0.4_1
                                          pfSense-rc-22.05
                                          pfSense-repo-22.05_2
                                          pfSense-upgrade-1.0_26
                                          php74-pfSense-module-0.76

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

                                            @orangehand said in Upgrade to 22.05 has killed my pppoe WAN:

                                            pfSense-22.01

                                            Yeah, it still has the 22.01 meta package. If you run pkg upgrade it should offer you the upgrades to the current versions of anything that didn't update correctly.

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