pfSense 2.5 Release Date News
-
Why was new hardware bought for a release that as yet has not official date?
Even if you waited until it was released, before buying new hardware, it's not like it takes months to arrive anyway.
-
@ahking19 said in pfSense 2.5 Release Date News:
What do you know that we don't? Where has it been said that the plan to use RESTCONF API has been dropped? I think you are jumping to conclusions. It's only been stated that RESTCONF API is not part of the 2.5 release.
Absolutely nothing, in fact, I am learning from you. I didn't mean to imply RESTCONF dropping, only dropped from 2.5v. I am just wanting to learn about it since I encounter pfSense late 2016 and that the gospel was all newbies should get hardware to meet pfSense 2.5v.
@webdawg said in pfSense 2.5 Release Date News:
I did not want to turn this thread bad.
Not at all and was never intended to be that way either...my hope is others checkout RESTCONF.
@Rod-It said in pfSense 2.5 Release Date News:
Why was new hardware bought for a release that as yet has not official date?
I had not visited the forum for quite awhile but remembered most of the talk with newbies during 2017 -2018 on the forum was to get hardware to meet pfSense 2.5v. So, after buying the hardware and returning to the forum, that's when I found out. The good thing is I got what I was seeking in hardware, and it should able to grow with pfSense over the next five years.
-
Dang, if they're waiting on FreeBSD 12.1 we probably will not see 2.5 this year.
-
@Zermus said in pfSense 2.5 Release Date News:
Dang, if they're waiting on FreeBSD 12.1 we probably will not see 2.5 this year.
It surely is appearing that way!
-
@KOM
It is not a hurry for 2.5 but also the development for 2.4.4 seems to be "frozen" as there are no package updates for it since a while.e.g.
Squid is stable in version 4.8 and in pfSense in version 3.5.28 of July 2018ntoPNG is stable in version 3.8 from December 2018 and in pfsense in version 3.6
There is just the "feeling" for users that pfSense is not of "high interest" of Netgate anymore because in former times there were more often regular updates, etc.
-
@ramup said in pfSense 2.5 Release Date News:
@KOM
It is not a hurry for 2.5 but also the development for 2.4.4 seems to be "frozen" as there are no package updates for it since a while.e.g.
Squid is stable in version 4.8 and in pfSense in version 3.5.28 of July 2018ntoPNG is stable in version 3.8 from December 2018 and in pfsense in version 3.6
There is just the "feeling" for users that pfSense is not of "high interest" of Netgate anymore because in former times there were more often regular updates, etc.
Almost all of the packages available for pfSense were created by and are maintained by volunteer contributors. The pfSense team looks after very few of the available packages. For various reasons these volunteer maintainers come and go, so the support of their particular package may suffer when one of them "abandons" it.
For example, I maintain the Snort and Suricata packages 100% as a volunteer contributor. There is no involvement of the pfSense developer team with either package other than the fact one of them "merges" updates I submit for those packages into the pfSense repository. So if a bus runs over me today, the Snort and Suricata packages would no longer be actively maintained.
Of course other package maintainers are welcome to enter the field. In fact, I took over the Snort package several years ago after its initial creator abandoned the pfSense eco-system. I believe user @BBcan177 took over the older pfBlocker package a few years ago and morphed it into the much more capable pfBlockerNG and pfBlockerNG-devel packages. So if you are concerned about support for packages, then please consider stepping up and becoming a volunteer maintainer.
-
@bmeeks
Thank you for this statement. I just wrote what my perception of an end user is and can only estimate that other users might think in a equivalent way in respect of regularly updates in the past.Unfortunately I am not a developer / programmer etc. with the necessary skills / ability to take care of a certain package.
I appreciate that other people with the needed skills take care of certain packages like you do.
Unfortunately there seems to be no capacity for Netgate to maintain the core (additional) packages. -
And of coarse you can always help out by testing. :)
https://redmine.pfsense.org/projects/pfsense/issues?query_id=105
-
@ramup Don't judge progress by package updates alone.
pfSense Activity
https://redmine.pfsense.org/projects/pfsense/activitypfSense 2.5.0 Open Issues
https://redmine.pfsense.org/projects/pfsense/issues?query_id=104 -
@ramup said in pfSense 2.5 Release Date News:
@bmeeks
Thank you for this statement. I just wrote what my perception of an end user is and can only estimate that other users might think in a equivalent way in respect of regularly updates in the past.Unfortunately I am not a developer / programmer etc. with the necessary skills / ability to take care of a certain package.
I appreciate that other people with the needed skills take care of certain packages like you do.
Unfortunately there seems to be no capacity for Netgate to maintain the core (additional) packages.I didn't mean my post as an idictment or anything personal against anyone. I was just trying to convey that the packages on pfSense are, for the most part, done by others outside of the Netgate/pfSense core team. Those guys are busy enough working on the core firewall itself and the handful of supporting utilities and kernel patches required.
If a pfSense user does have some PHP coding skills (primarily) and has familiarity with a particular FreeBSD port package, then please consider picking up support, or aiding in the support, of a package.
-
-
@ahking19 Have you seen anyone from Netgate say that they're still going to release pfsense 3.0 with VPP/DPDK and RESTCONF? Literally all evidence to date is that what was going to be PFSense 3.0 is TNSR instead, heck the preview of PFSense 3.0 looks identical to TNSR.
It's disappointing that Netgate won't just give a clear answer, but that's their prerogative. I'd never begrudge them expecting to get paid for their efforts if that's the route they chose to go, just frustrating they won't come right out and say that instead of leaving the community to guess.
https://fast.dpdk.org/events/slides/DPDK-2017-09-Ireland-pfSense.pdf
https://www.reddit.com/r/PFSENSE/comments/6wosx8/a_very_short_preview_of_30_cli_and_restconf/
https://docs.netgate.com/tnsr/en/latest/basics/working-cli.html -
@tcsac Thanks for providing this information. I did not look into TNSR, but it does look like you seem right.
It is a true shame if what you say is true, that functionality that is built into other enterprise devices, that pfSense is copying, is now bundled into a TNSR subscription. Sure the vector packet processing is great...but command and control bundled with it?
I hope I am wrong, but if I am not I will be at a loss for words soon. I do not think it is there prerogative, and I think that people deserve an answer eventuall. If they really are thinking about taking this direction with their products, and software then they should just commit to it.
It could be that is why they do not answer. Considering that the product that they release still has maintainers that do not get paid for the packages that they support. I was really looking forward to an API, and command line interfaces.
I was really looking forward to watching a company sweep the run out from under Cisco etc...I suppose soon we will have to look elsewhere, or just continue to wait?
I really still do wholeheartedly support pfSense, and Open Source software, and I do understand that companies need a strategy to profit from it, AND they may even need to hide that strategy, but the direction that we seem to be going here would need a change or we are all going to walk away disappointed.
-
@tcsac said in pfSense 2.5 Release Date News:
It's disappointing that Netgate won't just give a clear answer, but that's their prerogative.
Yes, surely it must be nefarious.... Seriously, you guys are being ridiculous. You expect them to update you on their future plans every day? Or just whenever you demand? Plans change. That's life. Netgate isn't Microsoft with tens of thousands of employees. There is only so much they can do, and sometimes plans turn out to be too ambitious or impractical based on new developments. It looks like their plans for pfSense 3.0 may have changed. Deal with it. I understand now why companies are loathe to talk about the future and roadmaps when people complain if those plans change for any reason.
I suppose the lesson learned by Netgate is to not tell you anything in advance.
-
@KOM said in pfSense 2.5 Release Date News:
Seriously, you guys are being ridiculous
What you said would have been holistic and understanding without the above statement. We all are here because we like open source software, especially pfSense. @tcsac Not only expressed himself, but also provided links to documents thus making us more informed.
-
@NollipfSense They're being ridiculous because they're jumping to conclusions and assuming bad intentions.
-
@tcsac said in pfSense 2.5 Release Date News:
https://docs.netgate.com/tnsr/en/latest/basics/working-cli.html
anyone from Netgate say that they're still going to release pfsense 3.0 with VPP/DPDK and RESTCONF?<<
"Still"? - not that I've read. I've never read that VPP was going to be part of pfSense 3.0.
VPP is at the core of tnsr and it runs on linux, CentOS I believe.Porting pfSense from FreeBSD to Linux is not something I've heard or would expect in 3.0.
-
@KOM said in pfSense 2.5 Release Date News:
@NollipfSense They're being ridiculous because they're jumping to conclusions and assuming bad intentions.
@KOM Jumping to what conclusions? PFSense 3.0 was codenamed pennybacker, which is what became TNSR. I haven't asked for an update every day, in fact I've literally NEVER asked for an update. I simply spoke up because after watching people get flamed repeatedly here for just being curious about what's happening, I thought someone should give a reasoned response. I won't even begin to try to understand why people like you have such a visceral reaction in the middle of people having a rational discussion. You might want to take a deep breath before posting your next response because you seem to be overly emotional for no reason.
https://www.reddit.com/r/PFSENSE/comments/75pt7g/pissed_with_my_edgerouter_thinking_of_switching/
level 3
gonzopancho
Netgate4 points ·
2 years agoIt's been code named "Pennybacker" for 3 years now.
Slides from two weeks ago: https://dpdksummit.com/Archive/pdf/2017Userspace/DPDK-Userspace2017-Day2-9-pfSense.pdf
One of the slides in there explains why it's not "pfSense". It's a new thing, and deserves a new name. In this way, pfSense can continue being what it is.
The name will be announced at launch.
-
@ahking19 said in pfSense 2.5 Release Date News:
@tcsac said in pfSense 2.5 Release Date News:
https://docs.netgate.com/tnsr/en/latest/basics/working-cli.html
anyone from Netgate say that they're still going to release pfsense 3.0 with VPP/DPDK and RESTCONF?<<
"Still"? - not that I've read. I've never read that VPP was going to be part of pfSense 3.0.
VPP is at the core of tnsr and it runs on linux, CentOS I believe.Porting pfSense from FreeBSD to Linux is not something I've heard or would expect in 3.0.
Yes, they literally said pennybacker which was presented at
fd.iodpdk was PFsense 3.0. Justifications for starting over from scratch/moving away from FreeBSD are in the slide deck.https://www.reddit.com/r/PFSENSE/comments/75pt7g/pissed_with_my_edgerouter_thinking_of_switching/
-
I won't even begin to try to understand why people like you have such a visceral reaction in the middle of people having a rational discussion.
And I never understand the people who come to this forum and do nothing but bitch and moan about something they haven't contributed even the tiniest thing towards. Look at you, you've been here for 5 years with a whopping 31 posts. No doubt you only post when you need help or want something.
And no, people don't get flamed for asking a question. They get negative responses because they invariably whine or jump to the conclusion that Netgate is being shady for some reason.
You might want to take a deep breath before posting your next response...
Blah blah blah
Look, if WebGUI is not your flavour and you really want a CLI, spin up a FreeBSD instance and go nuts. All the CLI and text file configs you can handle.
-
@tcsac said in pfSense 2.5 Release Date News:
Yes, they literally said pennbacker which was presented at fd.io dpdk was PFsense 3.0. Justifications for starting over from scratch/moving away from FreeBSD are in the slide deck.
https://www.reddit.com/r/PFSENSE/comments/75pt7g/pissed_with_my_edgerouter_thinking_of_switching/Yeh. I almost did not post what I wrote, but once I started reading about pennbacker I needed to chime in.
I don't know. I do not think any of us are trying to dump on the pfSense team here. I do not think any of us deserve to. I know I am trying to scratch that itch of excitement when I heard the phrase API.
I think we are all just trying to make decisions to support our future strategies, and information about pfSense direction may be needed to move those strategies along.
I apologize if I have offended anyone.
-
@KOM I think you are exaggerating what is going on here, and it should stop. You are turning this conversation into an argument, when we are all just trying to be good-natured. Please contain your passion, and maintain your respect in these forums.
-
@KOM said in pfSense 2.5 Release Date News:
I won't even begin to try to understand why people like you have such a visceral reaction in the middle of people having a rational discussion.
And I never understand the people who come to this forum and do nothing but bitch and moan about something they haven't contributed even the tiniest thing towards. Look at you, you've been here for 5 years with a whopping 31 posts. No doubt you only post when you need help or want something.
I actually have contributed, and most of my posts are me working through issues and following up with solutions and resolutions. If you had spent 30 seconds looking instead of making really poor assumptions you'd have figured that out.
And no, people don't get flamed for asking a question. They get negative responses because they invariably whine or jump to the conclusion that Netgate is being shady for some reason.
Asking about an update on something that was announced 3 years ago isn't whining.
You might want to take a deep breath before posting your next response...
Blah blah blah
Look, if WebGUI is not your flavour and you really want a CLI, spin up a FreeBSD instance and go nuts. All the CLI and text file configs you can handle.
I really don't understand what your issue is, but you should seriously take a step back and try to figure out why you're so toxic and hostile. You're jumping into a conversation and trying to start an argument for literally no reason. Everything you've thrown against the wall WRT: people whining or bitching or not contributing is literally fabricated bullshit. It has no place here or anywhere else, I'm not sure if you've got serious issues in real life or not, but chill the fuck out.
-
@tcsac I am hoping that it took a while to draft that response. I think we are all just passionate about this, and each want to express what we think. I can understand how you can feel attacked by @KOM , but I think you are both crossing some lines that should not be in this post.
While I understand that you need to defend yourself, please take the rest of this conversation somewhere else.
Thank you both for your contributions to this topic, and please continue to post relevant information.
-
@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.