From owner-freebsd-current Thu May 20 21:25:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id E332F14ECA for ; Thu, 20 May 1999 21:25:10 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA10853; Fri, 21 May 1999 14:25:07 +1000 Date: Fri, 21 May 1999 14:25:07 +1000 From: Bruce Evans Message-Id: <199905210425.OAA10853@godzilla.zeta.org.au> To: current@FreeBSD.ORG, sobomax@altavista.net Subject: Re: Plip almost unusable :( Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Is anybody have experience with plip usage on -current? For me it seems >broken - generally it works, but when I trying to make more or less >massive transfer (1-2 MB is sufficient for most cases) any of two system > >dying in panic. Also "ping -f -s 8000 "š kills remote or >local host in several seconds :( This is normal if you don't use the current workaround of configuring ppp. New-bus broke the previous workarounds of configuring slip or putting ppbus in device class "net". I haven't checked that configuring ppp actually helps for plip. The workaround provided by configuring slip was slightly stronger. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message