From owner-freebsd-stable  Mon Jun 19 11:15:26 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mercury.spvi.com (h194.spvi.com [208.150.70.194])
	by hub.freebsd.org (Postfix) with ESMTP
	id AC66F37BEC4; Mon, 19 Jun 2000 11:15:18 -0700 (PDT)
	(envelope-from steve@spvi.com)
Received: (from steve@localhost)
	by mercury.spvi.com (8.9.3/8.9.3) id NAA31747;
	Mon, 19 Jun 2000 13:14:45 -0500 (EST)
	(envelope-from steve@spvi.com)
Date: Mon, 19 Jun 2000 13:14:45 -0500 (EST)
Message-Id: <200006191814.NAA31747@mercury.spvi.com>
X-Authentication-Warning: mercury.spvi.com: steve set sender to steve@spvi.com using -f
From: Steve Spicklemire <steve@spvi.com>
To: freebsd-stable@FreeBSD.ORG, freebsd-net@FreeBSD.ORG
Cc: steve@spvi.com
Subject: mpd problems..... is it possible my cvsup can be 'undone?'
Reply-To: steve@spvi.com
References:  <Pine.BSF.4.21.0006191243010.7428-100000@discover.siteplus.net>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Hi Folks,

   I haven't seen any answers yet... maybe I'm barking up the
wrong three here. I had mpd/pptp working. Now I'm getting all these

Jun 18 17:25:20 mercury mpd: [pptp] CCP: state change Ack-Sent --> Opened 
Jun 18 17:25:20 mercury mpd: [pptp] CCP: LayerUp 
Jun 18 17:25:20 mercury mpd: [pptp] can't create mppc node: Device not configured 
Jun 18 17:25:20 mercury mpd: [pptp] CCP: parameter negotiation failed 
Jun 18 17:25:20 mercury mpd: [pptp] CCP: Close event 
Jun 18 17:25:20 mercury mpd: [pptp] CCP: state change Opened --> Closing 
Jun 18 17:25:20 mercury mpd: [pptp] CCP: SendTerminateReq #4 
Jun 18 17:25:20 mercury mpd: [pptp] CCP: LayerDown 
Jun 18 17:25:20 mercury mpd: [pptp] CCP: state change Closing --> Closed 
Jun 18 17:25:20 mercury mpd: [pptp] CCP: LayerFinish 
Jun 18 17:25:20 mercury mpd: [pptp] CCP: rec'd Terminate Ack #4 link 0 (Closed) 
Jun 18 17:25:21 mercury mpd: [pptp] rec'd unexpected protocol COMPD on link 0 
Jun 18 17:25:25 mercury last message repeated 13 times
Jun 18 17:37:07 mercury mpd: [pptp] rec'd unexpected protocol COMPD on link 0 
Jun 18 17:37:11 mercury last message repeated 3 times

I'm wondering if my cvsup/make world has broken it. Is there any "simple"
way to do a cvsup with the "cvs update '-D'" option? (I just checked the cvsup
man page and -D doesn't mean the same thing there!) I'd like to 

cvsup 'as it was on May 29'. Or something to that effect... alternatively
has anything happened to the crypto stuff, or netgraph that would
explain all these "rec'd unexpected protocol COMPD on link 0" messages
that I'm getting?

thanks! 
-steve


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message