Bug #2102
closedPPTP VPN does not work - LCP: parameter negotiation failed
0%
Description
We are using a pfSense 2.0.1 on a cable line.
One IP is directly on WAN, a /28-subnet is routed to DMZ for use with VMs.
When connecting via PPTP, the error "LCP: parameter negotiation failed" occurs.
We are connecting to the single WAN IP (tried the DMZ IP too).
Tried Windows 7, XP, Mac OS X and iOS from 3 different internet lines as clients - only this VPN doesn't work, others do.
Another PPTP-VPN on the DMZ has been tested successfully - disabling this one didn't help either.
Some others have already confirmed this bug:
http://forum.pfsense.org/index.php/topic,44028.msg228384.htm
This is the log:
Dec 22 14:18:19 pptps: pptp0: killing connection with 140.0.0.144 59491 Dec 22 14:18:19 pptps: pptp0: no reply to StopCtrlConnRequest after 3 sec Dec 22 14:18:16 pptps: pptp0: closing connection with 140.0.0.144 59491 Dec 22 14:18:16 pptps: [pt0] LCP: state change Closed --> Initial Dec 22 14:18:16 pptps: [pt0] LCP: Down event Dec 22 14:18:16 pptps: [pt0] LCP: state change Stopped --> Closed Dec 22 14:18:16 pptps: [pt0] LCP: Close event Dec 22 14:18:16 pptps: [pt0] link: DOWN event Dec 22 14:18:16 pptps: [pt0] PPTP call terminated Dec 22 14:18:16 pptps: pptp0-0: killing channel Dec 22 14:18:16 pptps: pptp0-0: clearing call Dec 22 14:18:16 pptps: [pt0] LCP: LayerFinish Dec 22 14:18:16 pptps: [pt0] LCP: state change Req-Sent --> Stopped Dec 22 14:18:16 pptps: [pt0] LCP: parameter negotiation failed Dec 22 14:18:14 pptps: ENDPOINTDISC [802.1] 00 0d b9 24 d8 08 Dec 22 14:18:14 pptps: MP SHORTSEQ Dec 22 14:18:14 pptps: MP MRRU 1600 Dec 22 14:18:14 pptps: AUTHPROTO CHAP MSOFTv2 Dec 22 14:18:14 pptps: MAGICNUM 2a1ca6a7 Dec 22 14:18:14 pptps: MRU 1500 Dec 22 14:18:14 pptps: PROTOCOMP Dec 22 14:18:14 pptps: ACFCOMP Dec 22 14:18:14 pptps: [pt0] LCP: SendConfigReq #161 Dec 22 14:18:12 pptps: ENDPOINTDISC [802.1] 00 0d b9 24 d8 08 Dec 22 14:18:12 pptps: MP SHORTSEQ Dec 22 14:18:12 pptps: MP MRRU 1600 Dec 22 14:18:12 pptps: AUTHPROTO CHAP MSOFTv2 Dec 22 14:18:12 pptps: MAGICNUM 2a1ca6a7 Dec 22 14:18:12 pptps: MRU 1500 Dec 22 14:18:12 pptps: PROTOCOMP Dec 22 14:18:12 pptps: ACFCOMP Dec 22 14:18:12 pptps: [pt0] LCP: SendConfigReq #160 Dec 22 14:18:10 pptps: ENDPOINTDISC [802.1] 00 0d b9 24 d8 08 Dec 22 14:18:10 pptps: MP SHORTSEQ Dec 22 14:18:10 pptps: MP MRRU 1600 Dec 22 14:18:10 pptps: AUTHPROTO CHAP MSOFTv2 Dec 22 14:18:10 pptps: MAGICNUM 2a1ca6a7 Dec 22 14:18:10 pptps: MRU 1500 Dec 22 14:18:10 pptps: PROTOCOMP Dec 22 14:18:10 pptps: ACFCOMP Dec 22 14:18:10 pptps: [pt0] LCP: SendConfigReq #159 Dec 22 14:18:08 pptps: ENDPOINTDISC [802.1] 00 0d b9 24 d8 08 Dec 22 14:18:08 pptps: MP SHORTSEQ Dec 22 14:18:08 pptps: MP MRRU 1600 Dec 22 14:18:08 pptps: AUTHPROTO CHAP MSOFTv2 Dec 22 14:18:08 pptps: MAGICNUM 2a1ca6a7 Dec 22 14:18:08 pptps: MRU 1500 Dec 22 14:18:08 pptps: PROTOCOMP Dec 22 14:18:08 pptps: ACFCOMP Dec 22 14:18:08 pptps: [pt0] LCP: SendConfigReq #158 Dec 22 14:18:06 pptps: ENDPOINTDISC [802.1] 00 0d b9 24 d8 08 Dec 22 14:18:06 pptps: MP SHORTSEQ Dec 22 14:18:06 pptps: MP MRRU 1600 Dec 22 14:18:06 pptps: AUTHPROTO CHAP MSOFTv2 Dec 22 14:18:06 pptps: MAGICNUM 2a1ca6a7 Dec 22 14:18:06 pptps: MRU 1500 Dec 22 14:18:06 pptps: PROTOCOMP Dec 22 14:18:06 pptps: ACFCOMP Dec 22 14:18:06 pptps: [pt0] LCP: SendConfigReq #157 Dec 22 14:18:04 pptps: ENDPOINTDISC [802.1] 00 0d b9 24 d8 08 Dec 22 14:18:04 pptps: MP SHORTSEQ Dec 22 14:18:04 pptps: MP MRRU 1600 Dec 22 14:18:04 pptps: AUTHPROTO CHAP MSOFTv2 Dec 22 14:18:04 pptps: MAGICNUM 2a1ca6a7 Dec 22 14:18:04 pptps: MRU 1500 Dec 22 14:18:04 pptps: PROTOCOMP Dec 22 14:18:04 pptps: ACFCOMP Dec 22 14:18:04 pptps: [pt0] LCP: SendConfigReq #156 Dec 22 14:18:02 pptps: ENDPOINTDISC [802.1] 00 0d b9 24 d8 08 Dec 22 14:18:02 pptps: MP SHORTSEQ Dec 22 14:18:02 pptps: MP MRRU 1600 Dec 22 14:18:02 pptps: AUTHPROTO CHAP MSOFTv2 Dec 22 14:18:02 pptps: MAGICNUM 2a1ca6a7 Dec 22 14:18:02 pptps: MRU 1500 Dec 22 14:18:02 pptps: PROTOCOMP Dec 22 14:18:02 pptps: ACFCOMP Dec 22 14:18:02 pptps: [pt0] LCP: SendConfigReq #155 Dec 22 14:18:00 pptps: ENDPOINTDISC [802.1] 00 0d b9 24 d8 08 Dec 22 14:18:00 pptps: MP SHORTSEQ Dec 22 14:18:00 pptps: MP MRRU 1600 Dec 22 14:18:00 pptps: AUTHPROTO CHAP MSOFTv2 Dec 22 14:18:00 pptps: MAGICNUM 2a1ca6a7 Dec 22 14:18:00 pptps: MRU 1500 Dec 22 14:18:00 pptps: PROTOCOMP Dec 22 14:18:00 pptps: ACFCOMP Dec 22 14:18:00 pptps: [pt0] LCP: SendConfigReq #154 Dec 22 14:17:58 pptps: ENDPOINTDISC [802.1] 00 0d b9 24 d8 08 Dec 22 14:17:58 pptps: MP SHORTSEQ Dec 22 14:17:58 pptps: MP MRRU 1600 Dec 22 14:17:58 pptps: AUTHPROTO CHAP MSOFTv2 Dec 22 14:17:58 pptps: MAGICNUM 2a1ca6a7 Dec 22 14:17:58 pptps: MRU 1500 Dec 22 14:17:58 pptps: PROTOCOMP Dec 22 14:17:58 pptps: ACFCOMP Dec 22 14:17:58 pptps: [pt0] LCP: SendConfigReq #153 Dec 22 14:17:56 pptps: ENDPOINTDISC [802.1] 00 0d b9 24 d8 08 Dec 22 14:17:56 pptps: MP SHORTSEQ Dec 22 14:17:56 pptps: MP MRRU 1600 Dec 22 14:17:56 pptps: AUTHPROTO CHAP MSOFTv2 Dec 22 14:17:56 pptps: MAGICNUM 2a1ca6a7 Dec 22 14:17:56 pptps: MRU 1500 Dec 22 14:17:56 pptps: PROTOCOMP Dec 22 14:17:56 pptps: ACFCOMP Dec 22 14:17:56 pptps: [pt0] LCP: SendConfigReq #152 Dec 22 14:17:56 pptps: [pt0] LCP: state change Starting --> Req-Sent Dec 22 14:17:56 pptps: [pt0] LCP: Up event Dec 22 14:17:56 pptps: [pt0] link: origination is remote Dec 22 14:17:56 pptps: [pt0] link: UP event Dec 22 14:17:56 pptps: [pt0] PPTP: attaching to peer's outgoing call Dec 22 14:17:56 pptps: [pt0] LCP: LayerStart Dec 22 14:17:56 pptps: [pt0] LCP: state change Initial --> Starting Dec 22 14:17:56 pptps: [pt0] LCP: Open event Dec 22 14:17:56 pptps: [pt0] link: OPEN event Dec 22 14:17:56 pptps: [pt0] opening link "pt0"... Dec 22 14:17:56 pptps: [pt0] Accepting PPTP connection Dec 22 14:17:56 pptps: pptp0: attached to connection with 140.0.0.144 59491 Dec 22 14:17:56 pptps: PPTP: Incoming control connection from 140.0.0.144 59491 to 213.0.0.9 1723
Updated by Chris Buechler over 13 years ago
- Status changed from New to Rejected
not a bug, that's a general problem with connectivity generally
Updated by Christoph Filnkößl over 13 years ago
I dont think so. In the forum others reported that the problem came or disappeared out of nowhere.
Also, other VPNs on the same connection work flawlessly.
Updated by Chris Buechler over 13 years ago
it is. PPTP and GRE connectivity is problematic in many circumstances for many reasons. post to the forum or mailing list for further help.