Your message dated Sat, 19 Feb 2005 13:39:45 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#295972: mppe negotiation fails due to bug in pppd
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 19 Feb 2005 12:21:24 +0000
>From [EMAIL PROTECTED] Sat Feb 19 04:21:24 2005
Return-path: <[EMAIL PROTECTED]>
Received: from ger7.wwwserver.net [212.114.35.2]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D2Tbv-00060y-00; Sat, 19 Feb 2005 04:21:23 -0800
Received: from localhost.localdomain (pD9E4B916.dip.t-dialin.net
[217.228.185.22])
(authenticated (0 bits))
by ger7.wwwserver.net (8.12.10/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP
id j1JCLNaF027291;
Sat, 19 Feb 2005 13:21:23 +0100
Apparently-To: [EMAIL PROTECTED]
Received: from herd by localhost.localdomain with local (Exim 4.34)
id 1D2Tcj-0001Ki-Va; Sat, 19 Feb 2005 13:22:13 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Bernd Herd <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: mppe negotiation fails due to bug in pppd
X-Mailer: reportbug 3.2
Date: Sat, 19 Feb 2005 13:22:13 +0100
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
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
---------------------------------------
Received: (at 295972-done) by bugs.debian.org; 19 Feb 2005 12:39:57 +0000
>From [EMAIL PROTECTED] Sat Feb 19 04:39:57 2005
Return-path: <[EMAIL PROTECTED]>
Received: from attila.bofh.it [213.92.8.2] (postfix)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D2Tts-0003fj-00; Sat, 19 Feb 2005 04:39:56 -0800
Received: by attila.bofh.it (Postfix, from userid 10)
id D180D5F7AA; Sat, 19 Feb 2005 13:39:52 +0100 (CET)
Received: by wonderland.linux.it (Postfix, from userid 1001)
id 763A81C15B; Sat, 19 Feb 2005 13:39:45 +0100 (CET)
Date: Sat, 19 Feb 2005 13:39:45 +0100
To: Bernd Herd <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#295972: mppe negotiation fails due to bug in pppd
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="liOOAslEiF7prFVr"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.6+20040907i
From: [EMAIL PROTECTED] (Marco d'Itri)
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
--liOOAslEiF7prFVr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Feb 19, Bernd Herd <[EMAIL PROTECTED]> wrote:
> It seems that the pppd Version used on sarge is too old.
And there is already another bug open about this, with an explanation.
But it will probably will not go in sarge anyway unless somebody can
backport support for old libpcap.
--=20
ciao,
Marco
--liOOAslEiF7prFVr
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCFzORFGfw2OHuP7ERAhWdAJoCka95MdE8A00RZuvaZj2NqP9dUACbBWT/
QjNGkieZ9PVaFrc6Zrokzxc=
=5z91
-----END PGP SIGNATURE-----
--liOOAslEiF7prFVr--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
