search for: autossh

Am 14.03.2017 um 21:43 schrieb Nico Kadel-Garcia: > On Tue, Mar 14, 2017 at 4:20 PM, Thomas G?ttler > <guettliml at thomas-guettler.de> wrote: >> >> >> >> 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...

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? -- htt...

...own wrapper script for ssh that deals with multitude of IP addresses, user accounts, keys and other ssh parameters for bunch of managed hosts. On X session start i (actually, my script) load all my private keys with 'ssh-add -c', to get confirmation on every key usage. This works bad with autossh, so i would like to add some logic: if I specify to run autossh with some host/user/key, the scipt will reload the private key without -c option (asking me for password). And maybe at the end of autossh session, reload the key back with 'ssh-add -c'. So, how can i detect if key loaded with...

Package: logcheck-database Severity: wishlist Hi! if autossh debug is enabled it logs to syslog, thus the messages go thru logcheck, messages are in this form May 19 14:02:55 sagara autossh[1909]: port set to 0, monitoring disabled so this is the ignore line ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ autossh\[[0-9]+\]: .*$ thanks, filippo -------------- next par...

We try to run a reliable ssh tunnel vis systemd. This is the unit configuration file: {{{ [Unit] Description=Tunnel For %i After=network.target [Service] User=autossh ExecStart=/usr/bin/ssh -o "ExitOnForwardFailure yes" -o "ServerAliveInterval 60" -N -R 40443:installserver:40443 -R 8080:installserver:8080 ExecStartPre=-/usr/bin/ssh tunnel@%i "for pid in $$(ps -u tunnel | grep sshd| cut -d' ' -f1); do kill -9 $$pid; echo kill o...

...imately 90*6 seconds, ssh aborts complaining of timeout with the remote server. I want to know if there is any way I can get ssh to try to renegotiate the active sessions to remote servers, without disconnecting them. Note: Please don't bother suggesting workarounds such as the use of screen, autossh, etc. I am looking for a specific answer about how to keep a session alive, or the impossibility of doing that. For example, autossh restarts ssh. I want existing sessions to continue as if nothing happened, as long as net access is not down for longer than some timeout. FWIW, I'm using Ope...

...the network card, the >> driver, or the cable, since if I am on a VPN connection via another >> server, the VPN and any ssh connection stay up indefinitely. >> >> Thanks. > Another poster has provided some possible reasons for the > disconnections. Whatever the cause, autossh (from the epel repo) is a > good workaround. > Not that this happens while I do large scp file transfers that may take more than half an hour, simply restarting an ssh session is not going to help since I will lose the file transfer.

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

...ssh where each satellite node should establish a socket on another 127.0.0.0/8 address but each time the same port. Now it looks like we are going to be forced to 127.0.0.1 as long as we have GatewayPorts set to "no" by default. More explainations: client A is going to open a channel by: autossh -i privkey -R 127.0.0.2:2222:127.0.0.1:22 user at host client B is going to open a channel by: autossh -i privkey -R 127.0.0.3:2222:127.0.0.1:22 user at host client C is going to open a channel by: autossh -i privkey -R 127.0.0.4:2222:127.0.0.1:22 user at host But none of this clients is going to...

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

...''): put(''qa.pp'', ''qa.pp'') put(''puppet apply qa.pp'') And puppet files don''t use anything like classes or modules, but simply: package {["nginx", "python-virtualenv", "rsync", "autossh", "redis-server", "git-core", "python-dev", "ntp"]: ensure => installed} service { ''nginx'' : ensure => "running", enable => true, hasrestart => true, require => Package["nginx"] } Now the...

I am trying to set up port forwarding using the client of a multiplexed connection, but the client is dying. The connection paramaters I am using are as follows: for the master: /usr/bin/ssh -T -n -N -o ControlMaster=yes -o ControlPath=/var/run/autossh/control-%r@%h-%p.sock -o ConnectionAttempts=3 -o BatchMode=yes -o EscapeChar=none -o ExitOnForwardFailure=yes -o ServerAliveInterval=15 -o ForwardAgent=no -c arcfour -2 -x user at host.com for the client: /usr/bin/ssh -T -n -N -o ControlMaster=no -o ControlPath=/var/run/autossh/control-%r@%h-%p.soc...

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

...re is anything wrong with the network card, the > driver, or the cable, since if I am on a VPN connection via another > server, the VPN and any ssh connection stay up indefinitely. > > Thanks. Another poster has provided some possible reasons for the disconnections. Whatever the cause, autossh (from the epel repo) is a good workaround. -- Liam

...gt;>> driver, or the cable, since if I am on a VPN connection via another >>> server, the VPN and any ssh connection stay up indefinitely. >>> >>> Thanks. >> Another poster has provided some possible reasons for the >> disconnections. Whatever the cause, autossh (from the epel repo) is a >> good workaround. >> > Not that this happens while I do large scp file transfers that may > take more than half an hour, simply restarting an ssh session is not > going to help since I will lose the file transfer. In that case sftp with the '-a&...

...ince if I am on a VPN connection via > > > another > > > server, the VPN and any ssh connection stay up indefinitely. > > > > > > Thanks. > > > > Another poster has provided some possible reasons for the > > disconnections. Whatever the cause, autossh (from the epel repo) is > > a > > good workaround. > > > > Not that this happens while I do large scp file transfers that may > take more than half an hour, simply restarting an ssh session is not > going to help since I will lose the file transfer. > I don'...

On Sat, May 30, 2015 at 10:38 AM, Phil Pennock <phil.pennock at globnix.org> wrote: > On 2015-05-30 at 15:00 +0200, Kasper Dupont wrote: >> On my laptop I have key1 and key2. I can use key1 to log in >> on server1, and I can use key2 to log in on server2. I want >> neither key to leave the laptop, and only key2 is allowed >> to be forwarded to other hosts. >

Hi all, I use the command below to set up a ssh tunnel. And I run it as a daemon process to keep the ssh tunnel work all the time. And I should wait for the ssh tunnel to be up and notify the tunnel is OK before sending any command to the remote port on the remote server. But the question is I don't know how to check the ssh tunnel status. Is there a way to show whether the ssh tunnel is up?

> 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

These patches implement a new mux client request to list the currently opened TCP forwardings. It also removes some todos regarding keeping the list of forwardings in the options up-to-date. Bert Wesarg (6): attach the forwarding type to struct Forward merge local and remote forward lists generate unique ids for forwardings to be used for identification remove closed forwardings from