pfSense 2.5 Release Date News
-
@tcsac
Sounds like you have a different use case than me. I don't need 10+Gbps in near future , 2-3 years. If you do, I understand the interest in VPP. -
Just my 2 cents but I think @tcsac has a valid point. I mean there is a whole fork of pfsense and their devs who used to support pfsense (Cough Opnsense), and their followers with this premise. That is valid evidence to back up his concerns, and that came from within, not just mere speculation. Otherwise the fork devs wouldn't have deviated from pfSense development.
Maybe @tcsac is just hitting too close to home for some to accept that people have these concerns over Netgate's direction. IMHO if they take this route they should just be clear like Redhat has recently done with Fedora and more recently with CentOS.
Bitching about people bitching is not very productive to the conversation. I will say I'm still here. I still support Netgate and pfSense. It's still the superior open source firewall. I'm also in the crowd that thinks they should be more clear with direction. We are their existing or potential customers. I don't post a whole lot on here. I don't have time, but I do support the project through donations, continued use of pfSense at home, and I control IT budget for a Fortune company. Flaming people like me with valid concerns is not very conductive, whatever Netgate's strategy actually is.
-
My last post on this.
First off, I'd like to apologize to both @tcsac and @webdawg. I went off on the two of you pretty harshly. It wasn't one of my better days and for that I am sorry. I usually try to act as peacemaker when tempers flare around here, but I was lacking in this case.
My frustration came from my view of seeing people assuming the worst or assuming sinister motivations from Netgate. I don't understand it. This is how rumours get started. Just because there is something you don't know, it doesn't mean they're hiding it. Just because Netgate changed something, it doesn't mean they're pulling a fast one.
Anyway, I've blown this whole thread out of proportion. I might suggest that if there is something that one really needs to know and don't have answers for with regard to Netgate and their direction, that you send them an email, or a tweet, or summon @jimp here in the forum. They have always been pretty responsive IME, so at worst you might get an "I don't know/Not sure" reply.
-
@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.
