From owner-freebsd-net Tue Aug 10 15: 9:50 1999 Delivered-To: freebsd-net@freebsd.org Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (Postfix) with ESMTP id 16F3314D41 for ; Tue, 10 Aug 1999 15:09:46 -0700 (PDT) (envelope-from kwc@world.std.com) Received: from world.std.com (root@world-f.std.com [199.172.62.5]) by europe.std.com (8.9.3/8.9.3) with SMTP id SAA15046 for ; Tue, 10 Aug 1999 18:09:37 -0400 (EDT) Received: by world.std.com (TheWorld/Spike-2.0) id AA20326; Tue, 10 Aug 1999 18:08:38 -0400 Date: Tue, 10 Aug 1999 18:08:38 -0400 From: kwc@world.std.com (Kenneth W Cochran) Message-Id: <199908102208.AA20326@world.std.com> To: freebsd-net@freebsd.org Subject: Kernel ppp (pppd) newer than ver 2.3.5 in -STABLE Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -STABLE Subject: Kernel ppp (pppd) version 2.3.5 --> 2.3.8 (Slightly edited from original sent to -stable...) What is the "status" of pppd more recent than 2.3.5 (2.3.8, for example) making it into -STABLE (RELENG_3)? I've also noticed a 2.3.9 rev now in beta. Not a show-stopper, but I get a strange "received bad configure-nak/rej" (at LOG_ERR level while trying to negotiate CCP) every time I connect. I do not get this behavior under Linux (Slackware 4.0/kernel 2.2.10/pppd-2.3.7) & I don't recall getting it under Linux with previous versions of pppd going back as far as 2.3.5 & 2.2.0f. IIRC the Linux version "properly" rejects the CCP negotiation(s) it doesn't like... :) According to the pppd-2.3.8 sources, it has been updated for FreeBSD 3.0 (& 3.1?). I suppose I could install it "manually" but I'm not (yet) keen on messing with the source tree, especially that of the kernel (ie. I don't want to mess-up the cvsup procedure). It also appears that there are differences between the kernel portions in the kernel source tree & those in pppd-2.3.8 (some are "older," some "newer"). Interesting... Is this worth filing a pr? Thanks, -kc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message