Re: Ascend-Maximum-Time limitation with Radius

Dale E. Reed Jr. ( (no email) )
Sun, 04 May 1997 03:19:49 -0700

Josh Hillman wrote:
>
> > I was told by ascend that in the User profile Ascend-Maximum-Time did not
> > work correctly even with their own Radius.
>
> Here's what the tech at Ascend wrote to me the last time...

Ok. I setup a trial for this. Here is my user entry:

-------------------------------------
amt Password = "amt"
User-Service = Framed-User
Framed-Protocol = PPP
Framed-Address = 255.255.255.254
Ascend-Maximum-Time = 12850637
-------------------------------------

radlogin shows:

-------------------------------------
C:\RADIUS>radlogin amt amt

Checking Radius user amt:
User-Service = Framed-User
Framed-Protocol = PPP
Framed-Address = 255.255.255.254
Ascend-Maximum-Time = 12850637
0: Time: 50 Auth: Good

1 Good 0 Bad 50 Avg
-------------------------------------

RadiusNT shows this in debug AND I got a valid PPP link
up, when Authing from the MAX. This is 5.0Ap1 on a 4004.

-------------------------------------
radrecv: Request from host cf3580fa code=1, id=177, length=82
User-Name = "amt"
Password = "\034\323+`"
NAS-IP-Address = 207.53.128.250
NAS-Port = 20101
NAS-Port-Type = Async
User-Service = Framed-User
Framed-Protocol = PPP
State = ""
Framed-Address = 207.53.128.238
Acct-Session-Id = "226586839"
rad_authenticate()
Checking user record PW_PASSWORD type
authPapPwd
chkPwd->strvalue is amt
decrypted pwd is amt
Sending Ack of id 177 to cf3580fa (207.53.128.250)
User-Service = Framed-User
Framed-Protocol = PPP
Framed-Address = 255.255.255.254
Ascend-Maximum-Time = 12850637

Response Time: 191
radrecv: Request from host cf3580fa code=4, id=178, length=80
User-Name = "amt"
NAS-IP-Address = 207.53.128.250
NAS-Port = 20101
Acct-Status-Type = Start
Acct-Delay-Time = 0
Acct-Session-Id = "226586839"
Acct-Authentic = RADIUS
Framed-Protocol = PPP
Framed-Address = 207.53.128.239
Sending Accounting Ack of id 178 to cf3580fa (207.53.128.250)

Response Time: 271
-------------------------------------

Unless someone can give me some more to go on and re-produce
the problem, I don't think this is a problem in RadiusNT. The
main reason is that RadiusNT uses the same A/V code for ALL
integer A/V pairs. If there was a problem, ALL integer A/V pairs
would have this problem.

-- Dale E. Reed Jr.  (daler@iea.com)_________________________________________________________________       IEA Software, Inc.      |  RadiusNT, Emerald, and NT FAQs Internet Solutions for Today  |    http://www.emerald.iea.com