(RADIATOR) Problem of Radiator MAXT TNT

[Muhammad Farooq Bhatti]

Dear Hugh

My problem of multi-login is solved its due to MAX TNT shared-pro setting in
ip-global profile.

But I still need a favor for my second query in which I mentioned for the
readable Disconnection Cause from Radiator dictionary Attribute.

1) That is How I can  relate MAX TNT Disco cause Attribute which is
Ascend-Disconnect-Cause = 101
 with Radius Attribute of Acct-Terminate-Cause to get a readable reason of
user disconnection in the log.

2) Any one from the list have some experience configuring radiator in
Redback BRAS; please guide me I am able to get Access-Accept but not been
able to connect. I am going to authenticate it from local system user
without accounting.

Please see the log

####################### Log of radius

Packet length = 97
01 1f 00 61 8a 04 c0 a7 72 c0 9f 77 f2 54 90 e6
a9 e8 18 4d 01 09 66 62 68 61 74 74 69 02 12 78
5b 18 d7 f8 7d 3a 86 78 97 32 7a 73 25 84 92 20
09 52 65 64 62 61 63 6b 1a 0c 00 00 09 30 3e 06
28 00 00 38 06 06 00 00 00 02 07 06 00 00 00 01
05 06 e8 00 02 42 4d 05 75 62 72 08 06 d2 38 0c
03
Code:       Access-Request
Identifier: 31
Authentic:  <138><4><192><167>r<192><159>w<242>T<144><230><169><232><24>M
Attributes:
        User-Name = "fbhatti"
        User-Password = "x[<24><215><248>}:<134>x<151>2zs%<132><146>"
        NAS-Identifier = "Redback"
        RB-NAS-Real-Port = 671088696
        Service-Type = Framed-User
        Framed-Protocol = PPP
        NAS-Port = 3892314690
        Connect-Info = "ubr"
        Framed-IP-Address = 210.56.12.3

Mon Aug 16 18:45:29 2004: DEBUG: Handling request with Handler
'Realm=DEFAULT'
Mon Aug 16 18:45:29 2004: DEBUG:  Deleting session for fbhatti, 210.56.14.9,
3892314690
Mon Aug 16 18:45:29 2004: DEBUG: Handling with Radius::AuthUNIX: System
Mon Aug 16 18:45:29 2004: DEBUG: Radius::AuthUNIX looks for match with
fbhatti
Mon Aug 16 18:45:29 2004: DEBUG: Radius::AuthUNIX ACCEPT:
Mon Aug 16 18:45:29 2004: DEBUG: Access accepted for fbhatti
Mon Aug 16 18:45:29 2004: DEBUG: Packet dump:
*** Sending to 210.56.14.9 port 1812 ....

Packet length = 46
02 1f 00 2e e5 2b c1 a1 11 12 92 c9 2d 69 d5 2c
47 01 33 45 1a 0d 00 00 09 30 04 07 6c 6f 63 61
6c 1a 0d 00 00 09 30 31 07 6c 6f 63 61 6c
Code:       Access-Accept
Identifier: 31
Authentic:  <138><4><192><167>r<192><159>w<242>T<144><230><169><232><24>M
Attributes:
        RB-Context-Name = "local"
        RB-Bind-Int-Context = "local"

Mon Aug 16 18:45:39 2004: DEBUG: Packet dump:
*** Received from 210.56.14.9 port 1812 ....

###################### End of log


 Muhammad Farooq Bhatti
 Assistant Director (Systems)
 First Floor, COMSATS Headquarters,
 Shahra-e-Jamhuriyat, G-5/2, Islamabad
 Ph. +92-51-9208063-5 Ext. 124
 Fax. +92-51-9212411
 farooq.bhatti at comsats.net.pk
 www.comsats.net.pk




----- Original Message ----- 
From: "Muhammad Farooq Bhatti" <farooq.bhatti at comsats.net.pk>
To: "Hugh Irvine" <hugh at open.com.au>
Cc: <radiator at open.com.au>
Sent: Friday, August 13, 2004 12:20 PM
Subject: Re: (RADIATOR) Problem of Radiator MAXT TNT


> Dear hugh
>
> Thanx for the clue of using authplsql.pm  I will try it later but even
after
> removing one of
> <SessionDatabase SQL>  its log is same as mentioned. If you could guide me
> why
> Ascend-Disconnect-Cause = 101
> Ascend-Connect-Progress = 67
>
> is comming in Access-request stop packet. of "comsats" user connection on
> MAX TNT for multi-login.
>
> where as ascend itself explain that
> Disconect-cause=101 is for The session failed for security reasons, such
as
> an invalid incoming user.
> Connect-Progress = 67 is for IPNCP is in the Open state.
>
> One more favour if u can guide is how can I make "disconnect cause code"
to
> readable in MAX like in cisco we get propper
> Acct-Terminat-casue.
> e.g. in ciscoAs5300,
> Acct-Terminate-Cause = User-Request
>
> Thanx and regards.
>
> Farooq Bhatti.

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.