Your comment suggests that FreeBSD is a thing of a past and no longer capable of "quality networking", due to poor WiFi support. I can only agree with the poor

Your comment suggests that FreeBSD is a thing of a past and no longer capable of "quality networking", due to poor WiFi support. I can only agree with the poor WiFi support part. But WiFi is by no means something you can judge networking stack dedicated for servers. FreeBSD was never designed for consumer hardware networking. There were a few "desktop distros" but all have more or less died, and the few FreeBSD-based "storage distros" moved to Linux after FreeBSD changed its upstream for ZFS. And I'm saying this as someone who made a lot of effort to use FreeBSD on laptop over the years, and a current user of 15.0-CURRENT on ThinkPad. But FreeBSD was and is THE choice for high-bandwidth wired networking. Netflix is both an early adopter and an active contributor to FreeBSD's networking codebase. They hack FreeBSD[0] to achieve cool numbers over and over[1][2]. Intel's device mentioned by you - AX200 - works "fine" on my ThinkPad, for a few months now. The device was on supported hardware list for more than a year prior, but the actual driver wasn't covering all vendor/device id pairs (different flavors of hardware or behavior all known as "the same" chip; this is a major problem with consumer devies since chip outages started). That said, by "fine" I mean that I can use the card and finally can connect to 5GHz networks and avoid disruptions related to 2.4GHz congestion. But FreeBSD is still incapable of utilizing speeds offered by modern WiFi specifications. Even with 5GHz connection, only throughput typical for 802.11n can be expected. At this point, I guess that modern WiFi (as protocol/specification) support will only mature in form of drivers ingested from Linux, and emulated via LinuxKPI[3]. And it's great! I'm using Ryzen's Radeon features and DRM stuff on FreeBSD thanks to the LinuxKPI compatibility layer, for a few years now. It's great that whenever FreeBSD can suck some non-GPL codebase from Linux via extending its "compatibility layer" - there's no major hostility. FreeBSD failed with evolving WiFi support on it's own. KPI worked great with amdgpu/DRM, and I have high hopes that Linux codebase will allow FreeBSD to evolve its WiFi support most reasonably. [0] https://www.youtube.com/watch?v=q4TZxj-Dq7s https://www.youtube.com/watch?v=q4TZxj-Dq7s [1] (400Gbps PDF) https://people.freebsd.org/~gallatin/talks/euro2021.pdf https://people.freebsd.org/~gallatin/talks/euro2021.pdf [1] (400Gbps video) https://www.youtube.com/watch?v=_o-HcG8QxPc https://www.youtube.com/watch?v=_o-HcG8QxPc [2] (800Gbps PDF) https://people.freebsd.org/~gallatin/talks/euro2022.pdf https://people.freebsd.org/~gallatin/talks/euro2022.pdf [2] (800Gbps video) https://www.youtube.com/watch?v=_o-HcG8QxPc https://www.youtube.com/watch?v=_o-HcG8QxPc [3] https://wiki.freebsd.org/LinuxKPI https://wiki.freebsd.org/LinuxKPI