From owner-freebsd-hackers Wed Mar 27 07:28:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA03211 for hackers-outgoing; Wed, 27 Mar 1996 07:28:21 -0800 (PST) Received: from psiint.com (vv.psiint.com [204.189.53.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA03180 Wed, 27 Mar 1996 07:28:13 -0800 (PST) Received: by psiint.com (8.6.12/4.03) id HAA65361; Wed, 27 Mar 1996 07:28:12 -0800 Date: Wed, 27 Mar 1996 07:28:12 -0800 (PST) From: Dave Walton To: Brian Litzinger cc: questions@FreeBSD.org, hackers@FreeBSD.org Subject: Re: BitsurfrPro on FBSD 2.1 & MLPPP broken In-Reply-To: <199603270055.QAA09258@MediaCity.Com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 26 Mar 1996, Brian Litzinger wrote: > > I'm using the Bitsurfr Pro with freebsd. Everything is fine except that > > in MLPPP mode, and when I receive files via ftp the bitsurfr resets itself. > > This only happens in the mlppp mode at 128k, it doesn't happen when using > > ppp on 64k. > > Could this be a limitation/problem from the ppp implementation on fbsd? > > It's not. > > > Has anyone experienced such a problem? > > yes. lots of us. > > > Or is my bitsurfr broken? > > yes it is. Even if its running 1E firmware. I'm curious in what way you feel it's broken. I haven't set mine up under FreeBSD yet, but I've never had a problem like this under Win95. That would tend to indicate to me that either only some BitSURFRs are broken (not mine), or the hardware works and it's a software (FreeBSD ppp) problem. Or am I missing something here? Dave ========================================================================== David Walton Unix Programmer PSI INTERNATIONAL, Inc. email: dwalton@psiint.com 190 South Orchard #C200 Fax :(707)451-6484 Vacaville, CA 95688 Phone:(707)451-3503 ==========================================================================