pfSense+ 25.11.1 support status?

adam:ONE® pfSense
1

Hi Adam:ONE team,

Can you confirm whether pfSense+ 25.11.1 is currently supported?

Environment:

  • pfSense+ 25.11.1-RELEASE (amd64)

  • FreeBSD 16.0-CURRENT

  • Netgate 4200 appliance (UEFI, Intel Atom C1110)

Issue:

  • Adam:ONE worked on prior pfSense+ releases.

  • After upgrading to 25.11.1, outbound traffic from LAN clients breaks when Adam:ONE is installed/enabled.

  • Removing all Adam:ONE rules immediately restores connectivity.

  • Reinstall attempts fail due to missing package metadata for 25.11.1 (repo paths return 404).

Downgrading pfSense resolves the issue, which suggests Adam:ONE packages/repos are not yet built for 25.11.x.

Questions:

  1. Is pfSense+ 25.11.1 supported today?
  2. If not, is support planned and on what timeline?

Thanks.

2

Welcome to the forum @therubymug
At the moment DTTS is broken on pfSense+ 25.11+ with x86 hardware, and we have not made a package for 25.11.1 available at all yet.
For the most part we’re telling everyone to downgrade to 25.07 which was working fine.

There is not yet a clear path to 25.11+ being fully supported.

3

Thanks for the welcome and update Arthur

One clarification I’m looking for: why can’t adam:ONE be installed as a proper pfSense package anymore? I may be missing something obvious.

More broadly, Netgate/pfSense support has told me in the past that they will not support systems with adam:ONE installed, since it’s an unsupported package. That creates a real support gap for users running pfSense+.

Is the lack of a package a technical limitation in 25.11+, a Netgate policy issue, or a design decision on the adam:ONE side?

Trying to understand whether this is temporary or an expected long-term constraint.

4

I’ll divide that into two issues.

  1. Supported packages: pfSense® does not officially allow or support third-party packages such as adam:ONE. We use a workaround because they do still allow standard freebsd packages to be installed. There is no likely path to this ever changing.

  2. For 25.11+ there is a freebsd bug that made it into pfSense. There is no fix, we are working multiple options. This is hopefully a temporary constraint. But if having something with official support is desired I’d recommend moving to VyOS where we can operate without using workarounds.