Openbsd
Step 1 was getting my hands on Raspbian. Step 2 was running OpenBSD on the Raspberry Pi 3 Model B. I had quite a few try & fails but it booted, installed and ran properly in the end. Full story follows.Continue reading...
I’ve enabled an OpenBSD unbound(8) daemon that is used as a central DNS cache resolver. Now I needed to know what it was doing and how it performed. The question was answered grabbing statistics from unbound and render them using Grafana.
The whole monitoring stack is composed of Net-SNMP, Telegraf and InfluxDB for the metrics part ; and syslogd(8), Logstash and Elasticsearch for the logs part. Of course, most of those run on OpenBSD (6.3) ; except Telegraf, which is not available (yet).Continue reading...
I regularly check my pf(4) activity using pfctl(8) and pflogd(8). I already monitored pf using collectd(1) and rrdtool. This time, I wanted to use my already configured InfluxDB/Grafana system. The thing is, Telegraf is not (yet) available in OpenBSD 6.3. So I used a Telegraf container to remotely poll OpenBSD using the native SNMP OPENBSD-PF-MIB.Continue reading...
I took the time to switch from OpenBSD 6.2 to 6.3 on my Cloud instance with encrypted disk. As usual, it went smooth and troubleless. For the record, here are the directions.Continue reading...
By default, a DHCP client gets an IP address, a network gateway and a DNS server. That’s fine most of the time. But if you own an OpenBSD cloud instance that has to use DHCP to get online, you might not be satisfied with the domain-name-servers option provided by your DHCP server. Hopefully, OpenBSD provides an easy way to force your DNS:
# vi /etc/dhclient.conf (...) prepend domain-name-servers 127.0.0.1; Since then, OpenBSD will use our DNS resolver. Which is… unbound(8)Continue reading...