This is my Raspberry PI Zero W - the original one - connected via wifi to my home network - powered by NetBSD. It's in read only as described by one of my former blog posts (https://it-notes.dragas.net/2024/09/10/make-your-own-readonly-device-with-netbsd/)

It contains my blog and serves it to the caching reverse proxies via IPv6 (via HE Tunnel Broker, no native IPv6 connection from home, yet). Those reverse proxies refresh the contents every 5 minutes and, to be sure this host is alive, continuously connect to it, via http. So this little toy receives a status connection every second and refreshes the contents as soon as they expire.

rpi# uptime

2:37PM up 27 days, 21:52, 4 users, load averages: 0.00, 0.00, 0.00

The caching reverse proxies help, but it can manage the normal load without particular problems: I tried a couple of times, I've removed the reverse proxies and I've also posted a link on the Fediverse, the best way to generate tons of (real) connections.

Sure, the CPU spikes, but it stays stable and reliable.

Here's the dmesg - after almost 28 days:

rpi# dmesg

[...]

[ 1.417036] bwfm0: Found Firmware file: brcmfmac43430-sdio.bin

[ 1.447119] bwfm0: NVRAM file default: brcmfmac43430-sdio.txt

[ 1.447119] bwfm0: NVRAM file model-spec: brcmfmac43430-sdio.raspberrypi,model-zero-w.txt

[ 1.447119] bwfm0: Found NVRAM file: brcmfmac43430-sdio.raspberrypi,model-zero-w.txt

[ 1.447119] bwfm0: CLM file default: brcmfmac43430-sdio.clm_blob

[ 1.447119] bwfm0: CLM file model-spec: brcmfmac43430-sdio.raspberrypi,model-zero-w.clm_blob

[ 3.218970] bwfm0: CHIPACTIVE

[ 3.319052] bwfm0: address xx:xx:xx:xx:xx:xx

[ 3.319052] bwfm0: wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f

[ 22.167139] wsdisplay0: screen 4 added (default, vt100 emulation)

No errors, no warnings, no problems.

#NetBSD #SelfHosting #LowPoweredDevices #RunBSD

Reply to this note

Please Login to reply.

Discussion

No replies yet.