In my previous posts, we’ve journeyed through the process of Bridging the Gap: Bringing Modern Kismet to OpenBSD and had some Fun with RTL-SDR on OpenBSD tracking planes and smart meters. Today, I’m diving deeper into the invisible signals surrounding us by shifting our focus to Bluetooth Low Energy (BTLE) and Zigbee.

I’ve always been curious about what IoT devices around me are actually saying “behind my back” - fitness trackers, smart lightbulbs, and even toothbrushes are constantly “advertising” their presence. In this post, we will look at how to set up a professional-grade sniffing environment on OpenBSD using both the classic Adafruit Bluefruit Sniffer (nRF51822) and the modern nRF52840 (specifically the nice!nano).

Following up on my previous post about Bridging the Gap: Bringing Modern Kismet to OpenBSD, it is time to explore the hardware that makes much of this wireless exploration possible. If you have a spare USB port and a €50 RTL-SDR dongle, you can turn your OpenBSD box into a powerful radio scanner.

What is SDR?

Software Defined Radio (SDR) shifts the heavy lifting of radio signal processing from dedicated hardware circuits to software. Traditionally, if you wanted to listen to a new frequency or decode a new protocol, you needed a specific physical radio. With SDR, the hardware is simply a “dumb” front-end that digitizes a chunk of the RF spectrum; your CPU handles the demodulation and decoding.

For years, OpenBSD was stuck in a technical time-warp. While the rest of the world moved to Kismet “Newcore” - with its powerful web-based UI, distributed capture, and multi-protocol support—the OpenBSD port remained anchored to the legacy ncurses version.

The core software, with some small patches, compiled fine, but there was a massive void: no Wifi capture driver for OpenBSD. To move forward and finally retire the ancient version, I had to build the engine: capture_openbsd_wifi.

In my previous article on this topic, I described how to build a legally compliant imprint using a c/o address and VoIP numbers. While that works, it is technically “patchwork.”

I have since found a solution that is even more elegant: online-impressum.de. Here is why I switched and how it simplifies my setup.

The Problem with the Phone Number

According to § 5 DDG (German Digital Services Act), an imprint must provide means for “fast electronic contact” and “immediate communication.” For a long time, this meant: Email + Phone. However, case law and the wording of the law allow for some leeway: if a contact form enables a response within a few minutes or hours, it can potentially replace the phone number.

Starting a blog is exciting, but if you are hosting from Germany or targeting European readers, you’ll hit a legal roadblock before your first “Hello World”: the Impressumspflicht (Imprint) and the DSGVO (GDPR).

Here is how I navigated the legal requirements, secured a privacy-friendly address, and implemented a multilingual setup in Hugo.

Why Do You Need This?

In Germany, § 5 DDG (formerly TMG) requires almost every website to have an “Impressum” (Legal Notice). It’s not just for businesses; even a hobby blog can be considered “business-like” if you have affiliate links or just a general “permanence.”

I love writing code and maintaining OpenBSD ports, but manually copying links to five different social media platforms is a chore that keeps me away from my workbench. Here’s how I built a ‘zero-touch’ distribution system.

Why Make.com? (The 2026 Automation Shootout)

As an IT enthusiast, I don’t just want things to “work” - I want them to be efficient and cost-effective. Before committing to this setup, I audited the current automation market. Why did I choose Make over the other major players?