From owner-freebsd-questions Wed Nov 19 21:48:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA10829 for questions-outgoing; Wed, 19 Nov 1997 21:48:13 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from scorpion.aracnet.com (root@scorpion.aracnet.com [205.159.88.23]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA10823 for ; Wed, 19 Nov 1997 21:48:09 -0800 (PST) (envelope-from bjj@aracnet.com) Received: from shelob.aracnet.com (bjj@shelob.aracnet.com [205.159.88.2]) by scorpion.aracnet.com (8.8.5/8.8.5) with ESMTP id VAA13688 for ; Wed, 19 Nov 1997 21:48:07 -0800 From: Ben Jackson Received: by shelob.aracnet.com (8.8.5) id VAA08060; Wed, 19 Nov 1997 21:48:05 -0800 Message-Id: <199711200548.VAA08060@shelob.aracnet.com> Subject: upgrade from 2.2-960801-SNAP to 2.2.5-REL, user ppp neg problem To: freebsd-questions@freebsd.org Date: Wed, 19 Nov 1997 21:48:05 -0800 (PST) Content-Type: text Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just upgraded from 2.2-960801-SNAP to 2.2.5-RELEASE (and wow is my Adaptec 2940 muuuch happer!). I've run into a snag with the user PPP stuff (/usr/sbin/ppp)... Using the same config files, the new ppp will get stuck in LCP negotiation forever after I connect to my ISP. No amount of logging (via set log +...) reveals what the negotiations are stuck on. The old ppp binary (from the SNAP) connects fine. Is there any way I can tell why the negotiation is never completing? --Ben