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

    New pfSense Plus 25.03-BETA is here!

    Scheduled Pinned Locked Moved Messages from the pfSense Team
    18 Posts 9 Posters 3.7k 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.
    • chudakC
      chudak
      last edited by

      No upgrade path 24.03 => 25.03?

      M GertjanG 2 Replies Last reply Reply Quote 0
      • M
        mcury Rebel Alliance @chudak
        last edited by

        Testing now.. so far so good.

        Upgrade from 24.11 in a SG-4100 took around 10 minutes.
        All packages still working , no problems to report yet.

        • acme
        • arpwatch
        • aws-wizard
        • iperf
        • ipsec-profile-wizard
        • lldpd
        • Netgate_Firmware_Upgrade
        • nmap
        • nut (UPS not directly connected to pfSense, remote server configured).
        • pfBlockerNG-devel (DNSBL disabled, only using IP block lists).
        • Service_Watchdog
        • System_Patches
        • WireGuard

        Thanks Netgate team.

        dead on arrival, nowhere to be found.

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

          @chudak said in New pfSense Plus 25.03-BETA is here!:

          No upgrade path 24.03 => 25.03?

          I saw the same question somewhere already, the answer was : go to 24.11 first. You don't need to stay long there, you can then access the second Beta : 25.03.b.20250306.0140.

          Btw : 25.03.b.20250306.0140 rock solid for me.
          ( not using pppoe )

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

          M chudakC 2 Replies Last reply Reply Quote 0
          • M
            mr_nets @Gertjan
            last edited by

            Regarding the PPPoE optimization, is it on track I didn't see any mention about that in the release note and no one has given any feedback?

            M J 2 Replies Last reply Reply Quote 0
            • M
              mcury Rebel Alliance @mr_nets
              last edited by

              Weird, I'm observing some weird logs after updating to 25.03 BETA.
              These are new, checked several days behind and only found these after the update.

              1e5a1120-c31e-4923-8ea0-9265a9c7b8f0-image.png

              Found this topic that may relate to this issue: https://forum.netgate.com/topic/195347/seeing-kea-dhcp-issues-after-upgrade-to-24-11/24

              echo '{"command":"config-get"}' | nc -U /var/run/kea4-ctrl-socket | jq
              echo '{"command":"lease4-get-all"}' | nc -U /var/run/kea4-ctrl-socket | jq

              first_command.txt second_command.txt

              Cleared DHCP leases but the issue still persists.

              Kindly let me know if you need more details, thanks.

              dead on arrival, nowhere to be found.

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

                @mcury said in New pfSense Plus 25.03-BETA is here!:

                first_command.txt

                Use this command :

                echo '{"command":"config-get"}' | nc -U /var/run/kea4-ctrl-socket | jq | grep 'pool'

                Yours showed :

                25cd8ad2-b434-470a-a297-64bb49429a30-image.png

                Are you sure ? /32 means : 1 lease avaible !?

                I have :

                [25.03-BETA][root@pfSense.bhf.tld]/root: echo '{"command":"config-get"}' | nc -U /var/run/kea4-ctrl-socket | jq | grep 'pool'
          "name": "pool_lan_0",
          "name": "pool_opt2_0",
          "name": "pool_opt1_0",
        "thread-pool-size": 0
      "reservations-out-of-pool": false,
          "pools": [
              "client-class": "pool_lan_0",
              "pool": "192.168.1.70-192.168.1.200"
          "pools": [
              "client-class": "pool_opt2_0",
              "pool": "192.168.2.15-192.168.2.254"
          "pools": [
              "client-class": "pool_opt1_0",
              "pool": "192.168.100.50-192.168.100.100"

                My pool go from, on 3 interfaces :
                LAN : 192.168.1.70 to 192.168.1.200 = 130 Lease avaible.
                OPT1: 192.168.2.15 to 192.168.2.254 = 240 leases avaible.
                OPT2 : 92.168.100.50-192.168.100.100 = 50 leases avaible.

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

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

                  @Gertjan

                  edit : Your other pool "pool_opt4_0" looks fine : 192.168.20.2->192.168.20.253

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

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    mcury Rebel Alliance @Gertjan
                    last edited by

                    Hello Gertjan, thanks for the input.

                    edit : Your other pool "pool_opt4_0" looks fine : 192.168.20.2->192.168.20.253

                    It is correct, just one lease in that VLAN, all devices are known.
                    For OPT4, it is a GUEST vlan.

                    dead on arrival, nowhere to be found.

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

                      @mcury said in New pfSense Plus 25.03-BETA is here!:

                      It is correct, just one lease

                      Can't you give it some more space to breath ?
                      Just to little 192.168.10.15 to 192.168.10.16 ? ( /31)

                      ALLOC_FAIL_NO_POOL
                      +
                      ALLOC_FAIL_SUBNET
                      = fail as you entered a subnet thing (the /32) where an pool (barrier) was expected ?

                      How did you enter this pool ?
                      Like this :

                      2bc935ac-92bf-4612-9da9-8380286fabfc-image.png

                      ?

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

                      M 1 Reply Last reply Reply Quote 0
                      • M
                        mcury Rebel Alliance @Gertjan
                        last edited by

                        @Gertjan said in New pfSense Plus 25.03-BETA is here!:

                        How did you enter this pool ?
                        Like this :

                        Yeap, exactly like that.

                        dead on arrival, nowhere to be found.

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

                          @mcury

                          What happens when you give it more space ?

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

                          M 1 Reply Last reply Reply Quote 0
                          • M
                            mcury Rebel Alliance @Gertjan
                            last edited by

                            @Gertjan said in New pfSense Plus 25.03-BETA is here!:

                            What happens when you give it more space ?

                            I'll try it, good observation.
                            As soon as I go back home I'll change it from 192.168.10.15-192.168.10.15 to 192.168.10.15-192.168.10.16 and I'll come here to update this thread with my findings.

                            dead on arrival, nowhere to be found.

                            1 Reply Last reply Reply Quote 0
                            • chudakC
                              chudak @Gertjan
                              last edited by

                              @Gertjan said in New pfSense Plus 25.03-BETA is here!:

                              @chudak said in New pfSense Plus 25.03-BETA is here!:

                              No upgrade path 24.03 => 25.03?

                              I saw the same question somewhere already, the answer was : go to 24.11 first. You don't need to stay long there, you can then access the second Beta : 25.03.b.20250306.0140.

                              Btw : 25.03.b.20250306.0140 rock solid for me.
                              ( not using pppoe )

                              I had issues with 24.11 and therefore decided to wait for 25.03. Hope it will be available in the final RC

                              1 Reply Last reply Reply Quote 0
                              • U
                                UweV
                                last edited by

                                Hello, where in this forum can I report feedback for this beta version? (2.8 beta)
                                Topic: Fixed: Old IPv6 addresses may continue to be used after DHCP or RA changes #12947
                                (included also in 25.03 beta)

                                Thank you.

                                bmeeksB 1 Reply Last reply Reply Quote 0
                                • bmeeksB
                                  bmeeks @UweV
                                  last edited by

                                  @UweV said in New pfSense Plus 25.03-BETA is here!:

                                  Hello, where in this forum can I report feedback for this beta version? (2.8 beta)
                                  Topic: Fixed: Old IPv6 addresses may continue to be used after DHCP or RA changes #12947
                                  (included also in 25.03 beta)

                                  Thank you.

                                  Here is the forum link: https://forum.netgate.com/category/102/plus-25-03-develoment-snapshots.

                                  If you have a verified bug report along with information about how to reliably reproduce the issue, you can submit a Redmine bug report here: https://redmine.pfsense.org/projects/pfsense.

                                  1 Reply Last reply Reply Quote 0
                                  • M
                                    mak73
                                    last edited by

                                    I am testing now also 2.8 Beta, PERFECT! THX

                                    1 Reply Last reply Reply Quote 0
                                    • J
                                      jwt Netgate @mr_nets
                                      last edited by

                                      @mr_nets it's in this beta

                                      1 Reply Last reply Reply Quote 3
                                      • M mwatch unpinned this topic on
                                      • First post
                                        Last post
                                      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.