Tagged “homelab”

The Day I Took Down My Whole Network With One DNS Change

Multi-WAN Failover That Actually Fails Over

Too Many Dashboards And Not Enough Sense

Moving Services Off the Cloud and Back Home

QoS for a Household That Streams Absolutely Everything

Backups I Actually Test Now

TrueNAS and the Great Disk Shuffle

Multi-WAN Failover That Actually Fails Over

Running My Own Recursive Resolver

Too Many Dashboards, and the Slow Walk Back

TrueNAS and the Great Disk Shuffle

IPv6 at Home, Eventually

the garage rack, two years on, regrets included

bgp in the homelab, because why not

ipv6 at home, after years of putting it off

ipv6 at home, after years of meaning to

i put bgp in the spare room and i regret nothing

bringing it all back home, one service at a time

keeping the telly happy when everyone's online at once

bgp in the homelab, because why not

qos for a household that streams everything

tailscale, and finally giving up on port forwarding

a backup you've never restored is just a hope

one compose file to rule the homelab

i built fourteen dashboards and look at none of them

the backup you never restore is just hope on a disk

nextcloud, for the third time, and the setup that finally stuck

pulling a few things back off the cloud

i built nineteen dashboards and looked at two

mikrotik or pfsense? a year on, the verdict is "it depends" and i mean it

moving twelve terabytes without losing my nerve

how home assistant quietly colonised my free time

replacing every disk in the pool without losing my nerve

bringing the small things back home from the cloud

making multi-wan failover do the one thing it promises

building multi-WAN failover that fails over when you're not watching

real certificates for services that never touch the internet

a year of MikroTik after a decade of pfSense

i fired my ISP's DNS and ran my own resolver instead

a year on mikrotik, and i'm not going back to pfsense

one compose file to rule the homelab (and the regret that followed)

qos for a house that never stops streaming

ripping out openvpn and not missing it

reverse proxy, certs, and let's encrypt at home

i ran kubernetes at home, and mostly regret it

a year on MikroTik after a decade on pfSense, the honest verdict

backups you haven't restored are just wishes

the resolver lives here now

when everything works except the big stuff

mtu, the silent killer

nextcloud, again, but properly this time

the afternoon i broke dns and then couldn't look up how to fix it

docker compose for the whole house

pulling vlans through a network that had none

kubernetes in the spare room, and why i kept some of it

cutting a flat home network into vlans without taking it all down

i had eleven dashboards and could not tell you if anything was broken

home assistant ate my evenings, and i let it

a year on mikrotik, would i go back to pfsense

why i finally left esxi for proxmox

bringing it all back home

the homelab as one stack, profiles and all

one compose file to rule the homelab

my third nextcloud install, and the first one i trust

small packets fine, large packets gone: an mtu story

keeping the calls clear when the house won't stop streaming

speaking bgp to my own cupboard

one compose file to run the house

bringing it all back home

the day my homelab lost its name

bringing it all back home

ipv6 at home, eventually

i have too many dashboards and not enough alerts

i run bgp at home now and i regret nothing

i stopped trusting other people's dns and ran my own

nextcloud, again, properly this time

moving the homelab off esxi and onto proxmox

when packets vanish and it's just the mtu

the backup you have not restored is a rumour

i swapped pfsense for a mikrotik a year ago, here is the honest scorecard

how i moved every disk in my nas without losing a byte

home assistant ate my evenings

bringing it all back home

the garage rack, and what i'd do differently

the day i pulled esxi out of the rack

a year on mikrotik after a decade on pfsense

bringing the services home again

nextcloud, again, and this time it sticks

the day i resilvered the wrong pool

bringing it all back home

nextcloud, the third attempt, and the one that actually stuck

ipv6 at home, eventually

mtu, the silent killer

multi-wan failover that actually fails over

rebuilding a truenas pool one disk at a time

truenas and the great disk shuffle

keeping the video call alive when the house is streaming

too many dashboards and not enough alerts

cutting out the middleman with my own resolver

one compose file to rule the homelab

a rack in the garage, regrets and all

ipv6 at home, eventually

a year of running mikrotik next to pfsense, and which one stayed

why i finally moved the homelab off esxi and onto proxmox

bgp in the homelab, because why not

multi-wan failover that actually fails over

bringing the small stuff back home from the cloud

how a single smart plug became a second job

bringing the small stuff back home

the backups i actually restore from now

keeping the video call alive while everyone else streams

the day i deleted every port forward and slept better

the garage rack, and what i'd do differently

tls on the home network without the faff

i finally threw out openvpn

rebuilding nextcloud and meaning it this time

the day i stopped forwarding ports

multi-wan failover that fails over before anyone notices

running my own recursive resolver at home

real certificates for things that never touch the internet

cutting a flat network into vlans without taking everything down

how home assistant quietly stole a fortnight

