This is not a question, rather a solution hoping to save others from frustration.
We recently upgraded to a BlueCurve modem. The speed increase was great and the signal was more reliable upstairs. With the family working at home we needed reliable Internet at good speeds and BlueCurve does that.
Unfortunately, I was finding that my SSH connections were dropping at random. Sometimes they would last for a day and sometimes would drop after a few minutes. The problem got so bad that I finally resorted to a hard-wired connection, so that I could still work from home. Fortunately, I have found a solution for wireless connections.
BlueCurve modems are dual band, 2.4 GHz and 5 GHz. This is good. Conveniently, the modems support band steering, so that connections automatically switch to whichever band has better signal strength.
For SSH, this automatic switching turns out to be bad. When there is channel congestion on 5 GHz, the connection is switched to the 2.4 GHz band, which causes active SSH connections to drop.
The solution is to give separate SSIDs to the two bands, e.g. myshaw24 and myshaw5. Now that I have done that, my SSH connections are rock solid.
There may be other workarounds or adjustments to SSH or band steering configurations that would help, but I have a simple solution that works well and I am satisfied.
It is possible that other applications which depend upon long-lived TCP connections are similarly affected by automatic band flipping and could benefit from this solution.
