similar to: rsync command for multi files and dirs from remote server

If one wants to go this way, then I just discovered Tags it should work like this (I haven?t tested it and never used tags) Match tagged FA ForwardAgent yes ControlPath ~/.ssh/controlmaster-%r@%h-%p-forwardagent ControlMaster off ? and then to have a session with forwarding: ssh -P FA user at host But I still think we should be able to setup ssh to just do the right thing if the

Hi, A user has noticed that X11 forwarding does not appear to work when using session multiplexing. It seems that the DISPLAY environment variable is not getting set in the slave sessions. Any thought? The ~/.ssh/config ib below. Host somehost-master ControlMaster yes ControlPath ~/.ssh/somehost.sock HostbasedAuthentication no HostName somehost Host somehost-slave ControlPath

On 09/10/15, Robert Moskowitz wrote: --------------- Quoted text ------------------ SSh is not parsing the port the way http does, it seems: $ rsync -ah --stats root at 192.168.129.2:613:/etc/dhcp/ /home/rgm/data/htt/httnet/homebase/new/dhcp ssh: connect to host 192.168.129.2 port 22: No route to host rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error:

On 9/11/2015 10:34 AM, Robert Moskowitz wrote: > > > On 09/11/2015 10:21 AM, C Linus Hicks wrote: >> On 09/10/15, Robert Moskowitz wrote: >> >> --------------- Quoted text ------------------ >> SSh is not parsing the port the way http does, it seems: >> >> $ rsync -ah --stats root at 192.168.129.2:613:/etc/dhcp/ >>

TL;DR: I expect ProxyCommand to have effect in preference to ControlPath. I've just tripped over this one. I have an ssh Host (let us call it "MAIN") with a ControlPath and with ControlMaster=no, from the .ssh/config file. I also have a shell script whose purpose is to hop to a remote host through a port forward, which uses the ProxyCommand option like this: ProxyCommand ssh

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/

On Thu, 10 Sep 2015 22:50:47 -0400 Robert Moskowitz wrote: > > That will use the default port on the remote host, you can override > > that without specifying the -e if required using -p <port>. > > > $ rsync -ah --stats --delete -p 613 root at 192.168.129.2:/etc/dhcp/ > /home/rgm/data/htt/httnet/homebase/new/dhcp > Unexpected remote arg: root at

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

Hi, I posted this question to the OpenBSD bugs list last week, however I have had no reply and it was suggested on IRC that I post here instead. So I must apologise if this is not appropriate. For a reference here is my previous post: https://marc.info/?l=openbsd-bugs&m=156080681530337&w=2 I am running OpenBSD 6.5-stable (also tested on -current). When I ssh somewhere I get a sig abort

https://bugzilla.mindrot.org/show_bug.cgi?id=2621 Bug ID: 2621 Summary: ControlMaster started by scp (non-ssh?) doesn't forward agent Product: Portable OpenSSH Version: 7.3p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: Miscellaneous

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

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:

It has always bugged me that if I want to use a shell and perform some file transfers in a single host I have to take two SSH connections: one for the shell via ssh(1) and one for the file transfer via sftp(1). Some graphical SSH clients can perform sftp operations and ssh shell access in a single connection by using SSH2 protocol's support for multiple channels. So I hacked my openssh client

Packing the data in TERM is a great idea! I?ll see what I can do with that. >> Finally, some administrative notes: I wasn't able to sign up for this >> mailing list at >> https://lists.mindrot.org/mailman/subscribe/openssh-unix-dev because >> attempts to do so were met by a "Bug in Mailman version 2.1.39" page. > > I just tried that and didn't get

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

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