New pfSense Plus 25.03-BETA is here!
-
@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.
-
@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.
-
@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! -
@SteveITS So does this make it an abandoned project?
-
No source (code ?) for 2.9 ?
Took me one click to find this https://github.com/pfsense/pfsense :
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. -
G Gertjan referenced this topic
-
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.
-
@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.
-
@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.
-
@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. -
@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. :-)