From owner-freebsd-questions Wed Dec 5 23:50:11 2001 Delivered-To: freebsd-questions@freebsd.org Received: from web20008.mail.yahoo.com (web20008.mail.yahoo.com [216.136.225.71]) by hub.freebsd.org (Postfix) with SMTP id 43FBB37B41C for ; Wed, 5 Dec 2001 23:50:02 -0800 (PST) Message-ID: <20011206075002.78882.qmail@web20008.mail.yahoo.com> Received: from [61.223.5.161] by web20008.mail.yahoo.com via HTTP; Wed, 05 Dec 2001 23:50:02 PST Date: Wed, 5 Dec 2001 23:50:02 -0800 (PST) From: Vincent Chen Subject: PPTP encryption problem? To: freebsd-questions@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dear all, I still have problem on PPTP encryption and ng_mppd won't loaded when there are incoming connection. Here is session log, please give me your advice. Thanks, [pptp] LCP: authorization successful [pptp] LCP: phase shift AUTHENTICATE --> NETWORK [pptp] up: 1 link, total bandwidth 64000 bps [pptp] IPCP: Up event [pptp] IPCP: state change Starting --> Req-Sent [pptp] IPCP: SendConfigReq #2 IPADDR 10.1.2.1 [pptp] CCP: Open event [pptp] CCP: state change Initial --> Starting [pptp] CCP: LayerStart [pptp] CCP: Up event [pptp] CCP: state change Starting --> Req-Sent [pptp] CCP: SendConfigReq #3 MPPC 0x01000060: MPPE, 40 bit, 128 bit, stateless [pptp] CCP: rec'd Configure Request #4 link 0 (Req-Sent) MPPC 0x010000f1: MPPC MPPE, 40 bit, 128 bit, stateless [pptp] CCP: SendConfigRej #4 MPPC 0x010000f1: MPPC MPPE, 40 bit, 128 bit, stateless [pptp] IPCP: rec'd Configure Request #5 link 0 (Req-Sent) IPADDR 0.0.0.0 NAKing with 10.1.2.251 PRIDNS 0.0.0.0 NAKing with 10.1.2.1 PRINBNS 0.0.0.0 NAKing with 10.1.2.1 SECDNS 0.0.0.0 SECNBNS 0.0.0.0 [pptp] IPCP: SendConfigRej #5 SECDNS 0.0.0.0 SECNBNS 0.0.0.0 [pptp] IPCP: rec'd Configure Ack #2 link 0 (Req-Sent) IPADDR 10.1.2.1 [pptp] IPCP: state change Req-Sent --> Ack-Rcvd pptp0-0: ignoring SetLinkInfo [pptp] CCP: rec'd Configure Nak #3 link 0 (Req-Sent) MPPC 0x01000040: MPPE, 128 bit, stateless [pptp] CCP: SendConfigReq #4 MPPC 0x01000040: MPPE, 128 bit, stateless [pptp] LCP: rec'd Terminate Request #6 link 0 (Opened) [pptp] LCP: state change Opened --> Stopping [pptp] LCP: phase shift NETWORK --> TERMINATE [pptp] up: 0 links, total bandwidth 9600 bps [pptp] IPCP: Down event [pptp] IPCP: state change Ack-Rcvd --> Starting [pptp] CCP: Down event [pptp] CCP: state change Req-Sent --> Starting [pptp] CCP: Close event [pptp] CCP: state change Starting --> Initial [pptp] CCP: LayerFinish [pptp] LCP: SendTerminateAck #5 [pptp] LCP: LayerDown [pptp] LCP: rec'd Terminate Request #7 link 0 (Stopping) [pptp] LCP: SendTerminateAck #6 [pptp] LCP: state change Stopping --> Stopped [pptp] LCP: phase shift TERMINATE --> ESTABLISH [pptp] LCP: LayerFinish [pptp] device: CLOSE event in state UP pptp0-0: clearing call pptp0-0: killing channel [pptp] PPTP call terminated [pptp] IFACE: Close event [pptp] IPCP: Close event [pptp] IPCP: state change Starting --> Initial [pptp] IPCP: LayerFinish [pptp] IFACE: Close event pptp0: closing connection with 10.1.2.5:1963 [pptp] IFACE: Close event [pptp] device is now in state CLOSING [pptp] bundle: CLOSE event in state OPENED [pptp] closing link "pptp"... [pptp] device: DOWN event in state CLOSING [pptp] device is now in state DOWN pptp0: invalid length 16 for type 4 pptp0: killing connection with 10.1.2.5:1963 [pptp] link: CLOSE event [pptp] LCP: Close event [pptp] LCP: state change Stopped --> Closed [pptp] device: DOWN event in state DOWN [pptp] device is now in state DOWN [pptp] link: DOWN event [pptp] LCP: Down event [pptp] LCP: state change Closed --> Initial [pptp] LCP: phase shift ESTABLISH --> DEAD [pptp] link: DOWN event [pptp] LCP: Down event __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message