Package: ppp Version: 2.4.2+20040428-6 Severity: normal
When using pppd togehrher with the "kernel-patch-mpppe" package, pppd fails to negotiate encryption parameters for it stops negotaion too early. My log reads: sent [CCP ConfReq id=0x1 <mppe +H -M +S -L -D -C>] rcvd [CCP ConfReq id=0x3 <mppe +H -M -S -L -D +C>] MPPE required but peer negotiation failed sent [LCP TermReq id=0x2 "MPPE required but peer negotiation failed"] sent [CCP ConfRej id=0x3 <mppe +H -M -S -L -D +C>] rcvd [IPCP ConfReq id=0x4 <addr 192.168.1.100>] Discarded non-LCP packet when LCP not open rcvd [CCP ConfAck id=0x1 <mppe +H -M +S -L -D -C>] Discarded non-LCP packet when LCP not open rcvd [LCP TermAck id=0x2 "MPPE required but peer negotiation failed"] Connection terminated. So the PPTP Server asked for a connection without encryption but was willing to agree with encryption, but pppd gave up too early. I've found more Information on this problem here: http://pptpclient.sourceforge.net/howto-diagnosis.phtml#mppe_rbpnf "Solution: you may fix this by (either); 1. using a later version of pppd that is not so pedantic, and will negotiate further to achieve encryption (not sure which version), or..." It seems that the pppd Version used on sarge is too old. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-mppe Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages ppp depends on: ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libpam-modules 0.76-22 Pluggable Authentication Modules f ii libpam-runtime 0.76-22 Runtime support for the PAM librar ii libpam0g 0.76-22 Pluggable Authentication Modules l ii libpcap0.7 0.7.2-7 System interface for user-level pa ii libssl0.9.7 0.9.7e-2 SSL shared libraries ii makedev 2.3.1-75 Creates device files in /dev ii netbase 4.20 Basic TCP/IP networking system ii procps 1:3.2.1-2 The /proc file system utilities -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
