RE: [RadiusNT] MLPPP / RadiusNT / Ascend MAX TNT

Austin, Gary D ( (no email) )
Fri, 14 Apr 2000 10:51:10 -0400

Make sure you have 'Variable login limits' is turned on. Ihad the same
problem.

-----Original Message-----
From: Clara Hatem [mailto:clara@inco.com.lb]
Sent: Friday, April 14, 2000 10:32 AM
To: radiusnt@iea-software.com
Subject: [RadiusNT] MLPPP / RadiusNT / Ascend MAX TNT

Hello,

We need to offer Multi Link PPP dial up connections to our customers.

We are running Emerald, and Radius NT version 2.5.206

I have configured the user (clarah) with the following attributes
Framed-Protocol = MPP
User-Service = Framed-User
Idle Timeout = 900 seconds
Login Limit = 2

I am using DUN on a win95 station with DUN 1.3 Update (to support MLPPP)

And establishing a connection to an Ascend MAX TNT Access server.

The problem is that the first connection is established , but the second
connection drops at authentication. No entries show in the RadLog.

We have extracted debug entries from the MAX TNT :
(The 2nd MPP session is being authenticated by Radius, but the accounting
records are somehow incorrect, triggering the disconnection. I noticed that
accouting record type 0 does not show) ; The username used is clarah.

Unsuccessful 2nd MPP Session Attempt
---------------------------------------------------------------------------
RADIF: radius type Auth ID = 75
RADIF: authenticating <6:clarah> with CHAP
RADIF: _radiusRequest: id 75, user name <7:clarah>
RADIF: _radiusReq: challenge len = <0>
RADIF: _radiusReq: socket 2 len 104 ipaddr 192.168.168.2 port 1678->1645
RADIF:_radiusReq: id 75 <7:clarah>, starting timer (10 sec)
RADIF: _radCallback: buf=101ECF90 from 192.168.168.2 1645
RADIF: _radCallback, authcode = 2, id 75
RADIF: _radCallback: id 75, killing timer
RADIF: Authentication Ack
RADIF: attribute 7, len 6, 00 00 01 00
RADIF: attribute 28, len 6, 00 00 03 84
RADIF: attribute 6, len 6, 00 00 00 02
RADIF: attribute 27, len 6, 2a ae 14 40
RADIF:_freeInfoClassSess

Accounting Record
----------------------------------------------------------------------------

RADIF: radius type Acct ID = 72 (<--- Following this there should be a type
0
AcctRequest ?? it is missing ...)
RADIF: _radiusAcctRequest: type 1 id 72, user name <0:> (<--- Note blank
user)
RADIF: _radiusAcctReq: socket 4 len 134 IP 194.126.5.8 port 1800=>1646,
ID=72
RADIF: _radCallback: buf=101EB5D0 from 194.126.5.8 1646
RADIF: _radProcAcctRsp: user:<0:>, ID=72
RADIF:_freeInfoClassSess
RADIF: _radCallback: processed acct server type=1 (<--- Acctg Stop Record.)

Any help is appreciated.

Thank you,
Clara

`\|||/
(@@)
ooO_(_)_Ooo________________________________
_____|_____|_____|_____|_____|_____|_____|_____|
___|____|_____|_____|_____|_____|_____|_____|____
_____|_____|_____|_____Have a Nice Day __|__|____|

Clara Hatem
Network Operation Center

Technical and IT Dpt.
IncoNet sal
Beirut - LEBANON

Mobile: 961 3 278216
Phone(Office): 961 1 255696 ext 707
Email:clara@inco.com.lb
P.O.Box: 16-6928 Beirut - LEBANON
___|____|_____|_____|_____|_____|_____|_____|____|

For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart

For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart