Why do I get 'connection reset by peer' ssh disconnections more frequently from my home internet versus the office internet?
I've been researching this issue on and off for years now and the other questions&answers on this site and Google don't help me.
Here's an actual disconnect example when my internet was otherwise fine:
Read from remote host examplehost.com: Connection reset by peer Connection to examplehost.com closed.
I've been through all the checking of ssh/sshd config, etc., for things like
ServerAliveInterval, ServerAliveCountMax, TCPKeepAlive, including esoteric suggestions like enable/disable
All systems are CentOS servers.
I connect to the same servers, via ssh, from the office and at home. I setup the routers, myself, at both places. The office router is an small-office class DSR-250N and my home router is a home-class DLink DIR-655.
Possibly of interest: I use VPN and, intriguingly, ssh connections over VPN seem to stay up as long as the VPN stays up (days to weeks).
This has been going on for years so I now suspect it has to do with router limitations rather than who provides the internet, but I'm not sure exactly what limitations there might be on a home-class router and what to look for in a new router to ensure these problems are at least reduced significantly.
Maybe it's router memory, maybe it's something like those 'session limit' specs I see on some routers, etc.?
I would be satisfied to know if the problem is just my relatively low-end router (although I think it's upper-middle end for home routers).