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.3k 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.
    • S
      Sissy @stephenw10
      last edited by

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

      Yeah, I see how this is failing. And would always have failed.

      https://redmine.pfsense.org/issues/16266

      Sorry for my delay in replying. Working through the 2.8.0 update process today pushed the cores well above where I had the Zone Warning set. That's probably why this problem only today caught my eye.

      Thank you for so quickly jumping on this and determining the root cause. I see that you've targeted the fix for 2.9.0, which I fear could be a long way off. Is there any chance of creating a patch for 2.8.0 sometime in the next few months? I mean that as a humble ask, not an entitled demand.

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

        Yup you can test the patch if you're able to:

        1231.diff

        S 1 Reply Last reply Reply Quote 3
        • S
          Sissy @stephenw10
          last edited by

          @stephenw10 Works great! I just did a cut & paste from the file to the System_Patches utility, pasted the description "Thermal Sensors Widget Thresholds not Evaluated," and applied the patch. The problem was immediately fixed, with the following screenshot showing the results (with test values for thresholds to illustrate the change):

          a2d7dbb1-d7ca-4bba-b5c6-dbe7ab69a997-image.png

          If you're planning to push it out as a formal patch, I think that you're good to go.

          Thanks again!

          1 Reply Last reply Reply Quote 2
          • stephenw10S stephenw10 forked this topic
          • B
            bimmerdriver
            last edited by

            I upgraded a couple of weeks ago. I mistakenly forgot to remove snort before upgrading, but it didn't seem to cause any obvious problems.

            I have noticed that the GUI is often slow and frequently reports "This site can't be reached..." Refreshing a few times usually brings it back.

            This morning, I started having major problems with DHCP and Unbound. This started when I attempted to reassign a couple of DHCP reservations to make room in the sequence for a new server.

            I deleted the existing reservation, then used ipconfig /release and ipconfig /renew to force the host to get a new dynamic address, which worked fine. Then I created a new reservation and again used ipconfig /release and ipconfig /renew to force the host to use the new address.

            After this, pfSense shows the new reservation is active, but the host is still using the DHCP address. I tried restarting the DHCP service on the host and it made no difference.

            To see if this problem was specific to the host, I tried the same procedure on another host. It worked, so I tried one more to see what would happen. It failed.

            By this time, the GUI was very slow and was frequently unresponsive, unbound was stopped and would not restart, then crash reports started.

            Here are some messages from the DHCP log:

            Jul 5 16:41:56	kea2unbound	32656	Unbound reloaded: /var/unbound/unbound.conf
Jul 5 16:41:56	kea2unbound	32656	Include updated: /var/unbound/leases/leases4.conf (5404252cd3db2c6d)
Jul 5 16:41:56	kea2unbound	32656	Unbound lease include is missing or inconsistent: /var/unbound/leases/leases4.conf
Jul 5 16:41:55	kea-dhcp6	30761	WARN [kea-dhcp6.dhcp6.0x199b00612000] DHCP6_MULTI_THREADING_INFO enabled: yes, number of threads: 2, queue size: 64
Jul 5 16:41:55	kea-dhcp4	30320	WARN [kea-dhcp4.dhcp4.0x169f0cc12000] DHCP4_MULTI_THREADING_INFO enabled: yes, number of threads: 2, queue size: 64
Jul 5 16:41:55	kea-dhcp6	30761	WARN [kea-dhcp6.dhcp6.0x199b00612000] DHCP6_RESERVATIONS_LOOKUP_FIRST_ENABLED Multi-threading is enabled and host reservations lookup is always performed first.
Jul 5 16:41:55	kea-dhcp6	30761	WARN [kea-dhcp6.dhcpsrv.0x199b00612000] DHCPSRV_MT_DISABLED_QUEUE_CONTROL disabling dhcp queue control when multi-threading is enabled.
Jul 5 16:41:55	kea-dhcp4	30320	WARN [kea-dhcp4.dhcp4.0x169f0cc12000] DHCP4_RESERVATIONS_LOOKUP_FIRST_ENABLED Multi-threading is enabled and host reservations lookup is always performed first.
Jul 5 16:41:55	kea-dhcp4	30320	WARN [kea-dhcp4.dhcpsrv.0x169f0cc12000] DHCPSRV_MT_DISABLED_QUEUE_CONTROL disabling dhcp queue control when multi-threading is enabled.

            I will update this with some crash reports.

            B GertjanG 2 Replies Last reply Reply Quote 0
            • B
              bimmerdriver @bimmerdriver
              last edited by

              @bimmerdriver Here are some bug reports:

              [05-Jul-2025 14:41:35 America/Vancouver] PHP Fatal error:  Uncaught TypeError: array_get_path(): Argument #1 ($arr) must be of type array, string given, called in /usr/local/pfSense/include/www/services_dhcp.inc on line 174 and defined in /etc/inc/util.inc:3961
