Mastodon

Infrastructure


What I’m running: the infrastructure behind this site, in case you were wondering.

AS201379

Public-internet IPv6-first network

  • 4x FreeBSD edge routers running FRR
  • /48 2a06:9801:1c::/48
  • IXPs: LocIX Düsseldorf, FogIXP Zürich, EVIX
  • Direct: BGP session with Hetzner (AS24940)
  • Home: MikroTik speaking iBGP, /64 from the /48
FreeBSDFRRRPKIIPv6-first

AS4242422539 / DN42

The hobbyist parallel internet

  • Border: MikroTik CHR (bhyve), 3x WireGuard peers
  • BGP: import/export filters, per-peer local-pref
  • DNS: FreeBSD bastille jail, PowerDNS authoritative for chofstede.dn42
  • Why: BGP is what people in this line of work do instead of model railways
DN42WireGuardRouterOS

Self-Hosted, All The Way Down

FreeBSD jails on ZFS, inside AS201379

  • This site (Pelican, static)
  • Mastodon: burningboard.net
  • Mail: Postfix + Dovecot
  • DNS: PowerDNS, Unbound
  • Git: Forgejo + Quadlets, Forgejo CI
  • Home Assistant, Cryptpad, Keycloak, FreeIPA
JailsZFSBastillecdist

Day Job: The Red Hat Stack

What customers actually pay me for

  • RHEL 7-10, hardening, lifecycle, ZFS-on-root for the brave
  • Ansible + AAP, Execution Environments, collections
  • FreeIPA / IdM, Kerberos, LDAP, SSSD, SSO
  • Satellite, content lifecycle at scale
  • Keycloak, OIDC, SAML, federation
RHCERHCSARHELAAP

Networking, Done Properly

IPv6 first, IPv4 grudgingly

  • BGP: FRR on FreeBSD, BIRD where it fits, MikroTik and Cisco where the customer already has them
  • Filtering: pf, ipfw, GeoIP rules, RPKI valid-or-undefined
  • VPN: WireGuard, IPsec
  • HTTP/3: QUIC on nginx + FreeBSD, because why not
IPv6 SageBGPFRR

Code & Automation

If I do it twice, it gets a playbook

  • Ansible (since the early days), roles, collections, EE images
  • cdist for FreeBSD jails, because it just works
  • Python, Bash, a bit of Rust when it matters
  • Podman + Quadlets, Java past life still occasionally useful
AnsiblePythonPodman