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

    Now Available: pfSense® CE 2.8.0-RELEASE

    Scheduled Pinned Locked Moved Messages from the pfSense Team
    112 Posts 24 Posters 18.2k 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.
    • fireodoF
      fireodo @sokeada
      last edited by

      @sokeada said in Now Available: pfSense® CE 2.8.0-RELEASE:

      take out the hardware wifi card from the machine...

      Hi,

      in my humble opinion that whould be the best - if possible!

      Regards,
      fireodo

      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.

      sokeadaS 1 Reply Last reply Reply Quote 0
      • sokeadaS
        sokeada @fireodo
        last edited by

        @fireodo thanks for the tips, I'll spare sometime to shutdown and take out the wifi card then. Just only take out the card, that's it? no extra task to turn off in bios or add in local config file, right?

        Best Regards,

        Sokeada

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

          @sokeada said in Now Available: pfSense® CE 2.8.0-RELEASE:

          Just only take out the card, that's it?

          Yes, thats it - if you remove physically the WLAN-Card neither BIOS nor pfsense (freebsd) Kernel can detect her anymore :-)

          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.

          sokeadaS 1 Reply Last reply Reply Quote 0
          • N
            netblues @sokeada
            last edited by

            @sokeada Obviously, since after upgrading there will be no access to the system, as it fails, you have to do everything on 2.7 before upgrading.

            Οf course if you can take out the card its easier.

            sokeadaS 1 Reply Last reply Reply Quote 0
            • sokeadaS
              sokeada @fireodo
              last edited by

              @fireodo thanks, I really appreciate your suggestions.

              1 Reply Last reply Reply Quote 1
              • sokeadaS
                sokeada @netblues
                last edited by

                @netblues thanks, I really appreciate your suggestions.

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

                  @netblues said in Now Available: pfSense® CE 2.8.0-RELEASE:

                  It is always like that before the upgrade.

                  In fact it would usually appear just as 2.8.0 for the available version but some changes to the builder resulted in 2.7.2 seeing the appended kernel version there. At what will probably be 2.8.1 it will just show 2.8.1. But, yes, safe to upgrade.

                  I agree removing the hardware is the best option to prevent that panic. It's doing nothing but consuming resources whilst present.

                  But, yes, you could add the loader disable hint to /boot/loader.conf.local whilst in 2.7.2 and then upgrade. It would still apply in 2.8.

                  Or if you are already in 2.8 you can interrupt the bootloader to reach the OK> prompt and set the hint there manually to allow it to boot. Then add it to the loader file once it's booted so it reboots OK next time.

                  S sokeadaS 2 Replies Last reply Reply Quote 0
                  • R
                    RodSlinger
                    last edited by

                    Did a dirty upgrade with pfBlockerNG-devel and snort running. Just had to restart pfBlocker after finishing the upgrade and all is well.

                    1 Reply Last reply Reply Quote 2
                    • fireodoF
                      fireodo
                      last edited by

                      I did the upgrade 2.7.2 -> 2.8.0 with all the packages (see signature) in place without any issues :-) but I recommend to take the netgate advise serious and uninstall the packages before upgrade ...

                      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
                      • W
                        Waqar.UK
                        last edited by

                        I know that removing before upgrade is the best possible way. But I upgraded without doing this. But backup the config file before.

                        1 Reply Last reply Reply Quote 0
                        • S
                          SteveITS Galactic Empire @stephenw10
                          last edited by

                          @stephenw10 I suspect the question was about the "pfSense-repoc: no pfSense packages installed" error. But, the upgrade seems to have run.

                          On our one client with a 2.7.2 VM, after changing branches I don't see that but do see a "pfSense-repoc: open: No such file or directory" message.

                          Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                          When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                          Upvote 👍 helpful posts!

                          S stephenw10S 2 Replies Last reply Reply Quote 0
                          • S
                            SteveITS Galactic Empire @SteveITS
                            last edited by

                            @SteveITS said in Now Available: pfSense® CE 2.8.0-RELEASE:

                            I don't see that

                            I can't seem to edit my post, but after changing back to 2.7.2 I do see the "pfSense-repoc: no package 'name' pfSense-repoc: no pfSense packages installed" message.

                            Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                            When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                            Upvote 👍 helpful posts!

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

                              @SteveITS said in Now Available: pfSense® CE 2.8.0-RELEASE:

                              but do see a "pfSense-repoc: open: No such file or directory" message.

                              Yup, it should still upgrade though if you set the branch to 2.8. That was a bug in an old repoc version but it should be upgraded by setting 2.8. Also it was cosmetic only is should still function.

                              1 Reply Last reply Reply Quote 0
                              • sokeadaS
                                sokeada @stephenw10
                                last edited by

                                @stephenw10 thanks for multiple solutions, I'll shutdown pfSense and remove WiFi Card during today break time then I'll start to upgrade again.

                                1 Reply Last reply Reply Quote 1
                                • T
                                  tgbauer @pfGeorge
                                  last edited by

                                  @pfGeorge New version is working well for me so far. Looks like there is a missing closing ")" in the second line of the SHA256 file here: https://www.netgate.com/hubfs/pfSense-plus-installer-checksums.txt

                                  This produces an error:

                                  % sha256sum -c pfSense-plus-installer-checksums.txt
                                  netgate-installer-amd64.img.gz: OK
                                  netgate-installer-aarch64.img.gz: OK
                                  sha256sum: WARNING: 1 line is improperly formatted
                                  

                                  After adding the closing ")", it works as expected:

                                  % sha256sum -c pfSense-plus-installer-checksums.txt
                                  netgate-installer-amd64.img.gz: OK
                                  netgate-installer-amd64.iso.gz: OK
                                  netgate-installer-aarch64.img.gz: OK
                                  
                                  1 Reply Last reply Reply Quote 0
                                  • J
                                    jiri.zemanek
                                    last edited by

                                    I need to compile a kernel driver. So I downloaded the pfSense/FreeBSD-src repository from GitHub, but there is no RELENG_2_8_0 branch. Using uname -a I thought there is a commit ID displayed but I have not found it in the repository either. So where do I get the FreeBSD source for this release?

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

                                      What driver do you need?

                                      1 Reply Last reply Reply Quote 0
                                      • J
                                        jiri.zemanek @jiri.zemanek
                                        last edited by

                                        @jiri-zemanek OK, by using git blame ./sys/sys/param.h in the devel-main branch and traversing backwards I found

                                        46297859a745 (John Baldwin        2024-12-06 17:25:04 -0500  76) #define __FreeBSD_version 1500029
                                        

                                        which is the same version that reports sysctl kern.osreldate. So I'll use that.

                                        1 Reply Last reply Reply Quote 1
                                        • J
                                          jiri.zemanek
                                          last edited by

                                          OK, so I installed 2.8.0 CE via the netgate installer ISO and now I am trying to install ACME plugin:

                                          WARNING: Current pkg repository has a new PHP major
                                                   version. pfSense should be upgraded before
                                                   installing any new package.
                                          

                                          When looking at the System --> Update, it says:

                                          Current Base System  2.8.0
                                          Latest Base System   2.7.0
                                          Status               Running a newer version.
                                          

                                          So not sure HOW...

                                          It seems this release is so hot that it's still glowing...

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

                                            It looks like your update branch is somehow set to 2.7.0. Did you restore a config with that set?

                                            Do you see the 2.8.0 branch available to set?

                                            Are you using any custom repos?

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