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
    48 Posts 10 Posters 6.5k 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.
    • N
      netblues @SteveITS
      last edited by

      @SteveITS Comparing Microsoft to Netgate has its own merits :)
      Do you really think that expect from the ones that lurk in this forum, anyone has a clue what 25.03 really stands for?

      In any case its nice to see 2.8ce released, and its rater safe to expect a plus rc really soon.

      I guess all those comments regarding abandoned ce version are now irrelevant too.

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

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

        @SteveITS Comparing Microsoft to Netgate has its own merits :)
        Do you really think that apart from the ones that lurk in this forum, anyone has a clue what 25.03 really stands for?

        In any case its nice to see 2.8ce released, and its rater safe to expect a plus rc really soon.

        I guess all those comments regarding abandoned ce version are now irrelevant too.

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

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

          all those comments regarding abandoned ce version are now irrelevant too.

          Are you kidding?? There's no source code available for 2.9! :(

          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!

          N GertjanG 2 Replies Last reply Reply Quote 0
          • N
            netblues @SteveITS
            last edited by

            @SteveITS So does this make it an abandoned project?

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

              @SteveITS

              No source (code ?) for 2.9 ?

              Took me one click to find this https://github.com/pfsense/pfsense :

              71593a99-41b3-4df9-9210-b2945c4fdece-image.png

              and just for fun, see what marcos-ng wrote a couple of hours ago : it's a solution for the IGMP firewall log issue, see elsewhere on the forum.
              So, that one didn't make it into 2.8.0 and will be part a future version, let's say "2.9.0".

              I probably just listed the first official System path for 2.8.0 😊
              And because pfSense plus 25.0x will come out later on this solution will get included.

              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
              • GertjanG Gertjan referenced this topic
              • I
                ITSGS_
                last edited by

                I just updated my SG4200 to 25.03. BETA which worked flawlessly. I'm using ACME, DDNS, pfBlockerNG, OpenVPN, Unbound. Also switched to new PPoE method. It fixed the Ram Drive size and it seems that I no longer have problems connecting to MS Teams. In the past couple of months I had to update (change MTU or something else) my PPoE WAN Interface to be able to join MS Teams meetings. After 1-2 hours I had to reset the WAN Interface again to be able to join again. Up until today I was not able to figure out what it was, but it seems that it is fixed now.

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

                  @ITSGS_ Rest assured, your issues with teams and previous versions have nothing to do with pfsense per se or pppoe. Far too many users are doing exaclty the same, for years now.

                  These are provider things, that just happened to be fixed at the same time period.

                  I 1 Reply Last reply Reply Quote 0
                  • I
                    ITSGS_ @netblues
                    last edited by

                    @netblues I'm not too sure about that. My neighbour is working at the same company and has the same internet provider but a different router. He had no issues. I just wanted to let the internet know in case someone has the same problem.

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

                      @ITSGS_ If there are mtu issues then nothing really works.
                      Same goes for disconnections.
                      In a ppp connection it always take two to tango
                      One is the isp bras and the other is the pppoe client.

                      Since the protocol is far too old to have issues, switching to the new, multi kernel optimized version, can't solve anything on the mtu or stability side too.

                      I don't say what you observed is untrue.
                      However doing a root cause analysis here seems impossible.

                      I 1 Reply Last reply Reply Quote 0
                      • I
                        ITSGS_ @netblues
                        last edited by

                        @netblues All true what you said. I do not know the cause. I neither captured packages or did anything else. It's just "a guess". But the information that it works after switching to the BETA might help somebody searching for a "easy" solution.

                        Next time I won't be lazy and start a topic about it. :-)

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

                          The final Beta ? :

                          5eb0aa1b-6b41-4aca-a0f7-44336d7ca886-image.png

                          fingers crossed : the RC will be coming out soon now.

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

                          N 1 Reply Last reply Reply Quote 2
                          • N
                            netblues @Gertjan
                            last edited by

                            @Gertjan The final countdown (the song)
                            Upgraded (dirty) under kvm.
                            No issues

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

                              One minor thing that might need some looking after :
                              The 'console' boot sequence needs some polishing.

                              This :

                              Syncing OpenVPN settings...done.
