From owner-freebsd-net Sat Jan 15 15:50:51 2000 Delivered-To: freebsd-net@freebsd.org Received: from tricord.system.pl (tricord.system.pl [195.205.185.10]) by hub.freebsd.org (Postfix) with ESMTP id C957715179 for ; Sat, 15 Jan 2000 15:50:30 -0800 (PST) (envelope-from saper@system.pl) Received: from localhost (saper@localhost [127.0.0.1]) by tricord.system.pl (SYSTEM Internet) with ESMTP id AAA09863; Sun, 16 Jan 2000 00:49:11 +0100 (MET) Date: Sun, 16 Jan 2000 00:49:08 +0100 (MET) From: Marcin Cieslak To: Brian Somers Cc: freebsd-net@FreeBSD.ORG Subject: Re: RADIUS support in ppp(8) In-Reply-To: <200001150119.BAA01055@hak.lan.Awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 15 Jan 2000, Brian Somers wrote: > > is it my fault that I don't supply "Challenge-Response" > > (as Ascend radiusd calls it) attribute - or is it > > not supported yet? Who is supposed to supply challenge > > (RADIUS server)? > > ppp send the challenge to the client, the client sends a response and > ppp sends both the challenge & response to the radius server then > passes the radius servers answer back to the client. It appears that Ascend RADIUS daemon does not support CHAP-Challenge(60) attribute - this violates RFC 2138. After I made a quick hack, it seems to work now. The ppp accounting patches are under way :) -- << Marcin Cieslak // saper@system.pl >> ----------------------------------------------------------------- SYSTEM Internet Provider http://www.system.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message