When I was trying out Netdata last year — I noticed I had lots of inbound_packets_dropped_ratio warnings, on multiple nodes.

Time to investigate 👇

Getting network to the garage is a story with many chapters. I started out with Wi-Fi mesh, then CAT6 — and now, finally, fiber!

I’ve been having a strange problem with outgoing WireGuard traffic, the problem has probably always been there — I just haven’t noticed, until now. Outgoing WireGuard traffic is very slow, while incoming is what I’d except with my 750/750 fiber internet connection.

This lead me down a rabbit hole of testing performance internally, which I documented in a previous blog post. That turned out to be a queue issue on the SFP+ port on my MikroTik CHR router. Could this also be queue related?

While doing some WireGuard testing between local peers; I noticed weird performance issues on my virtual MikroTik router. This lead me down a rabbit hole of testing the layer 3 throughput on my virtual CHR.

The bit rate started at close to 10 Gbit/s, but then dropped to 3-4 — only in one direction 🤷 Time to investigate…

I first got started on the network run from the attic switch to the 2nd floor den — back in October of 2021. I finished it a year later, so it’s about time to get this blog post published 😛

We recently moved the twins into their own bedrooms, after sharing a room for nine years — it was finally time for some privacy 🙂

With their own rooms; they also got their own computers — a life long dream 😉 Those computers needs network, proper network, not Wi-Fi.

We recently put up a wall in our previous family/play room — to make another bedroom, with a hallway outside. I might want an access point in that hallway at some point.

So I repurposed a telephone outlet and conduit, to run a CAT6 cable from the hallway down to the patch panel in the basement.

I stumbled onto NextDNS recently — it’s like a cloud hosted Pi-hole. I tried it for a few days, but this post isn’t about that.

Reading about the different block lists in NextDNS, and digging deeper into DNS ad blocking gave me motivation to change my current setup — and that is what this post is about 🙂

The Unifi UAP-AC-M access point in my garage stopped working a few weeks ago. Or, the device didn’t stop working, it still showed up in the Unifi controller and I could ping it. But it stopped providing Wi-Fi connectivity — my phone connected, but got no network access…

I remembered experiencing this before — the VLANs for user and guest Wi-Fi wasn’t allowed through the D-Link switch. I had simply not configured them, but why was it failing now?

Trying to log into the switch — I found that it no longer got an IP from the DHCP server. By all accounts; it looked like the switch had been reset.

Last year — I wrote about plans for my home network, or home network v2, as I called it. Let’s take a look at what I have done, what remains, and what has changed since then.