From owner-freebsd-isp Thu Nov 14 10:23:57 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA23563 for isp-outgoing; Thu, 14 Nov 1996 10:23:57 -0800 (PST) Received: from saguaro.flyingfox.com (saguaro.flyingfox.com [204.188.109.253]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA23553 for ; Thu, 14 Nov 1996 10:23:27 -0800 (PST) Received: (from jas@localhost) by saguaro.flyingfox.com (8.6.12/8.6.10) id KAA17779; Thu, 14 Nov 1996 10:20:32 -0800 Date: Thu, 14 Nov 1996 10:20:32 -0800 From: Jim Shankland Message-Id: <199611141820.KAA17779@saguaro.flyingfox.com> To: richardc@csua.berkeley.edu, shovey@buffnet.net Subject: Re: Decision in Router Purchase Cc: isp@freebsd.org Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Steve writes: > 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. I find this annoying. I'm sure you were having problems, and that interposing a Cisco between your users and your FreeBSD servers made the problem go away; but realize that "something [being] just a bit off with FreeBSD's tcp/ip" is not the only, nor indeed the most likely, explanation of the things you observed. Did you make any effort to investigate the problem (e.g., packet traces)? Did you report the problem? Or did you just try something (interposing the Cisco) and find that the problem went away? If so, fair enough; everybody's busy. But then you can't draw conclusions about what was wrong in the first place. Jim Shankland Flying Fox Computer Systems, Inc.