Bug 8016 – telnet disconnect over GWAN after approximately 2 hours of inactivity

Bug 8016 - telnet disconnect over GWAN after approximately 2 hours of inactivity

Summary:	telnet disconnect over GWAN after approximately 2 hours of inactivity

Status:	CLOSED DEFERRED

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	telnet (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Florian La Roche
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-12-27 15:42 EST by Ralph Tietje
Modified:	2008-05-01 11:37 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-02-03 17:54:55 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Ralph Tietje 1999-12-27 15:42:12 EST

Machine A: PC running Linux 6.1 in NY
Machine B: Sun running Solaris 2.6 in NY
Machine C: Sun running Solaris 2.6 in San Francisco

Open a telnet session between A -> C, B -> C. The session between
A -> C will get disconnected after aproximately 2 hours of inactivity
with a "connection closed by remote host message". The connection
between B -> C will remain active. I think there is T1 between the
sites.

Comment 1 Riley H Williams 1999-12-28 13:37:59 EST

Sounds like system (C) has an idle timeout configured and system (B) doesn't.
The obvious test is to see what happens if, after telnet to (B), you telnet from
there to (C) and leave it idle - does that time out as well?

Comment 2 Elliot Lee 2000-02-03 17:54:59 EST

This problem could be attributed to any number of causes - network problems,
idle timeouts, etc. I haven't ever seen this problem myself, so I think it's
safe to call it a fluke.

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