i put a server rack in the garage, and i'd do it again (mostly)

running bgp at home, which i will not pretend i needed to

the great disk shuffle, or how i rebuilt a pool without losing my nerve

a backup you have not restored is a rumour

getting multi-WAN failover to actually fail over

stop trusting someone else's dns

bringing it all back home, one service at a time

the backups i finally bothered to test

the half-hour my homelab lost dns to itself

i finally tore out openvpn and the house got quieter

how home assistant quietly took over my evenings

kubernetes at home was a mistake (mostly)

making the second internet line earn its keep

real certificates for things that never touch the internet

the day i deleted every port forward and didn't miss them

i am now running bgp at home and i regret nothing

i put a proper rack in the garage and i have feelings about it

replacing every disk in a pool without losing the pool

making the wifi survive four people streaming at once

i finally stopped poking holes in my firewall

running bgp at home, purely to learn it

one compose file to rule the house

i finally gave up on port forwarding

reverse proxy, certs, and let's encrypt at home

home assistant ate my evenings

nextcloud, the third install and the one that stuck

when everything works except the things that don't

i put a server rack in the garage and i have notes

one compose file to run the whole house

every exporter i installed and the one metric i should have started with

i ran kubernetes in my house for two years, here is the bill

i had forty grafana dashboards and looked at three

a backup you haven't restored isn't a backup

a rack in the garage, regrets and all

making the wifi fair when everyone is buffering at once

i stopped trusting someone else's dns

the day my homelab dns ate itself

i have built too many grafana dashboards

when packets vanish: an mtu mystery

one compose file to rule the house

a year on mikrotik, and what i miss from pfsense

replacing every disk in a pool, one at a time

reverse proxy, certs, and let's encrypt at home

why i moved the homelab from esxi to proxmox

running kubernetes at home was mostly a mistake

i stopped trusting someone else's resolver and ran my own

a year on mikrotik, and what i miss about pfsense

i stopped trusting other people's dns

getting IPv6 working at home, finally

i finally ripped out openvpn for wireguard

cutting a flat homelab into vlans without burning it down

i ran kubernetes at home and mostly regret it

running the whole house from one compose file

nextcloud, the fourth attempt, the one that stuck

the backups i now bother to restore

why my homelab moved off esxi onto proxmox

the day i deleted every port forward and felt better

a year of mikrotik and pfsense, and which one i kept

the year i finally let ipv6 into the house

bringing it all back home

running bgp at home, for reasons i can mostly justify

the day i put a server rack in the garage

running bgp at home because i could not help myself

making multi-WAN fail over before anyone notices

nextcloud, again, properly this time

i ran kubernetes at home and mostly regretted it

i finally ripped out openvpn

one compose file to run the entire flat

the day my whole house lost dns, and it was me

keeping a video call alive whilst the house streams

bringing it all back home

nextcloud, the third time, done properly

proper https for everything on the home network

a rack in the garage, regrets and all

docker compose for the whole house

i deleted every port forward and the homelab got better

i had forty dashboards and no idea if anything was broken

running the whole house on one docker-compose file

home assistant ate a fortnight of my evenings

yes, i run bgp at home

the network was fine until the packets got big

one compose file to run the whole house

rebuilding nextcloud the way i should have the first time

truenas and the great disk shuffle

the day i broke dns and blamed everything else first

too many dashboards, not enough alerts

dragging my services back home from the cloud

a rack in the garage, regrets and all

a rack in the garage, regrets and all

nextcloud, again, properly this time

bringing the small stuff back home

getting ipv6 working at home, eventually

nextcloud, for the third time, finally done properly

home assistant ate my evenings

home assistant ate my evenings

backups i actually test now

making the wifi behave when everyone is streaming at once

one compose file to rule the cupboard

ipv6 at home, after only a decade of putting it off

bringing the services home, one bill at a time

i built forty graphs and looked at none of them

two connections, one that works, and the gap between them

the vpn that fit in a screenful of config

multi-wan failover that actually fails over

making the router care about the right packets

rebuilding the nas without losing anything

the homelab outage that was hiding in 50 bytes of overhead

small pings work, big ones don't

carving VLANs out of a flat network without taking the house offline

kubernetes at home was a mistake (mostly)

backups I actually test now

moving services off the cloud and back home

getting ipv6 working at home, only a decade late

rebuilding my nas one disk at a time without losing my nerve

carving up a flat network without taking the house offline

i put bgp in my house and i regret nothing

a year of mikrotik and pfsense side by side

kubernetes at home was a mistake, mostly

i monitored everything and learned almost nothing

mtu, the silent killer, comes for my vpn

the day i broke my own dns and blamed everyone else first

truenas and the great disk shuffle

ipv6 at home, eventually

bringing the small stuff back home from the cloud

i finally swapped esxi for proxmox at home

a year of running mikrotik and pfsense side by side

