A pfSense roadmap
-
Ooops, that's on me. I stopped reading when it seemed to be addressing only the 2.4 branch. Thank you for including plans to update the 2.3 branch.
The question remains going forward: can we come up with a recipe for a 32-bit build of the 2.4 branch when the dust settles? Sure it won't be supported but sometimes you just gotta deal with it.
-
No, it is not viable. None of the patches have been tested on i386 and it's entirely possible there are required pieces missing (like an i386 kernel config), and who knows what else.
It isn't going to happen, and the time wasted on chasing it down on the off chance it might work would be better spent on non-obsolete hardware.
-
And how about my security concerns over Dnsmasq?
https://www.netgate.com/blog/no-plan-survives-contact-with-the-internet.html
"Users on pfSense 2.3.x or earlier concerned about these bugs can switch to the DNS Resolver (Unbound) until a new pfSense software release is available."
FYI- As of right now, if you are on 2.3.4-p1 you can fetch an updated dnsmasq
pkg update -y dnsmasq
That should find the update and install it, afterward you have to restart the dnsmasq service
-
Yes, that did the trick:
pkg upgrade dnsmasq
brought me upto
dnsmasq upgraded: 2.76,1 -> 2.78,1
Thank you.
-
And how about my security concerns over Dnsmasq?
https://www.netgate.com/blog/no-plan-survives-contact-with-the-internet.html
"Users on pfSense 2.3.x or earlier concerned about these bugs can switch to the DNS Resolver (Unbound) until a new pfSense software release is available."
FYI- As of right now, if you are on 2.3.4-p1 you can fetch an updated dnsmasqThe simplest way is to use:
13) Update from consolevia Console or ssh admin
-
Regarding the roadmap.
Do we have any approximate timeframe when PFSense 2.5 will be out ? Maybe when a beta will be available for testing ?
Since AES-NI will be required, I want to know how much time to I have until I would need new hardware :)Thanks a lot,
Andy.
