pfSense 2.5 Release Date News
-
@jimp, who we all know is very active on the forum, is taking a much-deserved vacation. In his absence let me just say that 2.5 is still in development and our engineers are actively working to a release. We try to be as transparent as possible and you can follow the development and see what exactly is being done in redmine.
-
@dennis_s said in pfSense 2.5 Release Date News:
@jimp, who we all know is very active on the forum, is taking a much-deserved vacation. In his absence let me just say that 2.5 is still in development and our engineers are actively working to a release. We try to be as transparent as possible and you can follow the development and see what exactly is being done in redmine.
It's heartwarming to see @jimp working on Sunday before he leaves for vacation...that's dedication!
-
@jimp hope you are having a good one!
-
sound more like this
-
Any updates on this thread?
-
@webdawg No updates on 2.5, you can still follow the updates in redmine to see what has been worked on recently. We did, however, release the 2.4.5 snapshots for community testing.
-
@Rod-It - for me and others, who were planning to buy new hardware anyway. The difference was speccing it with 2.5.0 in mind so we didn’t have to replace it again in a year or so, which for me meant an N3150 box instead of a J1900. Nothing world-ending.
I much would rather they announced the restconf (where the RFCs mandate hardware crypto) and delayed it in the roadmap as they have than to just silently shove it into 2.5.0 dev and upset people who had just bought hardware...
-
Netgate: So I'm assuming that 2.4.5 will be an update to get us off the end-of-life'd FreeBSD with some basic bug fixes so the bigger release of 2.5 can be perfected?
-
-
So, pfSense Santa deemed us good for an update...nice! It would be awesome if Snort inline mode and Suricata 5.01 can work with pfSense 2.4.5 while we wait for version 2.5.
-
I'm not sure 2.4.5 will drop before Xmas as there are quite a few open issues still. Snort in line has pretty much always worked with a new release, though.
-
I would be very much surprised if 2.4.5 released prior to end of January or well into February, let alone before the end of the year. They have been hammering out code all week from what I can see, but not 70 before COB on Friday. Then with Christmas being in the middle of the week and schools being off until January so the kids will be home. I don't see as much progress being made from 12/23/2019 - 1/2/2020 as was made this week.
Then you have testing to make sure all those bug fixes didn't introduce any new bugs and the stability of the near-final product before it will be offered as a stable update path.
I wouldn't hold any breath.
-
I'm making this a separate post, but I wanted to address the fight above in the comments.
Netgate is highly conservative with how much candid detail it provides on progress. So much so, that it isn't until there is sufficient noise and misinformation (i.e.: whining, complaining and bitching with elaborate conspiracy theories) that it finally ticks Jim Pingle off enough that he responds and lays the information smackdown usually laying blame firmly in the lap of FreeBSD's developers. He's not wrong.
Case in point the SG-1100 AES-NI support. That took a TON of noise and misinformation before it was revealed what the hold-up was and I think that one was only half FreeBSD's fault.
Couple that with 2.5.0 being this magical release number that was supposed to destroy the non AES-NI hardware and yes REST API! That magical buzzword that will make a sufficiently high-priced central management solution possible (see tangent 1). Truth is, they are trying to pile 10lbs of features into a 5lb release-cycle and they are trying to get onto FreeBSD 12, but 12.1 is also taking a little extra time to bake in the oven. So yeah, that's also about 40% FreeBSD's fault.
And you have to understand, pfsense is an open source project, that is free from very opinionated individuals that certainly doesn't infuriate certain users and even developers who leave the project to start a fork of their own to be free of said opinionated individuals.
If you want a particular feature, start programming it in yourself and hope that your programming style and personality meshes with the non-opinionated individuals on the pfsense development team.Netgate is a for-profit company that supports the pfsense project out of the kindness of it's heart and you need to accept that unless you pay them $100/year otherwise you need to pay them $300/year for TNSR and then your releases will come out much faster. Think of it this way, it's cheaper than a brand new F5 with 24/7 enterprise support. So count yourself lucky young man.
Tangent 1: They released on a poll on reddit an eon or so ago and their cheapest option was like $5/month/firewall. A vast majority of the replies criticized the price and their response was a very straight forward "then you are too cheap for us, go somewhere else". Not in that many words but the message was clear. This was for the central management system.
-
@PhlMike said in pfSense 2.5 Release Date News:
They have been hammering out code all week from what I can see, but not 70 before COB on Friday.
Note that the number of issues open against 2.4.5 are about 90% (60/68) issues waiting for testing and confirmation of fixes already in place. There are only 4 actual issues remaining to work on, and four release-related tasks (updating release notes, docs, etc). I still doubt it will happen before Christmas, but it's certainly not going to be months.
Edit: As always, if you want to see a release happen faster, then help test issues in the feedback state:
-
I have two rules I strictly follow in these situations. First keeps me from being constantly disappointed or agitated. The second keeps me from appearing privileged.
- If a product doesn't do something now it never will.
- If you jumped on the bus through the back door don't complain about the driver.
-
@jimp said in pfSense 2.5 Release Date News:
@PhlMike said in pfSense 2.5 Release Date News:
They have been hammering out code all week from what I can see, but not 70 before COB on Friday.
Note that the number of issues open against 2.4.5 are about 90% (60/68) issues waiting for testing and confirmation of fixes already in place. There are only 4 actual issues remaining to work on, and four release-related tasks (updating release notes, docs, etc). I still doubt it will happen before Christmas, but it's certainly not going to be months.
Edit: As always, if you want to see a release happen faster, then help test issues in the feedback state:
More than 3 months xD for 2.4.5
So what is the expected date for 2.5?
-
There is no ETA for 2.5.0.
-
@l0rdraiden To get an idea, this is how I determined an estimate for myself...I estimate that FreeBSD 12.1 will be stable somewhere around August where pfSense include it September and 2.5RC October...final release December. If it's earlier than that, alleluia...if it’s later, then I readjust my expectation. I won't have to ask anyone when it's releasing...I already have an idea. Meanwhile, I am enjoying it.
-
I would say 16 months. Looks like in the past 13 months they closed 159 issues, with another 164 to go so add an extra month for those, plus adding two-extra months because I was off two months the last time.
So May 2021. TNSR should be at version 100 by then, though...
But, No need to beat a dead horse. They refused to listen thus far and vehemently oppose our viewpoint. They did a partner survey back in February. I was talking to the other larger netgate parters, we all said the same exact thing. What we hear back? crickets....
-
Even though TNSR is basically Cisco and I know it well from decades of use, until it has OpenVPN (Or Ahem Wireguard, lol), Snort, and the pfSense front end I'm sticking with pfSense. The pfSense front end has totally spoiled me from CLI.
Netgate, you make that happen with TNSR and I'll gladly buy it. :)
