On 03/18/2015 05:30 AM, Robert Moskowitz wrote:
For some reason, after LOTS of idle chatter between my F21 SSH client and the server (I am assuming these are SSH application keep-alives), my F21 SSH client sends a TCP keep-alive. This is after some long time of the client NOT sending an SSH idle packet. As soon as the server receives this TCP keep-alive, it sends a TCP RST and that 'breaks the pipe'. So what in the client determines the rate of SSH keep-alives and for how long inactive?
Look at ServerAliveCountMax and ServerAliveInterval in /etc/ssh/ssh_config and ~/.ssh/config, however as Gordon has mentioned, it smells like an IP conflict and one way to sort it is "arping" the remote host. <snip> ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - "How does that damned three seashell thing work?" - - -- Sylvester Stallone, "Demolition Man" - ---------------------------------------------------------------------- -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
