From owner-freebsd-current Sun Jun 18 08:11:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA15277 for current-outgoing; Sun, 18 Jun 1995 08:11:53 -0700 Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA15269 for ; Sun, 18 Jun 1995 08:11:19 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id BAA16697 for freebsd-current@freebsd.org; Mon, 19 Jun 1995 01:10:57 +1000 From: michael butler Message-Id: <199506181510.BAA16697@asstdc.scgt.oz.au> Subject: Re: GENERIC kernel & some basic UNIX pointers (fwd) To: freebsd-current@freebsd.org Date: Mon, 19 Jun 1995 01:10:56 +1000 (EST) X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 790 Sender: current-owner@freebsd.org Precedence: bulk Jordan K. Hubbard writes: > predictor-1 compression is so far superior to what's provided by > pppd that I can't see any reason to use anything else now. One reason that it can't be used in some instances is that it currently provides no mechanism (that I've found) with which to disable ip-address negotiation. Specific examples which will always fail are connections to a box running any KA9Q variant (there are lots) and a Telebit NetBlazer. The latter component that this machine talks to is configured to reject any negotiation .. I do not know if that can be changed. In both instances, the user-mode ppp apparently decides that it can't confirm the address used by the other end and drops the connection on the floor. In contrast, "pppd -ip .." works every time, michael