AP Firmware 2.4d Released

This firmware update expands policy flexibility and strengthens core networking behavior. It enables more granular control over content filtering while improving IPv6 reliability and refining automatic channel selection for more consistent wireless performance.

  • Add support for multiple filter profiles per WiFi password, voucher, profile, and client.
  • Improve IPv6 support on non-Standard network types.
  • Resolve auto-channel selection issues on coordinating AP.

As part of filter profile migration, all old WiFi site-wide filter settings have been converted to global (not just site-wide) filter profiles. All WiFi passwords, vouchers, connection profiles, and client filter settings have been migrated to refer to the newly migrated filter profiles, unless filtering was bypassed. The filter profile name is derived from the site id, i.e. default-12345678.

This update is being rolled out now. You can manually initiate the upgrade if you’d like, or it will automatically update overnight (if auto-updates are enabled). The complete, up-to-date change log is available here:

As always, if you have questions or encounter any issues, feel free to reply here or start a new topic. Please include details about the issue so we can assist you effectively.

With the move to global filter profiles instead of site-scoped settings, what’s the recommended way to handle multi-customer (MSP) setups going forward?

We’re running multiple customer sites in the same org, and want to avoid configs bleeding across customers or future changes breaking isolation.

Is the expectation that we handle separation purely via naming/discipline, or are there plans / best practices for keeping customer configs properly isolated within a shared org?