ovpn0: changing name to 'ovpns1'
Configuring firewall......done.
Starting PFLOG...done.
Setting up gateway monitors...done.
Setting up static routes...igc0: link state changed to UP
2025-06-11T09:25:35.113521+02:00 pfSense.bhf.tld php-fpm 20265 - - /rc.linkup: Ignoring link event during boot sequence.
done.
Setting up DNSs...
arp: 192.168.1.20 moved from 28:70:4e:62:31:5d to 0c:ea:14:44:4a:38 on igc0
2025-06-11T09:25:35.415824+02:00 pfSense.bhf.tld php-fpm 20265 - - /rc.linkup: Ignoring link event during boot sequence.
2025-06-11T09:25:35.529452+02:00 pfSense.bhf.tld php-fpm 20265 - - /rc.newwanip: rc.newwanip: Info: starting on ovpns1.
2025-06-11T09:25:35.529968+02:00 pfSense.bhf.tld php-fpm 20265 - - /rc.newwanip: rc.newwanip: on (IP address: 192.168.3.1) (interface: VPNS[opt3]) (real interface: ovpns1).
2025-06-11T09:25:35.757933+02:00 pfSense.bhf.tld php-fpm 580 - - /rc.linkup: Ignoring link event during boot sequence.
2025-06-11T09:25:35.841945+02:00 pfSense.bhf.tld php-fpm 581 - - /rc.newwanipv6: rc.newwanipv6: Info: starting on ix3 due to RELEASE.
2025-06-11T09:25:35.843195+02:00 pfSense.bhf.tld php-fpm 581 - - /rc.newwanipv6: rc.newwanipv6: on (IP address: 2a01:cb19:dead:beef:92ec:77ff:fe29:392a) (interface: wan) (real interface: ix3).
2025-06-11T09:25:35.855015+02:00 pfSense.bhf.tld php-fpm 20265 - - /rc.newwanip: Removing static route for monitor2001:41d0:2:927b::3 and adding a new route through fe80::46d4:54ff:fe2a:3600%ix3
2025-06-11T09:25:35.872420+02:00 pfSense.bhf.tld php-fpm 20265 - - /rc.newwanip: Removing static route for monitor94.23.251.218 and adding a new route through 192.168.10.1
2025-06-11T09:25:35.907848+02:00 pfSense.bhf.tld php-fpm 581 - - /rc.newwanipv6: Removing static route for monitor2001:41d0:2:927b::3 and adding a new route through fe80::46d4:54ff:fe2a:3600%ix3
2025-06-11T09:25:35.930399+02:00 pfSense.bhf.tld php-fpm 581 - - /rc.newwanipv6: Removing static route for monitor94.23.251.218 and adding a new route through 192.168.10.1
Starting DNS Resolver...2025-06-11T09:25:36.991434+02:00 pfSense.bhf.tld php-fpm 581 - - /rc.newwanipv6: The command '/usr/local/bin/dpinger -S -r 0 -i WAN_DHCP6 -B 2a01:cb19:dead:beef:92ec:77ff:fe29:392a -p /var/run/dpinger_WAN_DHCP6~2a01:cb19                                                                                                              :dead:beef:92ec:77ff:fe29:392a~2001:41d0:2:927b::3.pid -u /var/run/dpinger_WAN_DHCP6~2a01:cb19:dead:beef:92ec:77ff:fe29:392a~2001:                                                                                                              41d0:2:927b::3.sock -C "/etc/rc.gateway_alarm" -d 1 -s 500 -l 2000 -t 60000 -A 1000 -D 500 -L 75  2001:41d0:2:927b::3 >/dev/null                                                                                                              ' returned exit code '1', the output was ''
2025-06-11T09:25:36.991546+02:00 pfSense.bhf.tld php-fpm 581 - - /rc.newwanipv6: Error starting gateway monitor for WAN_DHCP6
2025-06-11T09:25:37.732088+02:00 pfSense.bhf.tld php-fpm 82005 - - /rc.newwanipv6: rc.newwanipv6: Info: starting on ix3 due to REQUEST.
2025-06-11T09:25:37.734539+02:00 pfSense.bhf.tld php-fpm 82005 - - /rc.newwanipv6: rc.newwanipv6: on (IP address: 2a01:cb19:dead:beef:92ec:77ff:fe29:392a) (interface: wan) (real interface: ix3).
2025-06-11T09:25:37.769153+02:00 pfSense.bhf.tld php-fpm 82005 - - /rc.newwanipv6: Removing static route for monitor 2001:41d0:2:927b::3 and adding a new route through fe80::46d4:54ff:fe2a:3600%ix3
2025-06-11T09:25:37.786286+02:00 pfSense.bhf.tld php-fpm 82005 - - /rc.newwanipv6: Removing static route for monitor 94.23.251.218 and adding a new route through 192.168.10.1
done.
Synchronizing user settings...done.
Configuring CRON...done.
Starting NTP Server...done.
Starting webConfigurator...done.
Starting Kea DHCP service...done.
Starting Kea DHCPv6 service...done.

...

                              The output of "/rc.newwanipv6" and "/rc.newwanip" needs to go to the system log, not on the the console output during this booting phase.
                              All these lines are informative, there are no warnings or errors.

                              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
                              • I
                                ITSGS_
                                last edited by

                                Just upgraded from last BETA to the current one. No issues so far.

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

                                  Another one :

                                  Current Base System : 25.03.b.20250610.1659
                                  The "Juin 10" version is now installed.
                                  Using a 4100 MAX : all is well.

                                  Mandatory packages :

Netgate_Firmware_Upgrade 	23.05.01 
Nexus 	25.03.b.20250610.1659 	
aws-wizard 	0.12 	
ipsec-profile-wizard 	1.2.4 
openvpn-client-export 	1.9.5 
openvpn-client-import 	1.2_3 
System_Patches	2.2.21_2 (why is this package 'optional' ?)

My packages : the classic GUI / quality of live stuff :
acme 	0.9_1 
Avahi 	2.2_7 
Backup 	0.6.3 
Cron 	0.3.8_6 
Filer 	0.60.6_9 
Notes 	0.2.9_5 
nut 	2.8.2_5 
Shellcmd 	1.0.5_4 

Not really needed : very light DNSBL setup / Python mode :
pfBlockerNG-devel 	3.2.7

Because I like to things the hard way (auth captive portal):
freeradius3 	0.15.14

                                  This is a production device (company).

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

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

                                    Update from 25.03.b.20250606.1549 to 25.03.b.20250610.1659 on my SG4200 worked.

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