No route to host. Root cause: 5 GHz channel hit a DFS radar event (~64s eviction), and macOS refused to reroam because RSSI (-68 dBm) was just inside the threshold. The Hitron's web UI is locked; channel control is no longer possible without bridge mode. Solution: bridge the Hitron, drop a Wi-Fi 6 router behind it, lock the 5 GHz channel to UNII-1 (no DFS), point DNS at Cloudflare.
Wi-Fi 6 (AX5400 class). Full web UI with explicit channel, channel-width, and band-steering control. No app required. No cloud account. Six external antennas, OFDMA + MU-MIMO.
Available at Amazon, Best Buy, Newegg. Black with red trim — looks gamer-ish but it's quiet, no LEDs by default.
Also grab: 25 ft Cat6 ethernet cable (~$10) if you want to place the router somewhere other than next to the Hitron.
Write down the SSID (Plum MD) and password. If you reuse them on the new router, every device on the network auto-reconnects without intervention.
Plug the router in for power only — no ethernet yet. Note the default admin URL and Wi-Fi shown on the bottom-of-router sticker.
This is the only way to disable the Hitron's Wi-Fi and NAT. After bridge mode, the Hitron passes traffic to whatever's plugged into port 1 and stops doing anything else.
If the toggle isn't visible: log into the Xfinity website on a laptop instead — same path, same toggle. Some app versions hide it behind "More Settings."
Cat6 ethernet from the Hitron's port 1 → the new router's WAN port (yellow on TP-Link, blue on ASUS, labeled "Internet" on either). Power-cycle the new router.
Connect a laptop directly to the router via ethernet OR via the default Wi-Fi printed on its sticker. Browse to:
http://192.168.0.1 or http://tplinkwifi.nethttp://192.168.50.1 or http://router.asus.comRun the wizard. Set:
Plum MD (same as before so devices auto-reconnect)Wireless → Advanced Settings (or "Wireless" tab). Apply the values in the table below.
Internet/WAN settings → DNS. Override the ISP-supplied Comcast DNS — those servers were one of the failure paths during the 12:29 outage.
| Setting | 5 GHz | 2.4 GHz | Why |
|---|---|---|---|
| Channel | 36, 40, 44, or 48 | 1, 6, or 11 | UNII-1 5 GHz has no DFS — radar evictions can't happen. 2.4 GHz: pick whichever is least crowded; UI shows neighbor density. |
| Channel width | 80 MHz | 20 MHz | 5 GHz: 80 is sweet spot. 2.4: 20 prevents collisions in dense Wi-Fi areas. |
| Auto channel | OFF | OFF | Auto re-scans periodically and can land on DFS again. Lock both. |
| DFS | OFF / Disabled | n/a | Some firmwares have a separate DFS toggle. Off. |
| Mode | 802.11ax | 802.11ax | Wi-Fi 6 only. Disable legacy unless old IoT needs it. |
| Smart Connect / Band Steering | OFF | Off initially. Run separate SSIDs (Plum MD + Plum MD-2G) so you can test which band each device prefers. Re-enable later if you want. | |
| Position | Cloudflare | Quad9 (blocks known malicious) |
|---|---|---|
| Primary | 1.1.1.1 |
9.9.9.9 |
| Secondary | 1.0.0.1 |
149.112.112.112 |
| IPv6 primary | 2606:4700:4700::1111 |
2620:fe::fe |
| IPv6 secondary | 2606:4700:4700::1001 |
2620:fe::9 |
Pick one provider for both rows — don't mix. Cloudflare = pure speed, Quad9 = malware blocking.
Disconnect the laptop's ethernet, connect to Plum MD Wi-Fi.
Run a sustained ping for 3 minutes. Expect 0% loss:
ping -c 200 1.1.1.1
Check signal at the workspace. RSSI should be -55 to -65 dBm. If it's still around -68 or worse, repositioning the router is your next move (or a mesh node).
sudo wdutil info | grep -E "RSSI|SNR|Channel"
Real-world test:
MAC cache on Comcast's CMTS sometimes pins the old MAC for ~10 min. Reboot the Hitron from the Xfinity app. If still nothing, unplug the Hitron coax for 30s, plug back in.
Xfinity app → Bridge Mode → OFF. The Hitron returns to gateway-mode. The new router becomes useless until bridge is re-enabled. Zero risk path — bridge mode is fully reversible.
That points upstream to Comcast's coax side, not Wi-Fi. Open a ticket with this evidence:
That framing forces them past the "is your Wi-Fi working" deflection script.
That's a Mac-side issue independent of the router. Most likely fix: macOS update (14.2.1 has known IO80211 issues). Cleanest workaround at moment of failure:
sudo ifconfig en0 down && sudo ifconfig en0 up
Could also bind that to a Raycast / Alfred / shortcut.
Total: $130–140 hardware, 30 min one-time setup. Pays for itself the first time a discovery call doesn't drop.