From owner-freebsd-hackers  Tue Jan 28 03:47:40 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA09832
          for hackers-outgoing; Tue, 28 Jan 1997 03:47:40 -0800 (PST)
Received: from ravenock.cybercity.dk (ravenock.cybercity.dk [194.16.57.32])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA09824;
          Tue, 28 Jan 1997 03:47:32 -0800 (PST)
Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.4/8.7.3) id MAA17415; Tue, 28 Jan 1997 12:48:53 +0100 (MET)
From: Søren Schmidt <sos@ravenock.cybercity.dk>
Message-Id: <199701281148.MAA17415@ravenock.cybercity.dk>
Subject: Re: progress report on connection problems
In-Reply-To: <199701281002.UAA00874@nanguo.chalmers.com.au> from Robert Chalmers at "Jan 28, 97 08:02:02 pm"
To: robert@nanguo.chalmers.com.au (Robert Chalmers)
Date: Tue, 28 Jan 1997 12:48:44 +0100 (MET)
Cc: freebsd-questions@freebsd.org, freebsd-isp@freebsd.org,
        hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL30 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In reply to Robert Chalmers who wrote:
[lots o descriptions deleted] 
> I can connect to, and be connected to these OSs with no worries. 
> I have tried setting tcp_extensions NO and YES. If set to YES, I am unable
> to ftp to another FBSD site that also has tcp_extensions set YES (on).
> The connection simply 'hung'. If I set rfc1323 to 0 (off) the ftp connection
> worked fine, the other end being (on). The same happened at the other end, 
> when they tried to ftp to me. set tcp_extension on, fail, set it off, fine.
> 
> The only constant is the Annex. However, why does it pass _most_ traffic,
> if it is the fault of the Annex, and only fail on some.? 

Hmm, I'm seeing problems with the Annex's too if I run with tcp_extensions
enabled. Somehow the Annex's turn some of the trafic into "chernobyl" 
packets (ie all lamps and bells set). This is only a problem
if the other end also supports the extensions (ie a FreeBSD box).
However all problems dissapear if I disable the extensions.
I guess the only solution is to bug the vendor to implement a 
modern IP stackc...

> If FreeBSD is
> going to be so fussy about its tcp/ip flow, shouldn't it be reworked.
> The world is still full of less than leading edge hardware! Some of it
> brand new...

Disable the tcp_extentions is the only solution to the problems I'm
seeing as it is not the FreeBSD end that is at fault, and hence I
cannot fix it :(

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt               (sos@FreeBSD.org)               FreeBSD Core Team
                Even more code to hack -- will it ever end
..