search for: clientalive

https://bugzilla.mindrot.org/show_bug.cgi?id=2572 Bug ID: 2572 Summary: dead sessions aren't closed despite ClientAlive enabled Product: Portable OpenSSH Version: 3.7.1p2 Hardware: All OS: Linux Status: NEW Severity: major Priority: P5 Component: sshd Assignee: unassigned-bugs at mindrot.org...

https://bugzilla.mindrot.org/show_bug.cgi?id=2252 Bug ID: 2252 Summary: RekeyLimit breaks ClientAlive Product: Portable OpenSSH Version: 6.6p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: sshd Assignee: unassigned-bugs at mindrot.org Reporter: wiwi at progon.net...

...was updating our ssh-servers, I rewrote my old patch that adds idletimeout (just like in old ssh1) parameter to openssh. Since reapplying the patch for all new versions of openssh is not fun at all, I would like to have it included in the official openssh, if you consider the patch worthy. Unlike ClientAlive, idletimeout works for both protocol versions. It also works together with ClientAlive (however, the code which prevents clientalive-messages from resetting idletimeout is not foolproof. Foolproof patch would require to add different idletimeout support to different packets, which would be too comp...

...be connected to. > > Refer to the second diagram here: > > http://libguestfs.org/virt-p2v.1.html#how-virt-p2v-works > > I don't know why the second connection has been dropped. Does the > conversion server have ssh timeouts enabled? Or bash timeouts? You > can check ClientAlive* settings in /etc/ssh/sshd_config. Also look > for TMOUT or TIMEOUT environment variables on the conversion server. > You can also look in the logs on the conversion server to see if the > ssh connection was dropped or forced to close, and why. > > Rich. > > -- > Richard Jo...

...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. Disconnect after 90 seconds. ServerAliveInterval 30 ServerAliveCountMax 3 In /etc/ssh/sshd_config: # ClientAlive is more flexible and secure than TCPKeepAlive. (ssh2) # Send an alive messages every 30 seconds, and disconnect after 90 seconds. ClientAliveInterval 30 ClientAliveCountMax 3 The ssh client kept hanging even after the network was resumed. It finally timed out after about 2 hours because the tcp_ke...

Hi, I've been trying to migrate a physical host with two disks (the first, sda, is the OS disk and the second, sdb, is a data disk) into a VM, and it always fails on the second disk. The first disk, the OS disk, migrates fine, but when it starts on the second it fails almost straightaway with the following error: (0.00/100%)^Mqemu-img: Could not open '/var/tmp/v2vovl811e67.qcow2':

Fix and/or document issues raised in this thread: https://www.redhat.com/archives/libguestfs/2017-February/msg00010.html Rich.

Hello. Yes, i think that was the cause why agent forwarding wasn't performed at all, i had to rm(1) the control socket and the next ssh(1) connection forwarded the agent normally again. (It was a huge timeshift by several hours.) I.e., just in case this is something you didn't have on your radar yet. Ciao. --steffen

...quot; (in fact an NBD server) cannot be connected to. Refer to the second diagram here: http://libguestfs.org/virt-p2v.1.html#how-virt-p2v-works I don't know why the second connection has been dropped. Does the conversion server have ssh timeouts enabled? Or bash timeouts? You can check ClientAlive* settings in /etc/ssh/sshd_config. Also look for TMOUT or TIMEOUT environment variables on the conversion server. You can also look in the logs on the conversion server to see if the ssh connection was dropped or forced to close, and why. Rich. -- Richard Jones, Virtualization Group, Red Hat ht...

...t; Refer to the second diagram here: >> >> http://libguestfs.org/virt-p2v.1.html#how-virt-p2v-works >> >> I don't know why the second connection has been dropped. Does the >> conversion server have ssh timeouts enabled? Or bash timeouts? You >> can check ClientAlive* settings in /etc/ssh/sshd_config. Also look >> for TMOUT or TIMEOUT environment variables on the conversion server. >> You can also look in the logs on the conversion server to see if the >> ssh connection was dropped or forced to close, and why. >> >> Rich. >>...

Hi! There are configuration knobs (TCPKeepAlive) to enable/disable the use of TCP keepalives both in the ssh client and server. Unfortunately some UNIX systems default to SO_KEEPALIVE=on and some to =off. This may even be settable on a per host basis (OpenBSD default net.inet.tcp.always_keepalive=1 ???). For the TCPKeepAlive configuration knob I would like to propose changes along the lines

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:

Doing a search in the list archives, I see that in 2001/2002 there was a patch made available for IdleTimeout keyword, for example: http://marc.info/?l=openssh-unix-dev&m=99838019319356&w=2 Looks like that patch did not make it in the following versions of OpenSSH - is there a reason why - any chance of the patch getting back in? I do know about ClientInterval, but I think I need

https://bugzilla.mindrot.org/show_bug.cgi?id=2698 Bug ID: 2698 Summary: Tracking bug for OpenSSH 7.6 release Product: Portable OpenSSH Version: -current Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: Miscellaneous Assignee: unassigned-bugs at

...onnection tracking of TCP connections. The firewall has an idletimeout of TCP connections of between 30-40 minutes. After the timeout expires it just drops the packets related to that connection, and the ssh session is dead. The random packets functionality remedies this annoyance. Yes, sshd can do ClientAlive, but one isn't always in control of the system one is connecting to. Firewall reconfiguration is no easy option when dealing with a Windows NT-centric IT-department... Patch against openssh-2.9p2. /Martin diff -ur openssh-2.9p2/clientloop.c openssh-2.9p2.servalive/clientloop.c --- openssh-2...

https://bugzilla.mindrot.org/show_bug.cgi?id=2443 Bug ID: 2443 Summary: Bugs intended to be fixed for OpenSSH 7.1 Product: Portable OpenSSH Version: -current Hardware: Other OS: Linux Status: NEW Keywords: meta Severity: enhancement Priority: P5 Component: Miscellaneous

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 Assignee: unassigned-bugs at mindrot.org...

...ServerAlive detection kicks in as expected. This happens on every openssh version I've tried (All on linux, the versions on ubuntu 8.04, 10.04, 10.10, 12.04, 14.04), and is still in current from browsing the source code. The problem is the "ServerAlive" logic (and I assume, also the ClientAlive logic on the server side - though I haven't verified that yet): A connection is deemed "alive" if the select() waiting for data did not time out. However, it should be deemed alive only if there has been data on the ssh connection itself - not the local ends of a -L / -R tunnel and...

...ss 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: TCPKeepAlive no ClientAliveInterval 90 ClientAliveCountMax 6 ~/.ssh/config: Host * Protocol 2 Compression yes TCPKeepAlive no ServerAliveInterval 90 ServerAliveCountMax 6 But I guess the ssh client doesn't try to re-establish the session for the ServerAlive messages to work. The shells remain bl...

https://bugzilla.mindrot.org/show_bug.cgi?id=2543 Bug ID: 2543 Summary: Tracking bug for OpenSSH 7.3 release Product: Portable OpenSSH Version: -current Hardware: Other OS: All Status: NEW Keywords: meta Severity: normal Priority: P1 Component: Miscellaneous