Version 4.12.0 Scheduled Release is out for pfSense® and ASUS® and VyOS® as of 14 May 2024.
It includes a few improvements and fixes as outlined in previous 4.11.1 rapid releases. The most significant improvements are:
Muscle changes on all platforms:
- Support for traffic log to see which Enabler matched allowed traffic (MyTools update is coming shortly; it will make use of this and display it).
- Added support for ID HTTPS (Type 65) requests.
- Added support for MyTools to identify endpoint incorrect DNS server usage (MyTools update is coming shortly, it will make use of this and display that on whoami).
- The muscle no longer reacts to changes in IP addresses used in listeners. This will reduce the number of incidents where
anmuscle.sh
restarts. - Added a configuration switch option of
dns-blocked-record-types
which can be used to disable certain record types. - Fixed a time zone offset calculation but prefer to use
tm_gmtoff
wherever it is supported. - Improved handling of query type
SVCB
to_dns.resolver.arpa
to avoid upstreaming/recursion even if DNS Encryption is not in use. - Started sending profile id for modified entities to help controller support subnet-based default profiles.
pfSense® changes:
- Support for FreeBSD 15 (for pfSense+ 24.03).
- The muscle no longer reacts to changes in IP addresses used in listeners. This will reduce the number of incidents where
anmuscle.sh
restarts. adamone-setup
command prevents running as non-admin user.- Warning when running
adamone-setup
if adam:ONE is not checking in to the controller.
ASUS® changes:
- script updates to change installation default to fail open rather than fail close
VyOS® changes:
- Now supports cloud backups of the router config.
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.12.0
The solution is to:
- upgrade pfSense®
- re-install adam:ONE®
Update on older versions of pfSense®
Automatic upgrades have been completely disabled for any pfSense® versions prior to 23.01.
Thank you
– Adam Networks team