From owner-freebsd-isp  Tue Jan 28 10:21:01 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA29397
          for isp-outgoing; Tue, 28 Jan 1997 10:21:01 -0800 (PST)
Received: from saguaro.flyingfox.com (saguaro.flyingfox.com [204.188.109.253])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA29386
          for <freebsd-isp@freebsd.org>; Tue, 28 Jan 1997 10:20:58 -0800 (PST)
Received: (from jas@localhost) by saguaro.flyingfox.com (8.6.12/8.6.10) id KAA15672; Tue, 28 Jan 1997 10:16:29 -0800
Date: Tue, 28 Jan 1997 10:16:29 -0800
From: Jim Shankland <jas@flyingfox.COM>
Message-Id: <199701281816.KAA15672@saguaro.flyingfox.com>
To: freebsd-isp@freebsd.org, robert@nanguo.chalmers.com.au
Subject: Re:  annex may be the culprit!
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> So it seems that the Annex may be the culprit in my long
> standing connection woes.!!! bummer dude. Can't see anything
> else in the stream, and I haven't got a hope of translating
> anything I see in tcpdump.  I like the line (You will find
> tcpdump most useful) in the man page. Really!  Need a short
> course in it I think.

I know you checked to see if the TCP extensions were the problem.
Have you checked for buggy V-J compression code on either the
Annex or whoever it's talking to?  I.e., try turning off V-J
compression on the Annex, and see if things improve.

Jim Shankland
Flying Fox Computer Systems, Inc.