similar to: OpenSSH with "resumable" functionality

Dear Sirs & Madams: Thank you so much for your help. To remind, my situation is a wireless connection that is unreliable, where: (a) upon disconnect, !M's nxclient does not recognize connection death (b) after I manually kill nxssh and reconnect, reconnection takes some time. My idea: intercept myself in between NX client and server - detect connection drop, and reconnect. This is

Dear All: --- Summary, especially for openssh list (to test/reproduce): THANK YOU for all your help. Please extract into /home/username/nx on both host and client. cp ssh to a file named mxssh in that directory. Run (with an _n_ below) Start server on the remote host by typing ./server & Now do: ./nxssh hostname If you killall client on the remote end, it reconnects "seamlessly"

Dear Sirs: Please pardon me I am very new to R. I have been using MATLAB. I was wondering if R would allow me to do principal components analysis on a very large dataset. Specifically, our dataset has 68800 variables and around 6000 observations. Matlab gives "out of memory" errors. I have tried also doing princomp in pieces, but this does not seem to quite work for our approach.

Dear Sirs: Thank you so much for your help. I have now created both the client and server for resumable nx sessions using the ServerAliveInterval option to disconnect after several seconds of server inaccessibility. I am now working on an nxssh "substitute", which at this point seems fairly straightforward. However, when I spawn ssh, I need to know whether: (a) it exited because of

I just stumbled across this thread on openssh-dev... Is there anywhere to track progress on this issue? It'd be a fantastic feature that would fix all sorts of problems I deal with regularly. You may also be interested in an article "Design and Implementation of a Mobile SSH Protocol", if you haven't seen it, since that team implemented (afaict) the same feature, whether or not

What is the canonical link to Reference of "ServerAliveInterval"? Background: I want to write an answer at serverfault (Q-A Site). I want to avoid copy+pasting. I would like to lead the new comer to the canonical reference. Regards, Thomas G?ttler -- Thomas Guettler http://www.thomas-guettler.de/

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

I am pulling my hair out here folks...... ? I am running CentOS 5.5 in command line only.? Reason being I am standing up an IDS system on it.? ? I have installed the NX client/node and server pkgs.? I have installed the NX client for windows on a Vista box.?? When I attemtp to connect from the Vista to CentOS, I get this: ? NX> 203 NXSSH running with pid: 22080 NX> 285 Enabling check on

Am 14.03.2017 um 15:10 schrieb Nico Kadel-Garcia: > Look into the "autossh" program, which is very good to manage and > maintain such tunnels. > Hi Nico and other ssh users, Systemd restarts the ssh if it terminates. AFAIK this is all that is needed. But maybe I am missing something. Is there a feature of autossh that I don't get with systemd? --

Hi All, Using the following to ssh into my home to get mail, I suddenly get this: ssh -o TCPKeepAlive=yes -o ServerAliveInterval=240 -L 110:192.168.100.108:110 phil at FQDN phil at FQDN's password: bind: Cannot assign requested address <---- Last login: Sun Nov 13 23:45:29 2011 from FQDN I have never seen what I am indicating before and am wondering why this would suddenly appear?

The fact that '-o ServerAliveInterval=50' makes no difference suggests that there is a bug in the OpenSSH client. It either fails to sent heartbeats, or it gets stuck in some Windows system call and this makes it to fail to send heartbeats. Yuri

installed freenx server on CentOS 4 server installed nxclient from nomachine.com on workstation so far so good. following directions from web site... http://fedoranews.org/contributors/rick_stout/freenx/ where I tried both /etc/nxserver/client/client.id_dsa.key and /var/lib/nxserver/home/.ssh/client.id_dsa.key copied them to my workstation and then used the 'import' function in

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:

Try setting Host * ? ServerAliveInterval 240 in .ssh/config on the client (wherever that is in Windows).? Or pass "-o ServerAliveInterval=240" on the ssh client command line. I've seen this where connections pass through some low grade external firewall, which drops state after a certain amount of inactivity without sending back RST (and apparently is immune to TCP keepalives

Hello I can''t seem to be able to get X working on domain U My setup domain0 -ubuntu breezy domainU -ubuntu breezy I tried 3 techniques 1. ssh -X domainU steps: on domain U $ export DISPLAY=:0 $ xhost + xhost: unable to open display ":0" on domain0 ssh -X domainU result: ssh conection established no X forwarding starts. after login tried

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:

Hi there, okay so I have a port knocker installed on my remote server so I am trying to bundle a bunch of directories in a single ssh session that rsync establishes. so far all the rsync examples I have seen require a new ssh session for each directory. is there anyway to get something like this into one line and therefore one ssh session. Clues on this? --- snip --- /usr/bin/rsync -avrz

On Mon, 26 Oct 2015, Robert Moskowitz wrote: > On 10/26/2015 01:28 PM, Michael Hennebry wrote: >> >> All too often, my ssh session will freeze. >> I'm fairly certain the problem is at my end. >> Any suggestions on how to diagnose? >> > I had this a lot until I added to /etc/ssh/ssh_config > > ServerAliveInterval 15 Did it complain at all? Mine

Hello, I'm tasked with establishing a persistent SSH connection across a very unreliable link, for a remote port forward (always port 2217). I figured I'd use ServerAliveInterval to make sure that the ssh(1) process dies when the connection appears down, and I use systemd to restart it in this case. This works fine. What does not work fine, however, is the server-side. If the connection