similar to: Rsync connection times out on very large --files-from

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

The attached patch adds an option (off by default to preserve current behavior) to set a timeout on the select() statement that waits for input in clientloop.c. This fixes a timeout issue for me (explained below) and probably also fixes the timeouts mentioned in last month's thread "Idle time out". The patch is also available by http from:

Dear OpenSSH Portable sshd developers, I'm having a problem where sshd login sessions are occasionally (as often as once a day) getting stuck indefinitely. I enabled debug messages and got a backtrace of a stuck sshd, and I think I've found the bug. I wanted to run it by the list once before filing. sshd version: OpenSSH_4.2p1 FreeBSD-20050903, OpenSSL 0.9.7e-p1 25 Oct 2004

Dear All, we are experiencing severe problems with Samba 2.2.0 (with quota support) running on a dual processor (400MHz) Sun E450 running Solaris 2.7. This is used as a central file server for student diskspace, accessed by approx 1200 PCs running NT 4. Up until recently we experienced some, what we assume to be, loading issues with connections during the middle of the day being slow.

Attached is a patch to allow a user to turn on TCP keepalives for port forwarded connections. It's mainly useful when the connections to the ssh listener are coming from many different boxes, some of which crash, leaving the service on the other side of the port forwarder waiting on connections indefinitely. It creates a new option named "KeepAliveForward" to control this behavior.

https://bugzilla.samba.org/show_bug.cgi?id=7757 Summary: with big file, rsync times out out when it should not; the sender is still responsive Product: rsync Version: 3.0.7 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

On Jan 16, 2015, at 11:29 AM, Les Mikesell <lesmikesell at gmail.com> wrote: > On Fri, Jan 16, 2015 at 12:21 PM, Warren Young <wyml at etr-usa.com> wrote: >> >> A different fix is to exploit the real-time nature of video camera imagery > > Normally if you care about knowing if the other end of a connection is > gone you could enable keepalives on the socket

Heya, Most of the windows ssh clients (putty, securecrt) have anti-idle features. They offer either a null packet or protocol no-op or user defined string to be sent over every x seconds. Is this possible or planned with the OpenSSH client? Our draconian firewall admins have started timing out ssh sessions. Yes I'm aware I could hack up a port forwarding dumb traffic process, but was

Hi, The firewall at work doesn't allow me to make a direct SSH connection to the Internet, so I use the ProxyCommand to tunnel SSH through a HTTP proxy. This works fine, except for the fact that the HTTP proxy server closes the connection after 60 seconds of inactivity. Attached below is a patch that implements a new configuration option called "Idle" that lets you specify the

I have attached a patch which adds null packet keepalive functionality to the client. This patch is made against the current CVS tree as of 3/14/01. Please consider this patch for inclusion in the OpenSSH main tree. This patch is based upon and includes code from the Chris Lightfoot (chris at ex-parrot.com) patch posted 2/23. The original patch from Chris is at:

We've recently completed an internal eval of products to server Unix filesystems from our Unix fileservers to our NT clients via SMB. We evaluated two products, one of them was Samba 1.9.18pl10, the other was a commercial product. We've selected Samba. We had been using the commercial product for some time. All is great, fine, dandy. But, as a result of our experience with the

I mentioned this problem in a previous post (in November). This time I'm including a patch. Version: OpenSSH_2.3.0p1 Keywords: setsockopt keepalive hang masquerade interactive Symptom: For protocol 2, socket options (especially keepalive) are not being properly set for OpenSSH_2.3.0p1, even when request in the config files. Furthermore (for either protocol), keepalive is only set for

I've been in discussion with a colleague who had to reduce (!) SO_SNDBUF to get decent performance, and so wrote this little tool. It tells you the system default for most of the settable socket options. It can't do linger, as the value is a struct instead of an int, but that's probably uninteresting to Samba folks. Run this to see what you'd have if you didn't set any

After awhile, my connections from my PC to my samba server end up with a red "X" in them (share disappeared) if I leave my explorer window open. If I click on these, they "wake up" and continue to function (and the red X's go away). If I close my explorer window (while the red X's are there) and reopen it , they are gone. An attempt to reestablish these

On Fri, Jan 16, 2015 at 1:13 PM, Fred Smith <fredex at fcshome.stoneham.ma.us> wrote: >> > >> > Normally if you care about knowing if the other end of a connection is >> > gone you could enable keepalives on the socket >> >> That?s also an appropriate fix, especially when the protocol inherently has long periods of idle time, like SSH. >> >

Hi, we have a samba setup running samba 3.0.10-Debian with a lot of DOS pc's writing to it. Now we have a problem that when one of those pc's is restarted while having a lock, that file stays locked. We already tried changing this behavior by setting the following parameters without effect: - keepalive - SO_KEEPALIVE - deadtime How can we enable a timeout on these locks /

For someone that's network-aware, but hasn't sat down and plowed through umpteen SIP-related RFC's and memorized the standards, is there a good primer on troubleshooting SIP issues? I'm seeing a lot of NOTIFY/603 messages on my network between Asterisk and my Sipura 942's, for instance... Not sure what these are... perhaps the qualify keepalives? In which case, I guess

Hi, I''m looking for suggestions on the simplest way to implement an HTTP proxy under Rails/Mongrel. It should preserve ALL of the proxied HTTP response - including all header content such keepalives, etc. Yes, I know I can do this with Apache''s proxy module, and we already do that for the non-development/test environments. This is just for the development/test environment

Hi, After our upgrade from Samba 3.x to 4.1.6 we are having major performance issues. Today, I've been able to nail it down to a simple test case. What strikes me is that Windows XP takes about 25 seconds for one job, while it only costs 3 seconds on Windows 7. I have two tests: 1000 files of 10k each (total ~10Mb): * Linux on localhost or a remote host (1GE or 10GE): 5.5 seconds *

https://bugzilla.samba.org/show_bug.cgi?id=10312 Summary: Rsync times out during deletion on big folders Product: rsync Version: 3.0.9 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: gabriele at tozzi.eu