Labthrift Labthrift What to buy. What to skip. Why.

Written 6 Sep 2026. This is a how-to, not a product card.

When house Wi-Fi on the old PC keeps dropping

SSH dies or ads come back because the computer's Wi-Fi keeps falling off. Check power save, signal, then prefer a cable. You don't need a mesh kit tonight.

Still joining Wi-Fi for the first time? Put the old PC on house Wi-Fi. Cable is plugged in but dark? That failure is when the cable is plugged in but there's no link. This note is the other mess: the radio already joined the house, then flaps — SSH hangs from the couch, Pi-hole vanishes, or the address changes after idle. Don't buy a mesh kit for one old laptop tonight.

Skip until it is actually on Wi-Fi

If the computer lives on a cable and never uses the radio, this page is not your job — stay with a cable beats Wi-Fi for the computer. If it never joined house Wi-Fi, start with put the old PC on house Wi-Fi. If closing the lid puts a laptop to sleep, fix that first: don't let the old laptop sleep. You need a keyboard and monitor on the computer, or a moment when the radio comes back, so you can run a few commands.

What this is

House Wi-Fi that works, then falls off, is usually the radio sleeping to save power, a weak signal (wrong band through walls), or the router kicking an idle client. It is not “buy mesh.” It is not a new router. Walk power save and signal first. Prefer a cable when a port and a short run exist.

Step 1: prove the radio dropped

From the couch, SSH may hang or refuse. That alone does not name Wi-Fi. On the computer (keyboard and monitor, or after it comes back), print short link status:

ip -br link

Then device status if NetworkManager is installed:

nmcli device status

Or list Wi-Fi interfaces:

iw dev

The radio name is often wlan0, or it starts with wlp. Write that name down. You want the radio line UP with a house address when it is working. When it flaps, the line may go DOWN, lose the address, or show no carrier while the cable line (if any) stays quiet. Recent radio noise in the journal:

journalctl -b -u NetworkManager

Or, if that unit is missing:

journalctl -b | grep -iE 'wlan|wifi|nl80211'

When the radio is up, ping the router. Find the gateway with ip route (the default via line) and swap GATEWAY:

ping -c 3 GATEWAY

Three replies mean the path to the house router works right now. Drops after idle still point at power save or a weak link.

Step 2: rule out sleep and wall power

A laptop that sleeps when the lid closes looks like “Wi-Fi died.” Keep it awake: don't let the old laptop sleep. Confirm the brick is doing work: see if the old laptop is actually plugged in. If nothing answers on any path, prove the box is awake: is it still on?. Fix those before you chase radio settings.

Step 3: signal and band

Move the computer closer to the house access point for one test. If SSH stops hanging near the router, the far spot is the problem — walls, floors, or a 5 GHz band that does not reach. Many old laptops are happier on 2.4 GHz for a box that sits far from the AP. On the router, pick the 2.4 GHz SSID (or a combined name that prefers 2.4 for that client) and join again from the computer. Don't buy a mesh kit for one practice machine yet. A short ethernet run beats another radio hop.

Step 4: turn off Wi-Fi power save

Linux often puts the radio to sleep between packets. That saves battery on a laptop you carry. On a box you leave on for SSH and Pi-hole, it drops connections. Name the interface from Step 1 (swap wlan0 for yours):

iw dev wlan0 get power_save

If it says on, turn it off for this boot:

sudo iw dev wlan0 set power_save off

Check again:

iw dev wlan0 get power_save

That iw change lasts until the next reconnect or reboot. If NetworkManager manages the radio, make it stick. Create or edit:

sudo nano /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf

Put this in the file (value 2 means power save off):

[connection]

wifi.powersave = 2

Save, then:

sudo systemctl restart NetworkManager

Confirm with iw again after it reconnects. Prefer one durable fix. Don't stack three different power-save hacks. If NetworkManager is not installed (common on a netplan + networkd Ubuntu Server), the iw off is still the proof — then prefer a cable so you are not fighting the radio overnight.

Step 5: prefer a cable when you can

When a port and a cable can reach the router (or a switch on the house LAN), plug it in on purpose: a cable beats Wi-Fi for the computer. If the cable is seated but there is no link, that walk is when the cable is plugged in but there's no link. Once SSH works on the cable address, stop the radio from coming back so one address stays: keep Wi-Fi off after a reboot. Optional later: see the cable speed.

What this is not

This is not a mesh kit, a new router, or a Wi-Fi 7 upgrade for one old PC. It is not forwarding ports so SSH “survives” a flaky radio. It is not dual-homing (Wi-Fi plus ethernet as the plan). It is not the first-time join note — that is put the old PC on house Wi-Fi. Stay on power save, signal, then a cable.

What next

If the radio never joined, start with put the old PC on house Wi-Fi. When a cable can reach, switch: a cable beats Wi-Fi for the computer, then keep Wi-Fi off after a reboot. Cable dark? When the cable is plugged in but there's no link. Still hunting the number after a flap: find it on the house network, then SSH from the couch. SSH odd with a good link: when SSH won't connect. Ads back after the radio vanished: when ads come back. Lid sleep and wall power still matter: don't let the old laptop sleep, see if the old laptop is actually plugged in, is it still on?.

Optional: jot that the practice machine stays on house Wi-Fi (or moved to a cable) in Lab plan — username + passkey, no email. Skip if you just want to keep reading.

Skip

Sources

Debian: iw. Ubuntu: iw. NetworkManager.conf (wifi.powersave). NetworkManager: 802-11-wireless (powersave values). Debian: nmcli. Ubuntu: nmcli. Debian: ip-link. Official pages only. For the first join, see put the old PC on house Wi-Fi. For a cable, see a cable beats Wi-Fi for the computer. For a dark cable jack, see when the cable is plugged in but there's no link.

Also on this topic

Put the old PC on house Wi-FiUbuntu Server on an old laptop often has no cable nearby. Join house Wi-Fi so SSH and Pi-hole can work. Skip this if ethernet already works. A cable beats Wi-Fi for the computerOnce the computer is doing real work, plug it into the router with a cable. House Wi-Fi can wait. Skip this if it is already on a cable. When the cable is plugged in but there's no linkEthernet is seated, but SSH still hangs or the computer never gets a house address. Check both ends, LAN vs WAN, link lights, then ip link before you buy a NIC. Keep Wi-Fi off after a rebootAfter the cable works, stop Wi-Fi from coming back so the computer keeps one address. You don't need a new router. Don't let the old laptop sleepClose the lid. The old laptop has to stay awake so SSH and Pi-hole keep working. A desktop can skip this note. See if the old laptop is actually plugged inBefore you trust the old laptop overnight, confirm it is drawing wall power. A dying battery is not a reason to buy a UPS. Is it still on?You left the computer on. This morning ads are back, or SSH hangs. Check if it is awake before you buy anything. When ads come backAds are back, sites won't load, or a phone still shows banners. Check the computer, Pi-hole, router DNS, then the phone. When SSH won't connectSSH hangs, says connection refused, or Permission denied. Check the computer is on, confirm the address, then the user and password. You don't need a new router or a KVM. Find the computer on the house networkThe computer has a number on your house network. You need that number to SSH from the couch. You don't need a new router. SSH from the couchType commands on the old PC from your laptop, on the house network. Password login first. Don't open this to the internet. See the cable speedAfter the cable works, see whether the link is 1G or stuck slower. You don't need a 10G switch for this check.