Tons of new evidence (no tcpdump
yet):
- I'm still running RC1 on the Belkin RT3200
- I decided to try a couple more devices running
htop
, so I fired up my old MacBook Pro ("oMBP") and an old Win10 laptop. My primary machine is a newer MBP. All three were connected via Wi-Fi and runninghtop
successfully. - After ~1h 15 minutes, I got tired of waiting, so I stopped
htop
and exited the SSH sessions on oMPB and the Win10 machine . - Within 5 minutes,
htop
froze on the third computer (MBP). I could not re-establish a new SSH connection. (oMBP and Win10 were still disconnected from SSH at that time.) - While the new MBP was in that bad state, I was able to ssh in to the router and run
htop
on oMBP and Win10. After checking thathtop
worked, I stopped it and exited the SSH session on those machines. - I turned off Wi-Fi on the new MBP, then turned it back on, and was immediately able to reconnect to the router.
My summary of the evidence:
- Something is interfering with SSH & Wi-Fi. Running
htop
over Wi-Fi freezes within 5-20 minutes, and that computer cannot re-connect to SSH. - If multiple computers were connected via Wi-Fi and running
htop
, no freeze was observed (I waited 1h 15m, when a freeze normally occurs within 20 minutes) - (I didn't try it in this round of experiments, but...) SSH over Ethernet seems always to work
- When one computer is in the "frozen-Wi-Fi" state, another computer can SSH in via Wi-Fi
- When I turned Wi-Fi off and back on for the affected computer, it could immediately SSH back in.
What's the next experiment? tcpdump
? Thanks