New pfSense Plus 25.03-BETA is here!
-
A new public BETA for pfSense Plus 25.03 is now available!
A big thank you to all users willing to test this BETA release. Your community involvement is essential to making Netgate's pfSense Plus product a stronger solution for everyone!
This release includes over 60 updates, bug fixes, and enhancements. Release Notes with more details on these improvements are linked below!
Note: As of this BETA version, the Multi-Instance Management Early Look features, which included the 3 additional free managed instances, will be discontinued. The ability to control the local instance will still remain.
Release Notes: https://docs.netgate.com/pfsense/en/latest/releases/25-03.html
-
M mwatch pinned this topic on
-
I am puzzled as to why you don't allow a 24.03 => 25.03 upgrade path for this beta?!
-
Betas are/were based upon the latest "stable" as (imho) it isn't a full update/upgrade, but only the "current working set + the stuff that actually changed"
Probably less puzzling for you : going to 24.11, let the dust settle, and then go straight to the latest Beta.
Or is 24.11 a show stopper for you ? -
@Gertjan said in New pfSense Plus 25.03-BETA is here!:
Betas are/were based upon the latest "stable" as (imho) it isn't a full update/upgrade, but only the "current working set + the stuff that actually changed"
This can't be a beta. Beta is the full update, that the developers are confident enough to release for testing (either internal or public)
When things stabilize we get Release candidates., and one of them becomes release.
What you are referring is alpha code.
-
@netblues said in New pfSense Plus 25.03-BETA is here!:
New pfSense Plus 25.03-BETA is here!:
@netblues said in New pfSense Plus 25.03-BETA is here!:
This can't be a beta.
How can a beta not be a beta ?
-
@Gertjan I'm referring to your definition of beta.
25.03 is definitely a beta :) -
You are discussing symentics
It does not matter what you call it beta or alpha
It's definitely beta IMHO as long as it's released to the public for testing.
My point is that we don't test the 24.03 => 25.03 upgrade path.
And this is important to me as 24.11 presented issues to my environment.
-
@chudak said in New pfSense Plus 25.03-BETA is here!:
I am puzzled as to why you don't allow a 24.03 => 25.03 upgrade path for this beta?!
This has always been the case with pfsense upgrades.
They had to happen in sequence.Now if you want to go straight to 25.03, take a configuration backup file, install 25.03 beta and restore.
Works most of the times.
(but it is still a beta, so not recommended for production, (as always))
-
Beta 3 is there ....
-
@Gertjan installed and works fine, as is 2.8 beta released at the same time.
Didn't see any release notes though.
Any ideas what is "fixed" ? -
@netblues said in New pfSense Plus 25.03-BETA is here!:
Any ideas what is "fixed" ?
No, but your pfSense knows ^^ Mine send me this notification :
13:15:04 An update to pfSense version 25.03.b.20250427.2348 is available The following updates are available and can be installed using System > Package Manager: Nexus: 25.03.b.20250414.1838 ==> 25.03.b.20250427.2348 pfBlockerNG-devel: 3.2.6 ==> 3.2.7 Some packages are part of the base system and will not show up in Package Manager. If any such updates are listed below, run `pkg upgrade` from the shell to install them: if_pppoe-kmod: 25.03.b.20250414.1838.1500029 -> 25.03.b.20250427.2348.1500029 [pfSense] pfSense: 25.03.b.20250414.1838.1500029 -> 25.03.b.20250427.2348.1500029 [pfSense] pfSense-base: 25.03.b.20250414.1838 -> 25.03.b.20250427.2348 [pfSense-core] pfSense-boot: 25.03.b.20250414.1838 -> 25.03.b.20250427.2348 [pfSense-core] pfSense-default-config-serial: 25.03.b.20250414.1838 -> 25.03.b.20250427.2348 [pfSense] pfSense-kernel-pfSense: 25.03.b.20250414.1838 -> 25.03.b.20250427.2348 [pfSense-core] pfSense-pkg-Nexus: 25.03.b.20250414.1838 -> 25.03.b.20250427.2348 [pfSense] pfSense-pkg-pfBlockerNG-devel: 3.2.6 -> 3.2.7 [pfSense] pfSense-repo: 25.03.b.20250414.1838 -> 25.03.b.20250427.2348 [pfSense] pfSense-repoc: 20250222 -> 20250419 [pfSense]which is basically 'everything' = kernel, base files, and an updated pppoe kernel mod, and a pfSense package or two.
Imho, and I'm just a user like you, these were the last changes. According to redmine, a lot of small GUI and code changes 'everywhere'.
-
25.03.b.20250429.1329 "25.03 beta 4" up and running.
-
25.03.b.20250507.1611, "beta 5" is avaible.
-
25.03 Beta if_pppoe Feedback only
Since I installed the latest 25.03 Beta, I am seeing the following entries in the system log which are being posted every minute. These are not causing any issues, but you asked for feedback
2025-05-12 09:33:53.318614+01:00 kernel - pppoe: alien host unique tag, no session found
2025-05-12 09:32:53.394458+01:00 kernel - pppoe: alien host unique tag, no session found
2025-05-12 09:31:53.295508+01:00 kernel - pppoe: alien host unique tag, no session found
2025-05-12 09:30:53.280517+01:00 kernel - pppoe: alien host unique tag, no session found
2025-05-12 09:29:53.452473+01:00 kernel - pppoe: alien host unique tag, no session found
2025-05-12 09:28:53.311469+01:00 kernel - pppoe: alien host unique tag, no session found
2025-05-12 09:27:53.340471+01:00 kernel - pppoe: alien host unique tag, no session foundAlso in the system log on boot:
pppoe1: received unexpected PADO
pppoe1: received unexpected PADO
pppoe1: received unexpected PADO
pppoe1: received unexpected PADO
pppoe1: received unexpected PADO
pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for it
pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for it
pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for it
pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for it
pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for it
pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for it
pppoe1: link state changed to UP
pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for it
pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for it
pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for it
pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for it
pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for it
pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for it
2025-05-12T09:41pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for it
pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for it
pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for it
pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for it
pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for it
pppoe1: host unique tag found, but it belongs to a connection in state 3
pppoe: received PADO but could not find request for itSteve
