From owner-freebsd-isp Thu May 15 13:49:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA14147 for isp-outgoing; Thu, 15 May 1997 13:49:04 -0700 (PDT) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA14140 for ; Thu, 15 May 1997 13:49:01 -0700 (PDT) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id NAA17469 for isp@freebsd.org; Thu, 15 May 1997 13:50:05 -0700 (PDT) Date: Thu, 15 May 1997 13:50:05 -0700 (PDT) From: Jim Shankland Message-Id: <199705152050.NAA17469@biggusdiskus.flyingfox.com> To: isp@freebsd.org Subject: Re: interface card to connect 64k..256k to connect to internet Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks to all for the feedback on this; it's been illuminating. My take is that the case for the quad-sync card at an ISP or a corporat headquarters is stronger than that for the single-sync card in a remote-office or ISP-customer setting. Price certainly is a factor, and personally, at $1K for a PCI-based, single-T1 card, I find it a hard sell compared to a Pipeline 130 with an integrated CSU *and* a BRI port for, say, $1300. (And I can't say that I found derisive quote marks around the word "handle" in "handle a T1", or references to brands of automobiles, persuasive.) The FreeBSD box with 1-3 quad-T1 cards, plus a 100 Mb/s Ethernet card, is another story, and looks attractive. Jim Shankland Flying Fox Computer Systems, Inc.