From owner-freebsd-questions Sat Nov 18 14:21:23 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA21460 for questions-outgoing; Sat, 18 Nov 1995 14:21:23 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id OAA21454 for ; Sat, 18 Nov 1995 14:21:19 -0800 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA32112; Sat, 18 Nov 1995 17:19:59 -0500 Date: Sat, 18 Nov 1995 17:19:59 -0500 From: "Garrett A. Wollman" Message-Id: <9511182219.AA32112@halloran-eldar.lcs.mit.edu> To: Tony Harverson Cc: freebsd-questions@freebsd.org Subject: tcp_extensions ? In-Reply-To: <199511160850.KAA00212@hornet.netac.co.za> References: <199511160850.KAA00212@hornet.netac.co.za> Sender: owner-questions@freebsd.org Precedence: bulk < said: > I was wondering if there was a doc on the tcp_extensions sysconfig > setting in 2.0.5... I've been having a problem in that my machine > hangs tcp connections, but not randomly... Only to another freebsd > box that runs 2.0.5 without extensions. (a coupla other boxes have > had the same problem getting hold of it) Exactly what sort of > extensions are disabled, and what is the 'losing hardware' ? The extensions in question are RFC 1323 and RFC 1644. The particular losing hardware that caused a number of people problems was that certain vendors' terminal servers' SLIP implementations would get confused in compression by the presence of unknown TCP options, and cause things to break. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant