FreeBSD 14.0-Release

Original Article ↗ Hacker News Discussion ↗

FreeBSD 14.0-RELEASE introduces major upgrades such as OpenSSL 3.0, OpenSSH 9.5, OpenZFS 2.2, expanded SMP support up to 1024 cores on amd64/arm64, improved bhyve virtualization with TPM and GPU passthrough, and early steps toward better Wi‑Fi 6 and Intel wireless support. Commenters highlight practical gains for servers and homelabs—especially ZFS performance, native encryption usability, and high‑throughput networking—while also noting ongoing pain points like weaker container/Docker support, patchy Wi‑Fi drivers, firewall configuration complexity, and rough edges in packaging and automation. There is broad appreciation for FreeBSD’s design, documentation and longevity, tempered by concerns about third-party ecosystem support, the impending drop of most 32‑bit platforms in FreeBSD 15, and the trade-offs versus mainstream Linux in production environments.

Release highlights and performance

  • Discussion notes major upgrades: OpenSSH 9.5p1, OpenSSL 3.0.12 (from 1.1.1t), OpenZFS 2.2, CUBIC as default TCP congestion control, bhyve TPM/GPU passthrough, and SMP scaling to 1024 cores on amd64/arm64.
  • Some commenters link these improvements to large-scale deployments (e.g., multi‑hundred Gbps TLS serving), but note that real limits often come from memory/NUMA bandwidth, not just CPU count.

ZFS, storage, and encryption

  • OpenZFS 2.2 is praised for performance; RAID‑Z expansion has landed post‑2.2 in OpenZFS and FreeBSD -HEAD, but not yet in 14.0.
  • Native ZFS encryption is reported as working in practice, with new boot‑time key‑handling via zfskeys, though some remember earlier guidance favoring GELI.
  • ZFS pool checkpointing is recommended as a safety net before major upgrades.

Networking stack and TCP

  • CUBIC becoming default is highlighted; RACK TCP is available but not default and still under testing.
  • BBR is possible via custom kernels but not part of the standard build.

Wi‑Fi support

  • Wi‑Fi 6 support has been added to wpa_supplicant/hostapd and Intel’s iwlwifi driver has been updated to support up to Wi‑Fi 6E hardware.
  • However, the compatibility layer currently only exposes 802.11a/b/g; 802.11n/ac/ax support is still planned.
  • Some existing drivers (e.g., iwm) remain limited to legacy modes, leading to slow real‑world Wi‑Fi.

Firewalls and usability

  • pf is considered powerful but hard to approach; users miss Linux‑style tools like ufw with strong default IPv6/ICMP rules.
  • There are example configs in the tree and third‑party guides, but no widely endorsed, simple “web server + IPv6” template.
  • Some argue host firewalls can keep ICMPv6 simple (even fully open) if an edge router does the complex filtering.

Architectures and deprecations

  • FreeBSD 14.x is expected to be the last branch with i386, armv6, and 32‑bit PowerPC; 32‑bit armv7 remains, partly due to embedded usage and cleaner time handling.
  • 1024‑core limit is seen as a pragmatic cap balancing scalability and memory usage of per‑CPU data structures; ABI changes aim to allow future increases.

Ecosystem, tooling, and adoption

  • Many praise FreeBSD’s documentation and coherence but criticize parts of the tooling: ports/pkg reliability, automation/installer gaps, and weaker Docker story.
  • Jails are viewed by some as at least on par with Linux containers; others say lack of first‑class Docker and certain third‑party support makes FreeBSD impractical for their work.
  • bhyve is used successfully for running Linux VMs (e.g., to host Docker), though network performance and configuration complexity are concerns.

Cloud and deployment experiences

  • Some cloud providers have dropped native FreeBSD images, but others (UpCloud, Azure, certain VPS hosts, Hetzner via custom images/USB, DigitalOcean via custom images) still support it.
  • Experimental ZFS images for AWS/Azure are noted as a positive sign.
  • Opinions on in‑place major upgrades are mixed: many report smooth experiences, while others prefer fresh installs due to past failures.

Community and contribution

  • Commenters highlight the small team behind FreeBSD, encourage donations, and note how easy it is to contribute via ports (e.g., updating unmaintained ports through Bugzilla).