similar to: Tip for SSH users with connection unexpectedly closed troubles

Running CentOS 7 on workstation and having a problem with ssh disconnects. My ssh_config contains: Host * TCPKeepAlive yes ServerAliveInterval 30 ServerAliveCountMax 300 and sshd_config on the server contains: TCPKeepAlive yes ClientAliveInterval 60 ClientAliveCountMax 300 Have I missed any setting needed to prevent these random disconnects? I don't think there is anything wrong with the

On 02/12/2018 07:24 PM, Liam O'Toole wrote: > On 2018-02-12, H <agents at meddatainc.com> wrote: >> Running CentOS 7 on workstation and having a problem with ssh >> disconnects. My ssh_config contains: >> >> Host * >> TCPKeepAlive yes >> ServerAliveInterval 30 >> ServerAliveCountMax 300 >> >> and sshd_config on the server contains:

Hi all I have an ADSL modem which reboots when there is a power cut and the inverter (UPS) kicks in. Internet access is down for a duration of 1 to 2 minutes while the modem boots. I have many SSH tunnels and shells active. Due to the default "TCPKeepAlive On" setting, these sessions are terminated almost immediately. I tried the following configuration: sshd_config on server:

Hello, I am testing ssh with occasional network disconnection between server and client during these days. I found ssh sometimes hangs if the disconnection happens after the connection is established but before ssh_exchange_identification completes. The ssh configuration files show that both client and server alive options are set. In /etc/ssh/ssh_config: # Send keepalive messages to the server.

https://bugzilla.mindrot.org/show_bug.cgi?id=1404 Summary: Make keepalive work properly with Cisco PIX/ASA boxes Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: sshd AssignedTo:

I don't believe you've said: are the disconnects happening during periods of idleness on the connection, or periods of activity? If idleness, some device or script could be actively doing a disconnect-on-idle. On Mon, 26 Feb 2018, Kip Warner wrote: > Hey list, > > I've read the man page for both the client and server daemon, so either > I missed something or this

Hi, In the last several years, I noticed an annoying problem with ssh: Long-running ssh connections are automatically disconnected after just a few minutes of inactivity. This problem effects both interactive sessions (using ssh without screen(1) became almost impossible...) as well as ssh port forwarding and the likes. I never noticed this problem until about 6 years ago, but since then have

https://bugzilla.mindrot.org/show_bug.cgi?id=2627 Bug ID: 2627 Summary: Documentation update: semantic of ClientAliveCountMax 0 unclear Product: Portable OpenSSH Version: 7.3p1 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 Component: sshd

Hi, I have a client on a Windows machine that connects through openssh on a linux server. I have this script (tunnel.cmd): @echo off :RUN echo Connecting? "C:/Program Files/OpenSSH/bin/ssh.exe" -R 40201:localhost:50300 -o TCPKeepAlive=no -o ServerAliveInterval=15 -o ServerAliveCountMax=2 -i id_rsa visma at 10.55.40.123 echo Restarting in 10 seconds? GOTO RUN It is runned from another

You could try using an automounter, like autofs, in combination with sshfs. It'll be slower, possibly a lot slower, but it should be more reliable over an unreliable connection. I've been using: remote -fstype=fuse,allow_other,nodev,noatime,reconnect,ServerAliveInterval=15,ServerAliveCountMax=40,uid=0,gid=0,ro,nodev,noatime :sshfs\#root at remote.host.com\:/ BTW, I'm not sure

https://bugzilla.mindrot.org/show_bug.cgi?id=3362 Bug ID: 3362 Summary: [RFE] Implement a mechanism to disconnect idle users Product: Portable OpenSSH Version: 8.8p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee:

Hi openssh-unix-dev subscribers :) I have found that ServerAliveInterval & ServerAliveCountMax have some bug. Basically the ssh-alive check function (that verify the peer is alive) is called only if no data at all gets into ssh (when it should work only for server channel).I am pretty sure developers know about this ..anyway I have tried to fix this issue. Here is the patch: diff -rNu

Howdy: I need some help please to get hiera configuration data derived from YAML, thru puppet. I have studied Internet search results and puppet documentation on create_resources and custom defines but need a little help along. I can print out the YAML from variables, arrays, and, finally, hashes too from a puppet manifest. One thing that is stumping me is how to access from the custom define

> From: Juanito <juam at posteo.net> > > If I create a tunnel like this from the client side, > > ssh -nNTv -o ServerAliveInterval=60 -o ServerAliveCountMax=3 -o IdentitiesOnly=yes -o UserKnownHostsFile=$known_hosts_file -i /etc/sshquare/id_rsa -R $port:localhost:22 $user@$host > > would it be possible on the server side to restrict $port to say 10000 > and

https://bugzilla.mindrot.org/show_bug.cgi?id=3172 Bug ID: 3172 Summary: Idle connections not closed automatically Product: Portable OpenSSH Version: 8.2p1 Hardware: amd64 OS: Linux Status: NEW Severity: critical Priority: P5 Component: sshd Assignee: unassigned-bugs at

Hi OpenSSH team, We found that openssh5.0 has a bug with the "ServerAliveInterval" and "ServerAliveCountMax" options. This function doesnt work at all, which means when the Maxtime reached, the ssh will not kill the connection and prompt the infomation "Connection Timedout" as it used to do. We built the openssh5.0p1 code on the a Linux box, and use the

Hi folks, (3rd time I am sending this message, none of the other appear to have made it through!) Using "OpenSSH_6.9p1 Ubuntu-2ubuntu0.1, OpenSSL 1.0.2d 9 Jul 2015" on the server, "OpenSSH_7.2p2, OpenSSL 1.0.2g 1 Mar 2016" on the client. I am trying to use sshtunnel with StreamLocal forwarding to enable me to connect back to the client's ssh port, without having to

https://bugzilla.mindrot.org/show_bug.cgi?id=2265 Bug ID: 2265 Summary: ServerAlive{Interval,CountMax} ignored if using an active -R or -L tunnel Product: Portable OpenSSH Version: -current Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component:

Buenas tardes, Necesito obtener informaci?n de la cantidad de tuneles ssh que puede tener activo un servidor y adem?s por cuanto tiempo pueden permanecer activos estos tuneles. Explico mi situaci?n, tengo un servidor centos 5.5, con sistema ssh que viene por defecto la versi?n 4.3. A este servidor se conectan alrededor de 100 terminales, cada uno de estos terminales levantan 3 tuneles contra el

On Mon, Feb 12, 2018 at 6:25 PM H <agents at meddatainc.com> wrote: > Running CentOS 7 on workstation and having a problem with ssh disconnects. > My ssh_config contains: > > Host * > TCPKeepAlive yes > ServerAliveInterval 30 > ServerAliveCountMax 300 > > and sshd_config on the server contains: > > TCPKeepAlive yes > ClientAliveInterval 60 >