Host Identity
- <strong>Hostname</strong>: blowfish.lab.bitsmasher.net (alias: blowfish)
- <strong>IP</strong>: 10.10.12.15
- <strong>MAC</strong>: 98:b7:85:21:ad:77 (from DHCP reservation)
- <strong>OS</strong>: OpenBSD (planned; current DNS/DHCP entry references it as an OpenBSD host)
Role in the Lab
Blowfish is provisioned as a <strong>database host</strong> within the lab infrastructure. It was intended to serve as a dedicated database server, separate from the primary infrastructure hosts (chonk, stargate, skynet).
The OpenBSD role in the lab-franklin Ansible collection includes configuration references specific to blowfish:
- Login configuration uses \texttt{blowfish} password hashing algorithm (\texttt{localcipher=blowfish,a}) in \texttt{/etc/login.conf}.
- The bootstrap.sh for OpenBSD hosts includes a direct \texttt{/etc/hosts} entry for blowfish (10.10.12.15).
- DHCP reservation is configured in the lab's dhcpd.conf role.
Current Status
Blowfish has been <strong>unreachable</strong> from chonk since the initial infrastructure audit. The IP 10.10.12.15 resolved from DNS (stargate's /etc/hosts), but authentication was denied -- no matching SSH key was authorized on that host.
Key references:
- network\_update.sh: blowfish is the default target for the \texttt{openbsd\_bootstrap()} function.
- OpenBSD role tasks: includes commented-out ansible setup command for blowfish (indicating the host was expected to be online).
The host may need network investigation -- it resolved from DNS, had a DHCP reservation, and MAC address on file, suggesting it was once part of the lab but has since gone offline or been decommissioned.
Planned Configuration (OpenBSD)
When brought online, the expected setup for blowfish is:
- SSH key-based authentication via \texttt{~/.ssh/authorized\_keys}
- OpenBSD's built-in \texttt{pf} firewall with custom rules
- Database software stack (likely PostgreSQL or MariaDB on OpenBSD)
- Ansible-managed configuration via the lab-franklin collection, using the openbsd role as the base profile.