From owner-freebsd-hackers Sat May 2 08:46:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10379 for freebsd-hackers-outgoing; Sat, 2 May 1998 08:46:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10370 for ; Sat, 2 May 1998 08:46:41 -0700 (PDT) (envelope-from mike@ns1.seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with SMTP id LAA07378; Sat, 2 May 1998 11:45:36 -0400 (EDT) Date: Sat, 2 May 1998 11:45:36 -0400 (EDT) From: Mike To: Luoqi Chen cc: benedict@echonyc.com, spork@super-g.com, hackers@FreeBSD.ORG, jlp@Part.NET Subject: Re: odd network problem In-Reply-To: <9805012325.AA22110@watermarkgroup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 1 May 1998, Luoqi Chen wrote: > USR boxes have their own problems. For one, they couldn't handle VJ > compression correctly. That's true... we just spent $300,000 on POP upgrades (taking a few sites to the new Enterprise Network Hubs with PRI interfaces - gotta be 100% digital on our end or the customers throw fits, ya know ;). There were more installation and initial problems than I wanted to see considering what we paid for the boxes, but overall the products (and the support you get from 3com) have made be pretty happy (so far, knock on wood). I'm curious as to whether the 'port 5000' issue described in AntiOnline's I/O (http://www.antionline.com/io/issue2/4.html) is due to a misconfiguration on the administrator's part of it it's just standard behavior on Annex boxes. Mike Hoskins SEI Data Network Services, Inc. noc@seidata.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message