Welcome to the 2.4 board
-
-
-
I wonder if the problems on icap protocol error and suricata stopping will be resolved in this version.
-
It might help to know that there are two (three) development branches currently:
2.4.0 (amd64) HIGHLY-EXPERIMENTAL pfSense 2.4.0 ALPHA developers tree
2.3.3 (amd64 & i386) EXPERIMENTAL pfSense 2.3.3 developers treeSo 2.3.3 is still active.
We may, or may not, ever cut a 2.3.3
-
I installed this version to take a look. There is some strange behaviour relative to 2.3.3 development snapshot (with identical settings), including a crash report. Would you like me to post details somewhere?
-
@jwt:
We may, or may not, ever cut a 2.3.3
Sure and it's your call anyways.
I am with this project since 0.9something and AFAIK this is the first time that there are two public development branches simultaneously.
-
Will there be an i386 build when 2.4 is released?
-
Will there be an i386 build when 2.4 is released?
No, 32-bit has been taken out of the build scripts for 2.4.
2.3.* is the last release stream for 32-bit. There is yet to be an official announcement about the EOL support for that - I am hoping that ordinary code/fixes will continue to be back-ported and that a formal release build will be done "every now and then" of the RELENG_2_3 branch up to the EOL for FreeBSD 10.3 in 2018. -
No, 32-bit has been taken out of the build scripts for 2.4.
2.3.* is the last release stream for 32-bit. There is yet to be an official announcement about the EOL support for that - I am hoping that ordinary code/fixes will continue to be back-ported and that a formal release build will be done "every now and then" of the RELENG_2_3 branch up to the EOL for FreeBSD 10.3 in 2018.Thank you for the quick response. That is a bit of a bummer as I have a couple of i386 machines in production. Oh well. :(
-
I am hoping that ordinary code/fixes will continue to be back-ported and that a formal release build will be done "every now and then" of the RELENG_2_3 branch up to the EOL for FreeBSD 10.3 in 2018.
I'm with you.
Would be nice if they could commit to say 2 maintenance releases in 2017.
-
… if they could commit to say 2 maintenance releases in 2017.
Releases contain new features and/or fixes.
New features won't go into 2.3.x anymore and security/bug fixes are released when necessary. Do you already know if/when/how many fixes are needed in 2017? :o -
… if they could commit to say 2 maintenance releases in 2017.
Releases contain new features and/or fixes.
New features won't go into 2.3.x anymore and security/bug fixes are released when necessary. Do you already know if/when/how many fixes are needed in 2017? :oNew features are still being back-ported into the RELENG_2_3 branch. So far all the user code (as distinct from build scripts…) that has happened in master for 2.4 has been stuff that works just fine in 2.3 on FreeBSD 10.3, so the backports have been easy Git cherry-picking. Thus there are new features sitting in RELENG_2_3 that would just "pop out" by themselves into a 2.3.3 release build, if that is ever done.
-
Do you already know if/when/how many fixes are needed in 2017? :o
As a matter of fact yes I do.
If? Yes
When? Q2 & Q4, and any others deemed prudent.
How Many? At least 2, plus any others deemed prudent. -
Would someone please make this topic sticky?
-
Where to find ARM-Sources and Snapshots?
-
Question - processor specific issue.
Will pfsense 2.4 64bit run on a D2700 board? Its supposed to be 64 bit capable but I've read about some issues.
Currently there is a 32 bit version of pfsense running on a pfsense install that is far far away.
I'd test it myself but I can't physically touch that system. So, anyone know?
-
Will there be an i386 build when 2.4 is released?
No, 32-bit has been taken out of the build scripts for 2.4.
2.3.* is the last release stream for 32-bit. There is yet to be an official announcement about the EOL support for that - I am hoping that ordinary code/fixes will continue to be back-ported and that a formal release build will be done "every now and then" of the RELENG_2_3 branch up to the EOL for FreeBSD 10.3 in 2018.That's interesting, because the SG-1000 is based on the ARM Cortex-A8 which is is a 32-bit processor and only runs 2.4.
-
Will there be an i386 build when 2.4 is released?
No, 32-bit has been taken out of the build scripts for 2.4.
2.3.* is the last release stream for 32-bit. There is yet to be an official announcement about the EOL support for that - I am hoping that ordinary code/fixes will continue to be back-ported and that a formal release build will be done "every now and then" of the RELENG_2_3 branch up to the EOL for FreeBSD 10.3 in 2018.That's interesting, because the SG-1000 is based on the ARM Cortex-A8 which is is a 32-bit processor and only runs 2.4.
The intended detailed meaning is that 32-bit i386 has been removed (and all nanoBSD has been removed).
Technically speaking, yes there is still 32-bit in 2.4 because a 32-bit ARM build has been added. -
The intended detailed meaning is that 32-bit i386 has been removed (and all nanoBSD has been removed).
Technically speaking, yes there is still 32-bit in 2.4 because a 32-bit ARM build has been added.I actually figured that this particular device would only run on the 2.3 release and not be upgradable to 2.4 once it came out..
Thus a good reason for Netgate to continue 2.3 support well into the future. Phil- you absolutely sure that its sold with 2.4?
-
The intended detailed meaning is that 32-bit i386 has been removed (and all nanoBSD has been removed).
Technically speaking, yes there is still 32-bit in 2.4 because a 32-bit ARM build has been added.I actually figured that this particular device would only run on the 2.3 release and not be upgradable to 2.4 once it came out..
Thus a good reason for Netgate to continue 2.3 support well into the future. Phil- you absolutely sure that its sold with 2.4?
Yep, the ARM build is only in 2.4
I see that people are reporting 2.4-BETA issues on SG-1000 devices here, so I guess the hardware was ready back in Nov/Dec 2016 and they decided to ship it with 2.4-BETA
