pfSense 2.5 Release Date News
-
Unless there is a particular feature you're waiting on that's only in 2.5, I don't see what the hurry is. It will look and run the same as 2.4.4. If you're running in production, you're wise to wait at least a month after release before you upgrade.
-
It won't be for a while yet. We need to move to a FreeBSD 12.1 base and even after that, there are a number of issues to address. When we know more, we'll post about it.
-
Will it require AES-NI CPU Crypto?
-
@JKnott "AES-NI Not Required
The original plan was to include a RESTCONF API in pfSense 2.5.0, which for security reasons would have required hardware AES-NI or equivalent support. Plans have since changed, and pfSense 2.5.0 does not contain the planned RESTCONF API, thus pfSense 2.5.0 will not require AES-NI."https://www.netgate.com/blog/pfsense-2-5-0-development-snapshots-now-available.html
-
Tnx. I won't have to buy new hardware then.
-
Thank you all for responding. I am one of those who had bought new equipment to meet pfSense 2.5 requirement only to learn that that won't happen; so, I just want the update to be over with. Wondered how to add that Restconf API...it would be pleasant if we could add it as a package so the folks who prepared for it could have a sense of relief.
-
@NollipfSense said in pfSense 2.5 Release Date News:
could have a sense of relief.
PfSense of relief!
-
-
Is the rest API still a target, or is it deadlocked in TNSR???
-
Not for 2.5 it isn't. That was what as driving the AES-NI requirement. See:
https://www.netgate.com/blog/pfsense-2-5-0-development-snapshots-now-available.html#aes-ni-not-requiredSteve
-
@stephenw10 I understand that.
I think some better idea of the future of pfSense would be appropriate. As a couple people already mentioned they spent the money to upgrade the equipment, and some of us were happy to do it if it meant an API.
Not a huge deal. pfSense is always caught between comments like this, and trying to stay opensource. I do not want to come off as unappreciative, but if I went through all this non-sense for pfSense to pull back, I want to make a mental note why for the future.
-
@webdawg said in pfSense 2.5 Release Date News:
I do not want to come off as unappreciative
Same here...that's why I believe if an entity made a strategy decision, it should follow through. That's what I admired in Apple despite my expensive hardware became obsolete...but guess what, I turned around and bought many more.
I had been causally reading up on Restconf API here: https://tools.ietf.org/html/rfc8040 If I were pfSense, I would have at least make it available as a package...that way, the open source would continue to support innovation while remaining adaptable to all members. I think that's the essence of open source.
-
@NollipfSense 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.
Re: release as a package - I think you are underestimating the work involved and what the API will be used for. There has been a roadmap posts on the Netgate blog.
https://www.netgate.com/blog/further-a-roadmap-for-pfsense.html
https://www.netgate.com/blog/more-on-aes-ni.htmlGranted the posts are from 2015 & 2017 and maybe it is time for an updated roadmap blog post from Netgate. My guess is the API will be part of the 3.0 release, where the webGUI is rewritten. Why update the current PHP webGUI to use RESTCONF now only to replace all of PHP for 3.0 with Python? I'd rather have the developers working on 3.0.
-
@ahking19 Yeh, that is why I was asking. If the previous road-maps are not accurate...I was just looking for an update. I did not want to turn this thread bad.
-
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.
