adam:ONE v4.14.2-1 Scheduled Release

Announcements
, ,
1

Version 4.14.2 Scheduled Release is out for pfSense® and ASUS® and VyOS® as of 29 May 2025.

It includes a few improvements and fixes and in particular pfSense 2.8.0 Community Edition support!

Muscle changes on all platforms:

  • Resolved issue where an endpoint manual device IP change in dashboard required muscle restart; service restart no longer required
  • Resolved issue where an Enabler addition and policy enablement requires muscle restart; service restart no longer required
  • NetBIOS name now takes preferences over mDNS name on discovery/device naming process
  • Feature added for the muscle to support API monitoring for Reflex status
  • Feature added for the muscle to support API monitoring for pfSense pfctl state table exhaustion status
  • Added collect for queries that fail, get ignored, or get rate limited
  • Added feature of packet-never-monitor-subnets, required for some layer 3 network connections that should or should not auto-enrol
  • Added missing retry option support to the DoT server (resolves issues where internal DoT service would sometimes fail to start)

pfSense® changes:

  • pfSense 2.8.0 support

ASUS® changes:

  • Fix for the newest Asuswrt-Merlin where ipset was changed

VyOS® changes:

  • no specific changes to VyOS

Special thanks to all the testers that made this possible.

For installation of adam:ONE® see:

  1. pfSense®: adamnet.io/pfsense
  2. ASUS®: adamnet.io/asus
  3. 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.2-1

The solution is to:

  • upgrade pfSense®
  • re-install adam:ONE®

Thank you
– Adam Networks team

1 Like
2

This topic was automatically closed after 7 days. New replies are no longer allowed.