i moved the homelab off esxi and onto proxmox

i swapped esxi for proxmox and the homelab got friendlier

forty lines of config and my vpn just worked

i ran kubernetes at home so you don't have to

cutting a flat network into vlans without burning the weekend

i gave up on port forwarding and i feel fine

one reverse proxy to terminate them all

i built fourteen dashboards and looked at none of them

running bgp at home, for reasons i can only half justify

a rack in the garage, and everything it taught me the hard way

there is a server rack in my garage now and i have feelings about it

i put kubernetes in my spare room and mostly regret it

moving the homelab from ESXi to Proxmox

running my own recursive resolver at home

one docker-compose file to rule the homelab

truenas and the great disk shuffle

running kubernetes at home, and what it actually taught me

dragging a flat home network into vlans without losing the wifi

one compose file to run the whole house

home assistant ate my evenings, and i let it

i built a dashboard for everything and could see nothing

wireguard finally killed my openvpn config

i swapped esxi for proxmox in the rack and didn't look back

replacing a pool, one disk at a time, without losing my nerve

i finally threw out my openvpn config and i'm not going back

a year of mikrotik, and what i miss about pfsense

getting ipv6 working at home, only eighteen months late

a year of mikrotik and pfsense, and which one stayed

the backups i finally bothered to restore

rebuilding a pool one disk at a time without losing my nerve

i ran kubernetes at home and mostly regret it

one reverse proxy, real certs, and no more browser warnings at home

i put a rack in the garage, and the garage had opinions

it's never dns, except when it's mtu

truenas and the great disk shuffle

i stopped trusting someone else's dns and ran my own

the day i stopped trusting someone else's resolver

i built fourteen dashboards and look at none of them

backups i actually test now

why i swapped esxi for proxmox at home

the day the house lost the internet, and it was dns, and it was me

i ran kubernetes at home, and mostly i regret it

why i finally moved the homelab off esxi and onto proxmox

the great disk shuffle, or how i rebuilt my nas without losing a byte

one compose file to run the entire house

tearing out openvpn and not missing it for a second

i ran kubernetes at home for a year so you don't have to

the resolver was fine, the search domain was not

dropping google's dns for my own unbound

carving a flat network into vlans without taking the house down

running kubernetes at home was a mistake, mostly

i instrumented everything and then drowned in dashboards

mikrotik vs pfsense, a year later

bgp in the homelab, because why not

ipv6 at home, eventually

vlans on a flat network, the painful migration

a year on MikroTik after a decade on pfSense

why i moved the homelab off esxi and onto proxmox

i ran kubernetes at home and i'm mostly sorry

chopping a flat home network into vlans without taking it all down

the bug that was always mtu

carving up a flat network without taking the house offline

the homelab that worked for everything except big files

one compose file to run the whole house

i put a rack in the garage and i mostly don't regret it

the bug that only showed up on large files

i ran kubernetes in my house and i have regrets (mostly)

the network that worked, except when it really mattered

a year on the mikrotik, and what i still miss from pfsense

carving a flat home network into vlans without taking it all down

one docker-compose file to run the whole house

the time a stale ttl outlived my actual mistake

i built a wall of dashboards and stopped looking at any of them

a year of running both mikrotik and pfsense, and what i'd actually keep

mtu, the silent killer

i monitored everything and learned nothing

taming the upload so the house stops fighting itself

the day my own resolver broke and dnssec was right to

i stopped trusting my isp's dns and ran unbound

truenas and the great disk shuffle

getting ipv6 working at home, eventually

a rack in the garage, regrets and all

a year on proxmox, and i'm not going back

home assistant has quietly eaten a month of my life

kubernetes at home was a mistake (mostly)

real certs for the things on my own network

taming a house that streams everything at once

the path mtu problem that only broke big requests

kubernetes at home was a mistake, mostly

one compose file to run the lot

getting ipv6 into the house, the slow way

running bgp at home, which i did not need to do

getting ipv6 working at home, eventually

the garage rack, one winter in

i ran bgp in my own house and learned things i didn't need to

one compose file to run the whole house

shuffling disks under freenas without losing my nerve

i threw out my openvpn config and i feel lighter for it

the great disk shuffle, or how i grew a freenas pool the slow way

ripping esxi out of the homelab for proxmox

running bgp at home, for no good reason

i swapped esxi for proxmox and didn't look back

one compose file to run the house

i put kubernetes in my house and i have regrets

mtu, the silent killer

i bought a server rack for the garage

terminating tls at home with one nginx box

ripping ESXi out of the homelab for Proxmox

mikrotik or pfsense, twelve months in

kubernetes at home was a mistake, mostly

the day i pointed my whole house at a dead resolver

getting ipv6 working at home, finally

proper certs at home with a reverse proxy and let's encrypt

carving up a flat network into vlans, the hard way

one compose file to run the house