Stack trace:
#0 /usr/local/pfSense/include/www/services_dhcp.inc(174): array_get_path()
#1 /etc/inc/system.inc(629): kea6_earlydnsreg_mappings()
#2 /etc/inc/system.inc(660): system_hosts_entries()
#3 /etc/inc/services.inc(4983): system_hosts_generate()
#4 /etc/rc.linkup(164): services_unbound_configure()
#5 /etc/rc.linkup(236): handle_argument_group()
#6 {main}
  thrown in /etc/inc/util.inc on line 3961
[05-Jul-2025 14:41:39 America/Vancouver] PHP Fatal error:  Uncaught TypeError: array_get_path(): Argument #1 ($arr) must be of type array, string given, called in /usr/local/pfSense/include/www/services_dhcp.inc on line 174 and defined in /etc/inc/util.inc:3961
Stack trace:
#0 /usr/local/pfSense/include/www/services_dhcp.inc(174): array_get_path()
#1 /etc/inc/system.inc(629): kea6_earlydnsreg_mappings()
#2 /etc/inc/system.inc(660): system_hosts_entries()
#3 /etc/inc/interfaces.inc(4459): system_hosts_generate()
#4 /etc/rc.linkup(177): interface_configure()
#5 /etc/rc.linkup(236): handle_argument_group()
#6 {main}
  thrown in /etc/inc/util.inc on line 3961
[05-Jul-2025 14:42:07 America/Vancouver] PHP Fatal error:  Uncaught TypeError: array_get_path(): Argument #1 ($arr) must be of type array, string given, called in /usr/local/pfSense/include/www/services_dhcp.inc on line 174 and defined in /etc/inc/util.inc:3961
Stack trace:
#0 /usr/local/pfSense/include/www/services_dhcp.inc(174): array_get_path()
#1 /etc/inc/system.inc(629): kea6_earlydnsreg_mappings()
#2 /etc/inc/system.inc(660): system_hosts_entries()
#3 /etc/inc/services.inc(4983): system_hosts_generate()
#4 /etc/rc.linkup(164): services_unbound_configure()
#5 /etc/rc.linkup(236): handle_argument_group()
#6 {main}
  thrown in /etc/inc/util.inc on line 3961
