From owner-freebsd-isp  Mon Jan  6 15:05:37 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id PAA08303
          for isp-outgoing; Mon, 6 Jan 1997 15:05:37 -0800 (PST)
Received: from red.jnx.com (red.jnx.com [208.197.169.254])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA08296
          for <isp@freebsd.org>; Mon, 6 Jan 1997 15:05:34 -0800 (PST)
Received: from chimp.jnx.com (chimp.jnx.com [208.197.169.246]) by red.jnx.com (8.8.3/8.8.3) with ESMTP id PAA15907; Mon, 6 Jan 1997 15:05:04 -0800 (PST)
Received: (from tli@localhost) by chimp.jnx.com (8.7.6/8.7.3) id PAA04643; Mon, 6 Jan 1997 15:04:02 -0800 (PST)
Date: Mon, 6 Jan 1997 15:04:02 -0800 (PST)
Message-Id: <199701062304.PAA04643@chimp.jnx.com>
From: Tony Li <tli@jnx.com>
To: dennis@etinc.com
CC: isp@freebsd.org
In-reply-to: <3.0.32.19970106171528.00a807d0@etinc.com> (message from dennis
	on Mon, 06 Jan 1997 17:15:35 -0500)
Subject: Re: FreeBSD as T1 router
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


   My provider could be lying to me...but I doubt it since hes an old
   colleague. 

Doesn't mean he's lying.  Could be that he's just doing something wrong...
Could be a software or hardware problem.  We have no data.

   >Your generalizations are showing.

   And its not a "generalization", its a specific example to illustrate my
   point. The thing pigs out without being near to its published capacity....

Like any other sophisticated technology, it can be misused.  We do know
what a 7000 can do.  What you describe is well below what it can and has
done.  But, given the appropriately broken configuration (e.g., trying to do
X.25 at 4Mbps), well above what the worst case.

   Your bias is showing.

Yes, but a bias for truth is not one that I mind having or showing.  ;-)

Tony