From owner-freebsd-isp Thu Nov 14 13:55:07 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA09114 for isp-outgoing; Thu, 14 Nov 1996 13:55:07 -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 NAA09104 for ; Thu, 14 Nov 1996 13:55:03 -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 QAA23841; Thu, 14 Nov 1996 16:54:29 -0500 (EST) Date: Thu, 14 Nov 1996 16:52:19 -0500 () From: Bradley Dunn To: Steve cc: isp@FreeBSD.ORG Subject: Re: Decision in Router Purchase In-Reply-To: Message-ID: 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: > I could come to no other resolution than to put them on the other side of > a router. The problem did not exist with all 'dialers in' - just a > subset, but a subset with no connecting features other than that they used > PPP. > > I dont experience the problem with linux boxes or the SCO's (I have > both) - Just the freebsd's later than version 2.0 (it was not until 2.0.5 > that the problem arose) with or without the extensions enabled. > > I know that to get it fixed I would have to become a low level freebsd > tcp/ip expert, find and fix it myself at the source level. I dont have > the time for that. So it might annoy you, but I found it very annoying to > spend a week trouble shooting 3 web servers, and another week trouble > shooting an identicle problem with a news server, only because I had > switched to freebsd on them - and then could only resolve it by putting > them the other side of a cisco - because Im crasy and BSD is perfect. There is a door. Everytime you walk through that door, you hit your head. You discover that by separating your head from your body, you no longer hit your head when you go through the door. Was the problem solved? Yes. Was the correct cause indenified? No. You don't want to use FreeBSD, fine. Just don't claim it's broken because you don't want to do the work to find out what the real problem is. -BD