[dan at waycom.com: Re: Radius Help Anyone ?]
jnn at jump.net
Wed Jan 24 00:09:20 UTC 2001
Forwarded at Daniel's request, since he lost the message...
-- Attached file included as plaintext by Listar --
Received: from mail11.jump.net (mail11.jump.net [22.214.171.124])
by admin3.jump.net (8.9.3/8.9.1) with ESMTP id QAA11404
for <jnn at admin3.jump.net>; Tue, 23 Jan 2001 16:53:35 -0600 (CST)
Received: from ns1.waycom.com (ns1.waycom.com [126.96.36.199])
by mail11.jump.net (8.10.2/) with ESMTP id f0NMrU921461
for <jnn at jump.net>; Tue, 23 Jan 2001 16:53:31 -0600 (CST)
Received: from earth (earth.waycom.com [188.8.131.52])
by ns1.waycom.com (8.10.1/8.10.1) with SMTP id f0NMrTR03279
for <jnn at jump.net>; Tue, 23 Jan 2001 17:53:29 -0500
Message-ID: <004201c08590$4a482200$8809acd1 at waycom.com>
From: "Daniel G. Thompson" <dan at waycom.com>
To: <jnn at jump.net>
References: <001e01c080ef$bd618d80$8809acd1 at waycom.com> <20010123154441.A9519 at admin3.jump.net>
Subject: Re: Radius Help Anyone ?
Date: Tue, 23 Jan 2001 18:00:33 -0500
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Thanks for your response. Actually I found the part about needing to
the path in early in the game. My problem was that I kept getting rejects
the radius server. The actual problem was that all of my dialup servers are
Ascend products so I use Ascend radius. Ascend radius did not like the
for some reason, and would not log enough information for me to tell what
happening. Eventually I downloaded the most recent version of Cistron Radius
and set it up on another machine. Within 20 minutes of compiling the Cistron
Radius I had it configured and answering requests from the news server.
>From what I read in the docs for the Cistron Radiusd it appears that I can
use this daemon just fine with my Ascend Access Servers. I have not tried
yet, but should have a new one here within a few days that I can test with
still keep the natives happy ... ).
What we learned from this ?
Documentation should include references to the fact that the radius client
is included with inn-2.3.0 does not work with Ascend Radius. The
should also include references to radius daemons that do work with the
radius client (ie: Cistron).
dan at waycom.com
----- Original Message -----
From: "John Newman" <jnn at jump.net>
To: "Daniel G. Thompson" <dan at waycom.com>
Cc: <inn-workers at isc.org>
Sent: Tuesday, January 23, 2001 4:44 PM
Subject: Re: Radius Help Anyone ?
> The "auth" key, inside of the auth stanza that you want accessed
> via radius, needs to be set to "radius". This will make inn spawn
> the /news/bin/auth/passwd/radius.... radius.conf needs to be setup
> with the info for your radius server.
> On my setup the radius program, with inn 2.3.0, would not properly
> find its config file and segfaulted. I hard-coded the config file
> path into the source and it started working.
> In our previous exciting episode Wed, Jan 17, 2001 at 08:41:12PM -0500,
Daniel G. Thompson said:
> > I am new to the group and have not had much time to lurk here first but
> > here goes.
> > I have two large news servers that currently are using ip-address/domain
> > authentication for access rights. I am trying my best to make the news
> > servers
> > do Radius auth as well ( this will make life much easier ). I am quite
> > experienced
> > with Radius for use with remote access services so mostly I need to find
> > some
> > documentation about how to use it with INN.
> > I have searched a number of sites and as of yet have found mostly vague
> > references but nothing of a whole lot of value.
> > I have the sample config files as well as the binary that was included
> > INN-2.3.0.
> > I would be very pleased if someone could point me to some documentation,
> > new binaries or even newer source so that I can get radius to work with
> > news.
> > Thank You
> > Dan Thompson
> > dan at waycom.com
More information about the inn-workers