Re: [NTISP] Radius nt emergency

Dave P. ( (no email) )
Sun, 12 Dec 1999 14:54:12 -0500

Hi Dale,
Since this original posting, Brian from my ISP went to your web site
to get info about the company. He called to say that the problem does
lie elsewhere. He said he knows you and is going to try to contact you
about this problem. In the meantime hear is the log file you were
asking about. Thanks for your help in advance.

Resp Time: 110 Auth: 0/0 -> 0 Acct: 65/0/0 -> 65
radrecv: Request from host d1d54809 code=4, id=40, length=158
NAS-IP-Address =
NAS-Port = 96
NAS-Port-Type = Async
Acct-Status-Type = Stop
Acct-Delay-Time = 46
Acct-Session-Id = "309249340"
Ascend-Disconnect-Cause = 45
Ascend-Connect-Progress = 200
Received unknown attribute 255
Ascend-Data-Rate = 33600
Ascend-PreSession-Time = 37
Ascend-Pre-Input-Octets = 397
Ascend-Pre-Output-Octets = 1656
Ascend-Pre-Input-Packets = 17
Ascend-Pre-Output-Packets = 6
Received unknown attribute 120
Received unknown attribute 121
Received unknown attribute 122
Caller-Id = "9782825151"
NAS-Port-DNIS = "9782316652"
Sending Accounting Ack of id 40 to d1d54809 (

Resp Time: 120 Auth: 0/0 -> 0 Acct: 66/0/0 -> 66

Dave Palazola

-----Original Message-----
From: Dale E. Reed Jr. <>
To: <>
Date: Sunday, December 12, 1999 1:59 PM
Subject: Re: [NTISP] Radius nt emergency

>"Dave P." wrote:
>> Is IEA's radius NT RFC compliant? I an running version 2.5. I have a
>I don't think there are any RFC *COMPLIANT* RADIUS servers on the
>(mainly, because there were implementation/variations of RADIUS before
>the RFC was finalized). We are definately one of the most stringent
>although there are a lot of compatability settings we have had to deal
>with over the years.
>> modem pool for my 56K lines thru my T1 Supplier. I am a small ISP.
>> They upgraded some of their servers tonite and now my customers can't
>> log onto the 56K lines. My ISP is telling me that it's because of a
>> problem with the brand of Radius NT I am using. It's supposed to be
>> compliant. They are telling me, they don't believe that IEA's Radius
>> is RFC compliant. Need help asap. Thanks
>Thats just a BS story they are telling you, which I don't accept.
>Send me the -x15 debug mode and I'll tell you what the problem is.
>The last two times someone tried to challenge the RFC compliance of
>RadiusNT with me, *they* lost. That didn't mean they fixed the
>problem (we had to patch RadiusNT to work with their shortcomings),
>but I'll take a challenge of the RFC any day. :)
>Dale E. Reed Jr. Emerald and RadiusNT
>IEA Software, Inc.
>For more information about this list (including removal) go to:

For more information about this list (including removal) go to: