From owner-freebsd-stable Tue Jul 4 6:53:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sr14.nsw-remote.bigpond.net.au (sr14.nsw-remote.bigpond.net.au [24.192.3.29]) by hub.freebsd.org (Postfix) with ESMTP id E019C37B59F for ; Tue, 4 Jul 2000 06:53:30 -0700 (PDT) (envelope-from areilly@nsw.bigpond.net.au) Received: from areilly.bpc-users.org (CPE-144-132-171-71.nsw.bigpond.net.au [144.132.171.71]) by sr14.nsw-remote.bigpond.net.au (Pro-8.9.3/8.9.3) with SMTP id WAA26374 for ; Tue, 4 Jul 2000 22:07:59 +1000 (EST) Received: (qmail 794 invoked by uid 1000); 4 Jul 2000 12:07:57 -0000 From: "Andrew Reilly" Date: Tue, 4 Jul 2000 22:07:57 +1000 To: brian@Awfulhak.org, freebsd-stable@freebsd.org Cc: John Polstra , cananian@alumni.princeton.edu Subject: PPP in pptpclient, specifically EAP authentication Message-ID: <20000704220757.A99956@gurney.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've just discovered that ppp on my recent FreeBSD-stable system (FreeBSD gurney.reilly.home 4.0-STABLE FreeBSD 4.0-STABLE #0: Tue Jul 4 14:30:20 EST 2000 root@gurney.reilly.home:/usr/obj/usr/src/sys/GURNEY i386), when used with the pptpclient port (aka pptp-linux-1.0.2), won't authenticate to a Windows 2000 server running Microsoft's VPN. A little poking through the ppp logs shows that it doesn't like AUTHPROTO[4] 0xc227 (unknown). A bit of web digging shows that that is the so-called Extensible Authentication Protocol (EAP) defined in RFC 2284, and described at: http://www.networksorcery.com/enp/protocol/eap.htm a) Does anyone have this implemented for our PPP, and is looking for someone to test patches? b) Does anyone know of any way to force said Windows 2000 system to authenticate using something like CHAP or MS-CHAP, that our PPP _does_ understand? Thaks in advance, -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message