Version 4.14.1 Scheduled Release is out for pfSense® and ASUS® and VyOS® as of 21 December 2024.
It includes a few improvements and fixes as outlined in previous 4.14.0 rapid releases. The most significant improvements are:
Muscle changes on all platforms:
- DNS queries of wpad.* are answered with NXDOMAIN response unless matched to a forwarding rule
- Improved handling of illegal domain names
- Fixed broadcast packet handling (that impacted some HA environments)
- Allowed underscores in the middle of DNS labels by default
- Allowed all management domain names in origin for HTTP
- Fixed ACME requests to better handle propagation times
- Fixed encrypted MyTools not redirecting to set hostname
- Fixed a bug in profile-switching from NoInternet to another policy
- other code improvements
pfSense® changes:
adamone-setup configure
script now requires BoxID registration before script continues
ASUS® changes:
- Fix for some older Asuswrt-Merlin kernels versions that caused some traffic to fail
VyOS® changes:
- Supports immediate default treatment even before a device is enrolled (VyOS-only feature)
- Optimized how TCP reset and ICMP host unreachable packets are sent, and added an option to build a layer 2 packet, which is necessary for VyOS in bridge more
Special thanks to all the testers that made this possible.
For installation of adam:ONE® see:
- pfSense®: adamnet.io/pfsense
- ASUS®: adamnet.io/asus
- VyOS®: adamnet.io/vyos
Note on automatic upgrades
During adamone-setup configure
installation wizard, we recommend the default to automatically upgrade adam:ONE® software. When that default is selected, the attempt will be made based on contents in /etc/crontab
(pfSense®) or cru l
(on ASUS®).
However, in some circumstances, the internet will fail after automatic upgrade, specifically if these conditions are all met:
- your pfSense is older than what is listed at adamnet.io/pfsense
Disable the Dashboard auto-update check
is checked (System → Update → Update Settings)- the cronjob has executed and upgraded to
4.14.1
The solution is to:
- upgrade pfSense®
- re-install adam:ONE®
Thank you
– Adam Networks team