[05-Jul-2025 14:42:12 America/Vancouver] PHP Fatal error:  Uncaught TypeError: array_get_path(): Argument #1 ($arr) must be of type array, string given, called in /usr/local/pfSense/include/www/services_dhcp.inc on line 174 and defined in /etc/inc/util.inc:3961
Stack trace:
#0 /usr/local/pfSense/include/www/services_dhcp.inc(174): array_get_path()
#1 /etc/inc/system.inc(629): kea6_earlydnsreg_mappings()
#2 /etc/inc/system.inc(660): system_hosts_entries()
#3 /etc/inc/interfaces.inc(4459): system_hosts_generate()
#4 /etc/rc.linkup(177): interface_configure()
#5 /etc/rc.linkup(236): handle_argument_group()
#6 {main}
  thrown in /etc/inc/util.inc on line 3961

              Let me know if any other information would be helpful.

              Since the system is running so poorly, I'm considering reinstalling it from scratch. I don't know what else to do.

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

                I would run pkg-static upgrade and make sure there are no upgraded packages offered. If it aborted the upgrade part way through for any reason that can result in errors like that.

                B 1 Reply Last reply Reply Quote 0
                • B
                  bimmerdriver @stephenw10
                  last edited by

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

                  pkg-static upgrade

                  Thank you for the reply. I tried that and it reported that the system is already up to date.

                  The thread, Unbound Keeps restarting, is reporting the same symptoms, so I will give the posted solution a try.

                  B 1 Reply Last reply Reply Quote 0
                  • GertjanG
                    Gertjan @bimmerdriver
                    last edited by

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

                    Here are some messages from the DHCP log:

                    Jul 5 16:41:56 kea2unbound 32656 Unbound reloaded: /var/unbound/unbound.conf
                    ....

                    These are the usual dhcpv6 and v4 startup messages. They are flagged as "WARN" but are just "information".

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

                    [05-Jul-2025 14:41:35 America/Vancouver] PHP Fatal error: Uncaught TypeError: array_get_path(): Argument #1 ($arr) must be of type array, string given, called in /usr/local/pfSense/include/www/services_dhcp.inc on line 174 and defined in /etc/inc/util.inc:3961

                    The function array_get_path() is a configuration file access helper function.
                    As @stephenw10 implicitly said :: if this function fails, wrong file version are used.
                    Or it's this :

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

                    Argument #1 ($arr) must be of type array, string given

                    "<dhcpv6>" is searched in the config file.
                    Oen yours in a aditor (NOtepad++) and look for "<dhcpv6>" and see for yourself.
                    Normally, it's a array type called <dhcpv6> and it should contain, for each LAN type interface , a section, like <lan>, <opt1>, >opt2> etc.
                    Like, this :

                    659110b7-b579-469c-8635-0fcf7eea697c-image.png

                    It looks like your <dhcpc6> is totally empty ?!?, thus not an array (filled with per LAN interface dhcpv6 setting), so it became a simple text string => that's the error.

                    <dhcpc6> empty : go to your dhcpv6 settings page(s) and save them all.
                    This should populate <dhcpc6>, thus it becomes an array, and the error will be gone.

                    Why all you array items (<lan>, <opt1>, >opt2> etc) in <dhcpc6> were gone : I can't tell.

                    No "help me" PM's please. Use the forum, the community will thank you.
                    Edit : and where are the logs ??

                    1 Reply Last reply Reply Quote 1
                    • B
                      bimmerdriver @bimmerdriver
                      last edited by

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

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

                      pkg-static upgrade

                      Thank you for the reply. I tried that and it reported that the system is already up to date.

                      The thread, Unbound Keeps restarting, is reporting the same symptoms, so I will give the posted solution a try.

                      As I reported in the referenced thread, I was able to get the system working properly again by disabling and reenabling DHCPv4 and DHCPv6 and the respective DNS settings. The first time I did it, DHCPv4 started working properly. After I did it a second time, DHCPv6 also started working properly. I have no idea why this happened in the first place, but it's at least fixed (for now).

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

                        And it's definitely still resolving new leases?

                        B 1 Reply Last reply Reply Quote 0
                        • B
                          bimmerdriver @stephenw10
                          last edited by

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

                          And it's definitely still resolving new leases?

                          Yes, it appears to be working normally since.

                          1 Reply Last reply Reply Quote 1
                          • M
                            mark_lab_user
                            last edited by

                            I completely forgot that I was running 2.7.2 with manually installed realtek drivers for my $10 2.5Gbit cards. Needless to say the upgrade failed due to unknown reasons because I did not have screen plugged in at the time. So I bricked the system. But I don't have any screen captures. Also, I rebooted and specified "kernel.old" so that I could at least boot but then I could not get PPPoE to work. I just might walk away from the mess. Too many hours and real Netgate hardware is too costly. So for now, my only option was to call my ISP and ask them to take their garbage router out of bridge mode so I could get my lab back working sort of.

                            It was all my fault.

                            But one last word... Why did you not add the Realtek 2.5 Gb drivers? They have been stable forever.

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

                              We build the module as a package so if you had it installed in 2.7.2 and upgrade it will upgrade the package and you should have it still in 2.8.

                              But it appears that the driver now has two builds because the newest version is not stable with some hardware. You might have hit that since the package we build is the new version.

                              M 1 Reply Last reply Reply Quote 0
                              • M
                                mark_lab_user @stephenw10
                                last edited by

                                Thanks. Maybe someday I will get some Intel cards but even Intel had a serious bug if I recall. There is a certain Intel card/chipset that went horribly wrong if I recall. Just can't remember what version to avoid.

                                M C 2 Replies Last reply Reply Quote 0
                                • M
                                  mark_lab_user @mark_lab_user
                                  last edited by

                                  Is there an archive of 2.7.2 iso?
                                  (I did find 2.7.0).

                                  I am thinking about installing 2.7.2 under Proxmox 8.4. My current Proxmox 8.4 is giving me stable speeds of 2.35 Gbits per second with 'iperf3' tests to a Debian desktop machine thru a cheap 2.5/10Gbit switch.

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

                                    https://atxfiles.netgate.com/mirror/downloads/

                                    M 1 Reply Last reply Reply Quote 0
                                    • M
                                      mark_lab_user @stephenw10
                                      last edited by

                                      Thank you for your help. As you can see I am not ready to go to Opnsense yet. I think Proxmox will be prudent. Snapshots and portability when my lab stuff crashes such as yesterday.

                                      1 Reply Last reply Reply Quote 0
                                      • C
                                        chrcoluk @mark_lab_user
                                        last edited by

                                        @mark_lab_user i226 seems pretty solid. It also got some good driver work done on it recently as well.

                                        All intel gigabit cards should be solid as well, i210, i350 etc.

                                        pfSense CE 2.8.0

                                        1 Reply Last reply Reply Quote 1
                                        • S
                                          sTicKs23
                                          last edited by

                                          Is it just me or the world's most trusted open-source firewall didn't post the RELENG_2_8_0 branch on GitHub anymore?
                                          Are you guys using a different git repository or open-source is just a marketing ad for v2.8.0?

                                          GertjanG 1 Reply Last reply Reply Quote 0
                                          • GertjanG
                                            Gertjan @sTicKs23
                                            last edited by

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

                                            RELENG_2_8_0

                                            Let's say it's called 'master' (for now) - and check again ?

                                            No "help me" PM's please. Use the forum, the community will thank you.
                                            Edit : and where are the logs ??

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