Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 160705 - Heartbeat/Watchdog Patch for OpenSSH (RFE)
Summary: Heartbeat/Watchdog Patch for OpenSSH (RFE)
Alias: None
Product: Fedora
Classification: Fedora
Component: openssh
Version: 4
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2005-06-16 19:37 UTC by Pete Toscano
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2005-06-16 20:04:54 UTC

Attachments (Terms of Use)

Description Pete Toscano 2005-06-16 19:37:47 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Epiphany/1.6.1

Description of problem:
It'd be great to apply the patch from this site to the FC4 openssh packages:

I'm constantly having longer-running ssh sessions through a NAT firewall dropped due to inactivity.  With this patch, the problem disappears.  I don't know why some (pre-patched) ssh sessions through NATs stay up indefinately while others don't, but this problem fixes that problem.

It's an easy patch to apply.  I'll include my spec file.  The tgz with the patch file is available at the above link.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Ssh to a box on the other side of a Checkpoint firewall.
2. Wait a couple hours.

Actual Results:  Session disappears due to inactivity.

Expected Results:  It should stay up until I exit the session.

Additional info:

Comment 1 Tomas Mraz 2005-06-16 20:04:54 UTC
You can set ServerAliveInterval in ssh_config and ClientAliveInterval in
sshd_config already.

These options apply to protocol 2 only but the protocol 1 shouldn't be normally
used anyway.

Note You need to log in before you can comment on or make changes to this bug.