From owner-freebsd-isp  Thu Nov 14 11:31:30 1996
Return-Path: owner-isp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA28478
          for isp-outgoing; Thu, 14 Nov 1996 11:31:30 -0800 (PST)
Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA28468
          for <isp@FreeBSD.ORG>; Thu, 14 Nov 1996 11:31:27 -0800 (PST)
Received: from swoosh.dunn.org (swoosh.dunn.org [206.158.7.243]) by ns2.harborcom.net (8.7.6/8.6.12) with SMTP id OAA28591; Thu, 14 Nov 1996 14:31:21 -0500 (EST)
Date: Thu, 14 Nov 1996 14:29:12 -0500 ()
From: Bradley Dunn <bradley@dunn.org>
To: Steve <shovey@buffnet.net>
cc: isp@FreeBSD.ORG
Subject: Re: Decision in Router Purchase
In-Reply-To: <Pine.BSI.3.95.961114085720.17009P-100000@buffnet11.buffnet.net>
Message-ID: <Pine.WNT.3.95.961114142125.-91463C-100000@swoosh.dunn.org>
X-X-Sender: bradley@harborcom.net
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-isp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 14 Nov 1996, Steve wrote:

> Go with the cisco!  There is something just a bit off with freebsd's
> tcp/ip.  I have a subgroup of users who get stalls, if my freebsd's are
> not the other side of my cisco from them.  For instance, if they were to
> pull headers from a new server on the same subnet, the news server being
> freebsd, it would stop.. Same with web pages.

Have you used tcpdump to investigate this? "Something just a bit off"
doesn't mean anything to me.

If putting your FreeBSD boxes behind a router fixes things, then I have a
hard time believing that it is a TCP/IP problem. Remember, routers do
layer 3 switching, which means the problem is most likely at layer 2 or
layer 1.

-BD