<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>NetworkDaddy</title>
<link>https://networkdaddy.net/</link>
<description>Practical, tested articles on networking, cybersecurity, backups and homelabs — written by a working IT professional.</description>
<language>en</language>
<atom:link href="https://networkdaddy.net/rss.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Slow Wi-Fi? Check router placement before you buy anything</title>
<link>https://networkdaddy.net/posts/slow-wifi-check-router-placement/</link>
<guid>https://networkdaddy.net/posts/slow-wifi-check-router-placement/</guid>
<pubDate>Tue, 20 Oct 2026 12:00:00 GMT</pubDate>
<category>Networking</category>
<description>Placement, channel congestion and interference cause more slow Wi-Fi than your internet plan does. Here's how to diagnose it in 20 minutes.</description>
<content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>Most &quot;slow internet&quot; complaints I get aren't about the internet at all. The connection coming into the house is fine — the problem is the last 30 feet between the router and your laptop. Before you upgrade your plan or buy a mesh kit, run through these checks.</p>
<h2 id="step-1-prove-where-the-slowdown-is">Step 1: Prove where the slowdown is</h2>
<p>Plug a laptop directly into the router with an Ethernet cable and run a speed test. Then run the same test over Wi-Fi standing next to the router, and again in the room where things feel slow.</p>
<div class="table-wrap"><table><thead><tr><th>Test</th><th>What it tells you</th></tr></thead><tbody><tr><td>Wired at the router</td><td>What your provider is actually delivering</td></tr><tr><td>Wi-Fi next to the router</td><td>Whether the router's radio is healthy</td></tr><tr><td>Wi-Fi in the problem room</td><td>How much signal you lose to distance and walls</td></tr></tbody></table></div>
<p>If the wired test is slow, call your provider. If only the problem room is slow, keep reading — it's a Wi-Fi coverage issue.</p>
<h2 id="step-2-get-the-router-out-of-the-closet">Step 2: Get the router out of the closet</h2>
<p>Routers broadcast in roughly a sphere. Every wall, floor, mirror, fish tank and metal cabinet takes a bite out of that signal. The worst places for a router are exactly where they usually end up: inside a media cabinet, behind the TV, or in a corner of the basement.</p>
<ul><li>Put it <strong>central</strong> and <strong>high</strong> — a shelf in the middle of the home beats a floor in the corner.</li><li>Keep it <strong>in the open</strong>, not in a cabinet.</li><li>Keep it away from microwaves, cordless phone bases and large metal objects.</li></ul>
<aside class="callout callout-tip"><p class="callout-title">Tip</p><p>If the internet line comes in at the edge of the house, a single long Ethernet cable to a central spot costs a few dollars and often fixes everything.</p></aside>
<h2 id="step-3-check-for-channel-congestion">Step 3: Check for channel congestion</h2>
<p>In apartments and townhomes, your neighbours' networks compete for the same airtime. On the 2.4 GHz band only channels 1, 6 and 11 don't overlap, so pick whichever is least crowded. Most phones have free Wi-Fi analyzer apps that show this at a glance.</p>
<p>Better still, connect devices that support it to <strong>5 GHz</strong> (or 6 GHz on Wi-Fi 6E/7 gear). It's faster and less crowded, but it doesn't travel through walls as well — which is why placement matters even more.</p>
<h2 id="step-4-update-the-firmware">Step 4: Update the firmware</h2>
<p>Router firmware updates fix bugs, improve performance and close security holes. Log in to the router's admin page or app and check for updates. If the router hasn't had an update in years, that's a sign it's time to replace it.</p>
<h2 id="step-5-decide-whether-you-actually-need-mesh">Step 5: Decide whether you actually need mesh</h2>
<p>Only after the steps above should you consider more hardware:</p>
<ul><li><strong>Still dead zones in a large or multi-storey home?</strong> A mesh system or wired access points will help.</li><li><strong>Can you run cable?</strong> Wired access points (or mesh nodes with a wired backhaul) beat wireless mesh every time.</li><li><strong>Small apartment?</strong> You probably don't need mesh — a well-placed modern router is enough.</li></ul>
<h2 id="the-short-version">The short version</h2>
<ol><li>Test wired vs. wireless to find where the problem actually is.</li><li>Move the router somewhere central, high and open.</li><li>Use 5 GHz where you can and pick an uncrowded channel.</li><li>Update the firmware.</li><li>Buy hardware last, not first.</li></ol>]]></content:encoded>
</item>
<item>
<title>Turning on MFA: the order that actually matters</title>
<link>https://networkdaddy.net/posts/turn-on-mfa-in-the-right-order/</link>
<guid>https://networkdaddy.net/posts/turn-on-mfa-in-the-right-order/</guid>
<pubDate>Tue, 13 Oct 2026 12:00:00 GMT</pubDate>
<category>Security</category>
<description>Multi-factor sign-in is the single best security upgrade most people can make. Start with the account that can reset all the others.</description>
<content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>Multi-factor authentication (MFA) means signing in takes something you know (your password) plus something you have (your phone or a security key). Even if your password leaks, an attacker can't get in without the second factor.</p>
<p>Most people agree it's a good idea and then never finish setting it up. The trick is to do it in the right order, so the most important accounts are protected first.</p>
<h2 id="1-your-primary-email">1. Your primary email</h2>
<p>Your email is the master key. Almost every other account lets you reset its password by email, so whoever controls your inbox can take over everything else. Protect it first.</p>
<h2 id="2-your-password-manager">2. Your password manager</h2>
<p>If you use one (and you should), it holds every other password. Turn on MFA and store its recovery codes somewhere safe and offline.</p>
<h2 id="3-banking-and-payments">3. Banking and payments</h2>
<p>Banks, credit cards, PayPal, and any app that can move money.</p>
<h2 id="4-your-phone-account">4. Your phone account</h2>
<p>Your mobile carrier account is a target for &quot;SIM swap&quot; attacks, where someone convinces the carrier to move your number to their SIM card. Add a PIN or passcode to the account — most carriers support this.</p>
<h2 id="5-everything-else">5. Everything else</h2>
<p>Social media, cloud storage, shopping sites, and work tools. Do a few a day until the list is done.</p>
<h2 id="which-kind-of-mfa-should-you-use">Which kind of MFA should you use?</h2>
<div class="table-wrap"><table><thead><tr><th>Method</th><th>Security</th><th>Notes</th></tr></thead><tbody><tr><td>Passkey or security key</td><td>Best</td><td>Resistant to phishing. Use wherever it's offered.</td></tr><tr><td>Authenticator app</td><td>Very good</td><td>Codes generated on your phone, works offline.</td></tr><tr><td>Push approval</td><td>Good</td><td>Never approve a prompt you didn't trigger yourself.</td></tr><tr><td>Text message (SMS)</td><td>Okay</td><td>Better than nothing, but vulnerable to SIM swaps.</td></tr></tbody></table></div>
<aside class="callout callout-warning"><p class="callout-title">Warning</p><p>Save your recovery codes when you set up MFA. If you lose your phone without them, getting back into your account can take days.</p></aside>
<h2 id="the-ten-minute-plan">The ten-minute plan</h2>
<p>Pick the top three accounts on this list and turn on MFA tonight. That alone puts you ahead of most people — and most attackers move on to easier targets.</p>]]></content:encoded>
</item>
<item>
<title>The 3-2-1 backup rule, and why you must test restores</title>
<link>https://networkdaddy.net/posts/3-2-1-backup-rule/</link>
<guid>https://networkdaddy.net/posts/3-2-1-backup-rule/</guid>
<pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate>
<category>Backups</category>
<description>Three copies, two kinds of storage, one off-site — and a backup you've never restored is just a hope.</description>
<content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>Drives fail, laptops get stolen, and ransomware encrypts everything it can reach. The 3-2-1 rule is the simplest way to make sure none of that becomes a disaster.</p>
<h2 id="the-rule">The rule</h2>
<ul><li><strong>3 copies</strong> of your data — the original plus two backups.</li><li><strong>2 different kinds of storage</strong> — for example your computer's drive and an external drive or NAS.</li><li><strong>1 copy off-site</strong> — in the cloud or at another location, safe from fire, theft and floods.</li></ul>
<h2 id="a-setup-that-works-for-most-homes-and-small-offices">A setup that works for most homes and small offices</h2>
<ol><li><strong>Local backup:</strong> an external drive or NAS running automatic backups (Time Machine on a Mac, File History or a backup app on Windows).</li><li><strong>Off-site backup:</strong> a cloud backup service that runs in the background.</li><li><strong>Phones:</strong> turn on your phone's cloud backup and photo sync.</li></ol>
<h2 id="protect-backups-from-ransomware">Protect backups from ransomware</h2>
<p>Ransomware tries to encrypt or delete any backup it can reach. Defend against it by:</p>
<ul><li>Keeping at least one copy that isn't permanently connected — or uses versioning, so you can roll back to before the infection.</li><li>Using a separate account for the backup system, with its own password and MFA.</li></ul>
<h2 id="test-your-restores">Test your restores</h2>
<aside class="callout callout-important"><p class="callout-title">Important</p><p>A backup is only as good as your last successful restore.</p></aside>
<p>Once a quarter, pick a random file and a random folder and restore them to a different location. Check that they open. Once a year, practise a full recovery of one machine. It's far better to find a broken backup on a quiet afternoon than during an emergency.</p>]]></content:encoded>
</item>
<item>
<title>Separate your smart devices from your computers</title>
<link>https://networkdaddy.net/posts/separate-iot-devices/</link>
<guid>https://networkdaddy.net/posts/separate-iot-devices/</guid>
<pubDate>Tue, 29 Sep 2026 12:00:00 GMT</pubDate>
<category>Networking</category>
<description>Cameras, TVs and smart plugs rarely get security updates. Here's how to put them on their own network — from a simple guest network to full VLANs.</description>
<content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>Smart TVs, cameras, doorbells, plugs and thermostats are convenient, but many of them get few security updates. If one is compromised, you don't want it sitting on the same network as the laptop you use for banking.</p>
<p>The fix is <strong>network segmentation</strong>: put those devices on their own network so they can reach the internet but not your computers.</p>
<h2 id="option-1-use-your-router-s-guest-network-easy">Option 1: Use your router's guest network (easy)</h2>
<p>Most routers have a guest network that's isolated from the main one.</p>
<ol><li>Turn on the guest network and give it its own name and strong password.</li><li>Make sure &quot;allow guests to access the local network&quot; is <strong>off</strong>.</li><li>Reconnect your smart devices to the guest network.</li></ol>
<p>This takes about 15 minutes and covers most homes.</p>
<h2 id="option-2-vlans-more-control">Option 2: VLANs (more control)</h2>
<p>If you have a business-grade or prosumer router and managed switch, you can create VLANs — separate virtual networks running over the same hardware. A common layout:</p>
<div class="table-wrap"><table><thead><tr><th>VLAN</th><th>Devices</th><th>Can reach</th></tr></thead><tbody><tr><td>Trusted</td><td>Laptops, phones</td><td>Everything</td></tr><tr><td>IoT</td><td>TVs, plugs, cameras</td><td>Internet only</td></tr><tr><td>Guest</td><td>Visitors</td><td>Internet only</td></tr></tbody></table></div>
<p>Firewall rules then decide what can talk to what. For example, allow your phone to reach the cameras' viewing app, but block the cameras from reaching anything on the trusted network.</p>
<h2 id="a-few-gotchas">A few gotchas</h2>
<ul><li><strong>Casting and AirPlay</strong> rely on devices discovering each other. If casting to the TV stops working after you split networks, your router may need mDNS or multicast forwarding enabled between the networks.</li><li><strong>Cameras</strong> that record to a local recorder need that recorder on the same network, or a firewall rule allowing it.</li><li><strong>Label everything.</strong> Write down which network each device is on — future you will be grateful.</li></ul>
<h2 id="where-to-start">Where to start</h2>
<p>If you've never done this before, start with the guest network tonight. You can always graduate to VLANs later.</p>]]></content:encoded>
</item>
</channel>
</rss>