Tagged “networking”

Putting It Together: A Worked Inventory Replication Example

Constructing It Client-Side, and the Blueprint Surface

FastArraySerializer: Replicating Lists Without Resending Everything

Custom NetSerialize: Packing Your Fields by Hand

USTRUCTs as Network Payloads, and Exposing Them to Blueprints

Breaking Up Data Objects to Send Across the Network in Unreal

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

Multi-WAN Failover That Actually Fails Over

QoS for a Household That Streams Absolutely Everything

Multi-WAN Failover That Actually Fails Over

Running My Own Recursive Resolver

IPv6 at Home, Eventually

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

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

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

making multi-wan failover do the one thing it promises

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

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

qos for a house that never stops streaming

ripping out openvpn and not missing it

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

the resolver lives here now

when everything works except the big stuff

mtu, the silent killer

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

pulling vlans through a network that had none

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

a year on mikrotik, would i go back to pfsense

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

the day my homelab lost its name

ipv6 at home, eventually

i run bgp at home now and i regret nothing

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

when packets vanish and it's just the mtu

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

a year on mikrotik after a decade on pfsense

ipv6 at home, eventually

mtu, the silent killer

multi-wan failover that actually fails over

keeping the video call alive when the house is streaming

cutting out the middleman with my own resolver

ipv6 at home, eventually

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

bgp in the homelab, because why not

multi-wan failover that actually fails over

keeping the video call alive while everyone else streams

the day i deleted every port forward and slept better

i finally threw out openvpn

the day i stopped forwarding ports

multi-wan failover that fails over before anyone notices

running my own recursive resolver at home

cutting a flat network into vlans without taking everything down

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

getting multi-WAN failover to actually fail over

stop trusting someone else's dns

the half-hour my homelab lost dns to itself

i finally tore out openvpn and the house got quieter

making the second internet line earn its keep

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

i am now running bgp at home and i regret nothing

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

i finally gave up on port forwarding

when everything works except the things that don't

making the wifi fair when everyone is buffering at once

i stopped trusting someone else's dns

the day my homelab dns ate itself

when packets vanish: an mtu mystery

a year on mikrotik, and what i miss from pfsense

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

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

running bgp at home, for reasons i can mostly justify

running bgp at home because i could not help myself

making multi-WAN fail over before anyone notices

i finally ripped out openvpn

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

keeping a video call alive whilst the house streams

i deleted every port forward and the homelab got better

yes, i run bgp at home

the network was fine until the packets got big

the day i broke dns and blamed everything else first

getting ipv6 working at home, eventually

making the wifi behave when everyone is streaming at once

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

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

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

getting ipv6 working at home, only a decade late

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

mtu, the silent killer, comes for my vpn

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

ipv6 at home, eventually

a year of running mikrotik and pfsense side by side

forty lines of config and my vpn just worked

cutting a flat network into vlans without burning the weekend

i gave up on port forwarding and i feel fine

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

running my own recursive resolver at home

dragging a flat home network into vlans without losing the wifi

wireguard finally killed my openvpn config

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

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

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

the day i stopped trusting someone else's resolver

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

tearing out openvpn and not missing it for a second

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

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

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

the bug that only showed up on large files

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

the time a stale ttl outlived my actual mistake

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

mtu, the silent killer

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

getting ipv6 working at home, eventually

taming a house that streams everything at once

the path mtu problem that only broke big requests

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

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

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

running bgp at home, for no good reason

mtu, the silent killer

mikrotik or pfsense, twelve months in

the day i pointed my whole house at a dead resolver

getting ipv6 working at home, finally

carving up a flat network into vlans, the hard way