[RadiusNT Digest]

Sun, 7 Jun 1998 00:00:16 -0700

Message 1: Re: feature request
from "Rudy Komsic" <rudyk@cyberglobe.net>

Message 2: Bad digest error?
from "Kevin L. Gross" <klg@randori.com>

..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.
| Message 1 |
'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'
Subject: Re: feature request
From: "Rudy Komsic" <rudyk@cyberglobe.net>
Date: Sat, 6 Jun 1998 06:01:20 -0400

Also to ADD to this feature is a Limiter that WILL NOT Allow Clients to dial
the other Lines if they paid for this one service. It should reject his

Also, when will it be added to 2.5 Emerald as it was promised that it will be
in it?

-----Original Message-----
From: Brian Lube <brian@mpinet.net>
To: radiusnt@iea-software.com <radiusnt@iea-software.com>
Date: June 5, 1998 4:31 PM
Subject: Re: feature request

>I'm sorry, I didn't finish that sentence (I got interrupted by one of the
>other sysadmins here). I'm looking for this in the Radlogs table, so that
>when someone fails I can find out what number they are dialing into and
>from. This is nice for finding people who are hacking into my system.
>Brian Lube
>At 01:05 PM 6/5/98 -0700, you wrote:
>>Brian Lube wrote:
>>> I have a feature request for the next release of RadiusNT. I would
>>> *really* like to see it record custom fields (such as NASPortDNIS and
>>> Callerid). This would help me out *so* much.
>>> Just a request.
>>If you are referring to the Calls table, it can already do this.
>>If you put fields in the Calls table matching the attribute names
>>(without the dashes) RadiusNT will populate the fields. It reads
>>the column list upon startup, so you have to restart it for the
>>changes to take affect.
>>Dale E. Reed Jr. (daler@iea-software.com)
>> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
>> Internet Solutions for Today | http://www.iea-software.com

..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.
| Message 2 |
'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'
Subject: Bad digest error?
From: "Kevin L. Gross" <klg@randori.com>
Date: Sat, 6 Jun 1998 10:36:46 -0700 (PDT)


I'm setting up a news server to query a customer's Radius box to
allow access to my news server. The customer is using RadiusNT.
I am using the Perl5 Authen::Radius package.

The host and secret are put into a hash table:

$r = new Authen::Radius(Host => $host, Secret => $secret);

which is used later during the actual radius call. I think all is
working; that is, the hash table gets created, and then a call gets
made to:

$rtn = $r->check_pwd($user, $pass);

But $rtn is empty. I run a

$err = $r->get_error;

immediately after the check_pwd call, and $err=ETIMEOUT. But I don't
know how it could be timing out in just a few seconds, maybe 10-15 max?

Now on the WindowsNT system running the RadiusNT, the log shows my
system connecting over the internet, but displays a "Bad Digest" and
goes no further. We are fairly certain the host, secret, user & pass are

I don't pretend to understand RadiusNT or NT itself for that matter but
I'm pretty sure the Perl on my UNIX system is working OK, or the target
system would not show the source system's name. I could be wrong. ;-)

Any help on this would really be appreciated. Thanks,

-Kevin L. Gross
Randori News - Providing USENET News Services to Netizens World Wide.
Send email to info@randori.com or visit http://www.randori.com