pfSense® CE 2.8.1 Beta Now Available!
-
A new public beta for pfSense CE 2.8.1 is now available!
Thank you to all users willing to test this beta release. Your involvement is essential to making Netgate's pfSense CE product a stronger solution for everyone!
This beta release includes numerous updates, bug fixes, and enhancements., with more to come.
Call for Testing
Testing this beta software release is essential. Given the diversity of users' environments and configurations, it is the most effective way to ensure that the software is robust and reliable for everyone. By testing this beta release and providing feedback on any issues, our users can play a vital role in improving the software for everyone.Where to report issues
We encourage you to test the things that are important or unique to your deployments. Please report any errors or concerns in the Development category of the Netgate Forum. Depending on the issue, we may ask for more details or for you to open a bug on redmine.pfsense.org.Summary
We want to express our sincere thanks to all users willing to test this beta release. Your community involvement is essential to making Netgate's pfSense CE software a stronger solution for everyone. -
@pfGeorge Release notes?
-
Upgraded from 2.8ce under kvm and uefi,
No issues for now, however we would appreciate release notes so as to know what to look for. :)
-
I have a stable 2.80 version. Should I upgrade to "Version 2.8.1.b.20250717.1752.1500029 is available"?
-
@Waqar-UK If you like testing prerelease software and are willing to report and work through all the bugs you find, sure.
-
I understand. But my family needs a stable connection as father is disabled and uses a IP based telephone.
-
Working well for me.
Relatively basic installation under Proxmox with NIC pass though though. -
Successful and uneventful update from 2.8 to 2.8.1 on bare metal. I initiated the update from GUI with an IPMI console session (which I never touched) side-by-side.
Update preparation was outputted nicely to the GUI logview, which persisted during the 'still rebooting, retrying again in xx seconds...' making it helpful to be able to scroll back through and review what steps were performed and packages were marked for upgrade.
From console view, the system then appeared to reboot into 2.8, perform/finalize the 2.8.1 update, and then reroot into the now-updated system.
If you're doing it 'blind' from GUI (i.e., no console view), expect it to take at least 10 minutes.
I did manually start
unbound
, which was still stopped, once I logged back into the GUI. But I may have jumped the gun on that. (Not running any service watchdog or anything, checked DNS Resolver log quick, and then just decided to click the 'Start' radio from the Dashboard Services widget, and it started normally.) -