log2table is a small daemon I wrote: it watches log files, recognizes attack patterns with regular expressions, and puts the offending IP addresses in a PF table so the firewall blocks them. The whole behavior is driven by one file: parameters.py.

Writing rules is easy. Knowing whether they are good rules is harder: do they catch what is really hitting my server today? Do they ban innocent visitors? Do two rules count the same attack twice?

This post explains the new version of parameters.py in the repository, its built-in checker that runs against your real log files, and how I used an AI (Claude, through Claude Code) to read the checker's output and propose improvements.

I've changed my dhcpd daemon from a Actif/passif system managed via ifstated, to an Actif/Actif system without ifstated. I decided to change mainly because this is a builtin feature. A bit complex to setup, but once I've found the correct setup, it's in act easy. My biggest problem was coming from the -Y and -y parameters of dhcpd.

Three days in Brussels with the people who build BSD. A training with Kirk McKusick, talks on FreeBSD's future, a museum visit by tram, and long conversations with names I'd only known from mailing lists. I went in wondering how many people actually make a living from BSD. I came back with an answer, a few new friends, and a lot of respect for a community that mostly does this for love, not money.

This month, this blog turns 10 years old.

I want to use this anniversary post to look back at everything I've written over the last decade: what has stayed the same, what has evolved, and what I've replaced along the way.

Increasingly, new ISP boxes bundling fiber, TV, and all the bells and whistles no longer allow inbound connections from the outside. Unfortunately, that's exactly what I need — I want to reach my home server from anywhere. Thanks to WireGuard as set up on OpenBSD, there's a very simple solution to this. This post explains how to do it.

In the context of the DMA developped in this post, this blog post improve it so to have accents and all nice icons in emails delivered by DMA

This blog provides the precise configuration required to build a localized, self-learning mail server on OpenBSD. We assume your mail is hosted on a remote IMAP service and you want to filter it locally before your best email client (K-9 Mail in my case) ever rings.

This is an intermediary setup where I keep my provider as MX records, but I'm allowed to perform my own spam filtering.

Then by using imap server, I can publish cleaned inbox.

As for each server on internet, I receive lot of bad requests. Thanks to a continuous check on different log files, I'm able to automatically add bad IPs in the pf firewall (OpenBSD). This blog will explain how I've setup log2table and how I treat those bad IPs

Last year I've took notes about the way to connect to FOSDEM's wifi from my laptop doing dual boot OpenBSD and FreeBSD. But this year those commands, were not working. So, here the new method.

FreeBSD jails are one of the operating system’s most elegant features. Introduced over two decades ago, they provide lightweight, secure isolation for processes and filesystems without the overhead of full virtual machines or the complexity of Linux container setups. What makes them especially appealing today is how straightforward it is to create and destroy them — no bridges, no epair interfaces, no VNET, no NAT rules, no sysctl tweaking, and no permanent rc.conf hacks. In this post, I’ll walk you through the exact process I use to spin up a clean FreeBSD 14.3 jail and then completely remove it, demonstrating just how simple and lightweight the whole thing is.