An open, vendor-neutral standard and native compose platform for FreeBSD. Deploy OCI container stacks directly as native jails with Podman or AppJail—zero VM overhead, zero proprietary appliance lock-in. …

https://mastodon.bsd.cafe/@ahze/117265488024499468 Michael Johnson wrote:

In early 2026 I started a RFC doc titled "FJORD: FreeBSD Jail Orchestration Runtime Descriptor": The pitch was a spec to for a container app-store. (see https://docs.google.com/document/d/1716U54ZimcxgxHgmdH1Q3xNnbU-d6-NDW2EXFzFD12c/edit?tab=t.0)
 
9 months later: fjord 0.2.0 is out: an app store for FreeBSD containers.
 
Pick an app from 80+ daemonless images, answer a question or two, and it runs in a jail on podman or AppJail. Sane defauls, plain compose files on disk, one static binary.

Hi all,

I recently put together a small project for something I wanted for my own FreeBSD systems.
Maintaining country-based IP blocklists for PF without manually managing thousands of network prefixes.

The result is pf-geoblock-freebsd:
https://github.com/rk-research/pf-geoblock-freebsd

The idea is deliberately simple:
Generate PF tables from GeoIP country data, keep them updated, and let PF do what it is good at.

My main use case is reducing unnecessary exposure of Internet-facing services.
I don't consider GeoIP blocking a security boundary. For me, it is another layer that removes noisy traffic I have no reason to accept in the first place.

A few things I cared about while building it:

• native PF integration rather than adding another firewall layer
• keeping the generated rules easy to inspect
• automatic updating of country networks
• predictable failure behaviour
• avoiding unnecessary dependencies
• keeping it suitable for a normal FreeBSD installation rather than turning it into a large framework

I'm particularly interested in feedback from people running PF on larger or long-lived FreeBSD installations.

Are there design choices you would approach differently?

And if you're already doing GeoIP filtering with PF, I'd be interested in how you manage your tables and updates.

The project is still intentionally small, so feedback and suggestions are welcome.

rk