31.05.2008 01:13:24
nickm324
Posts: 9
|
I have noticed an issue where session records are not being removed when a user disconnects from the NAS and the stop accounting record is sent.
Sometimes the session records stays in the table and has to be manually deleted.
|
|
• permalink
• reply with quote
|
31.05.2008 10:59:56
admin
Administrator
Posts: 881
|
Hi,
Can you send log entries (from TekRADIUS.log) for such a session?
Thank you,
Yasin KAPLAN
|
|
• permalink
• reply with quote
|
31.05.2008 13:59:27
nickm324
Posts: 9
|
admin wrote:
Hi,
Can you send log entries (from TekRADIUS.log) for such a session?
Thank you,
Yasin KAPLAN
Yea next time it occurs I will send the zipped up copy of the log.
|
|
• permalink
• reply with quote
|
01.06.2008 00:52:54
nickm324
Posts: 9
|
Ok I think the issue is with long strings in the accounting record.
for this user bglover you can see the start record where the session started with this session ID = 489211755.
RadAuth req. from : 24.227.96.202 - 5/31/2008 6:11:46 AM
Size : 201 / 201
Identifier : 151
Attributes :
Calling-Station-Id = 8508592002
Framed-IP-Address = 192.168.1.150
NAS-Port-Type = 0
Called-Station-Id = 6610
User-Name = bgloverdfs
NAS-IP-Address = 192.168.1.5
Ascend-VSA-Xmit-Rate = 31200
Service-Type = 2
Ascend-VSA-Data-Rate = 21600
NAS-Port = 20101
Acct-Session-Id = 489211755
Framed-Protocol = 1
5/31/2008 6:11:46 AM - Authentication successfull for user bgloverdfs
RadAuth reply to : 24.227.96.202 - 5/31/2008 6:11:46 AM
Size : 32
Identifier : 151
Attributes :
Idle-Timeout = 1200
Session-Timeout = 28800
RadAcct req. from : 24.227.96.202 - 5/31/2008 6:11:47 AM
Size : 183 / 183
Identifier : 120
Attributes :
Framed-IP-Address = 192.168.1.150
Acct-Status-Type = Start
Calling-Station-Id = 8508592002
NAS-Port-Type = Async
Acct-Authentic = RADIUS
Called-Station-Id = 6610
User-Name = bgloverdfs
NAS-IP-Address = 192.168.1.5
Framed-Protocol = PPP
Ascend-VSA-Modem-SlotNo = 5
Ascend-VSA-Owner-IP-Addr = 0.0.0.0
NAS-Port = 20101
Ascend-VSA-Modem-PortNo = 6
Acct-Session-Id = 489211755
Acct-Delay-Time = 0
Then here you cans see where an accounting record was sent for max time exceeded but the session table was never cleard and it looks like it was an issue with the string.
And my NAS sent the ACCT record 4 times but the session table was never cleared of this user. Then a little while later the user tried to connect back and was rejected due to simultaneous connections.
But if you look here you can see the statment was terminated because of an issue with the string
I think due to the statement below being terminated the stop record was never accepted and thats why the session was not cleared.
5/31/2008 2:11:48 PM - Debug Message : (Radius Accounting)
String or binary data would be truncated.
The statement has been terminated.
I am sure I can work around this by reducing the length of the string in the dictionary, but it might be better if you were to put a limitation on the lenght of the string allowed in the description of the codes.
I can't include all 4 ACCT STOP records here be cause your forum has a limit of 4000 characters I will email the log to you.
RadAcct req. from : 24.227.96.202 - 5/31/2008 2:11:48 PM
Size : 333 / 333
Identifier : 109
Attributes :
5/31/2008 2:11:48 PM - Debug Message : (Radius Accounting)
String or binary data would be truncated.
The statement has been terminated.
Framed-Protocol = PPP
Ascend-VSA-Connect-Progress = 60
Acct-Authentic = RADIUS
Calling-Station-Id = 8508592002
Called-Station-Id = 6610
Acct-Status-Type = Stop
Ascend-VSA-Disconnect-Cause = Max-Call-Duration-Reached. The call disconnected because the call duration exceeded the maximum amount of time allowed by Max-Call-Duration.
Acct-Input-Octets = 3260655
Ascend-VSA-Pre-Input-Octets = 484
User-Name = bgloverdfs
Ascend-VSA-PreSession-Time = 31
Acct-Input-Packets = 67497
NAS-IP-Address = 192.168.1.5
Ascend-VSA-Data-Rate = 21600
Ascend-VSA-Modem-SlotNo = 5
Ascend-VSA-Pre-Input-Packets = 12
Ascend-VSA-Owner-IP-Addr = 0.0.0.0
Ascend-VSA-Modem-PortNo = 6
Acct-Delay-Time = 0
Ascend-VSA-Pre-Output-Octets = 251
Acct-Output-Octets = 21551318
Ascend-VSA-First-Dest = 224.0.0.22
NAS-Port = 20101
Acct-Output-Packets = 26808
Ascend-VSA-Xmit-Rate = 31200
Acct-Session-Id = 489211755
NAS-Port-Type = Async
Ascend-VSA-Pre-Output-Packets = 12
Acct-Session-Time = 28800
Framed-IP-Address = 192.168.1.150
|
|
• permalink
• reply with quote
|
01.06.2008 01:21:18
admin
Administrator
Posts: 881
|
Ascend-VSA-Disconnect-Cause attrbiute in RADIUS Accounting stop is uncesssaryly long. Try to shorten it using Dictionary Editor:
Ascend-VSA-Disconnect-Cause = Max-Call-Duration-Reached. The call disconnected because the call duration exceeded the maximum amount of time allowed by Max-Call-Duration.
|
|
• permalink
• reply with quote
|
01.06.2008 03:37:18
nickm324
Posts: 9
|
Yes I already shortened the string, but you may want to put a length restriction in TekManager to prevent anyone esle from entering a string to long.
My string is now just : Max-Call-Duration-Reached.
Will let you know if that resolves the issue completely or not.
|
|
• permalink
• reply with quote
|
27.01.2010 02:54:41
oilesa
Posts: 13
|
I have same problem with Simultaneous-Use, I have set it to 1 for users but somtimes they can not connect due to session are not cleard.
|
|
• permalink
• reply with quote
|
27.01.2010 10:38:13
admin
Administrator
Posts: 881
|
Hi,
If active session is not cleared when user logs out means TekRADIUS does not receive a proper RADIUS Accounting stop from the access server.
Please set logging level to debug to see if TekRADIUS receives a proper RADIUS accounting stop from the access server.
Best regards,
Yasin KAPLAN
|
|
• permalink
• reply with quote
|
27.01.2010 12:27:52
oilesa
Posts: 13
|
Dear Yasin,
It is active in my windows RRAS.I will put it to debug mode and will send you the log.
|
|
• permalink
• reply with quote
|
27.01.2010 12:35:48
admin
Administrator
Posts: 881
|
You can send log to info at tekradius.com
|
|
• permalink
• reply with quote
|
16.03.2010 10:13:57
angeles_eros
Posts: 2
|
Hi,
I am having the same issue. the stop requests is sent to tekradius but the session is not clearing. So when I try to login again I am getting rejected due to the simultaneous login.
AV
|
|
• permalink
• reply with quote
|
16.03.2010 10:55:38
angeles_eros
Posts: 2
|
I am also having the same issue. The stop record is sent to Tekradius but when I try to relogin I will be rejected due to the Simultaneous Login. Appreciate if you can help me to resolve this. attached is my logfiles for a session where I logged in once and try to relogin and gets rejected.
|
|
• permalink
• reply with quote
|
16.03.2010 18:02:54
admin
Administrator
Posts: 881
|
Hi,
As far as from the see logs, Accounting-Start message does not have "NAS-Port = 2" attribute. TekRADIUS can not match Checkpoint and stop Stop messages since Accounting-Start message does not have "NAS-Port = 2" attribute.
|
|
• permalink
• reply with quote
|
16.03.2010 19:34:39
oilesa
Posts: 13
|
admin wrote:
Hi,
As far as from the see logs, Accounting-Start message does not have "NAS-Port = 2" attribute. TekRADIUS can not match Checkpoint and stop Stop messages since Accounting-Start message does not have "NAS-Port = 2" attribute.
Hi Yasin,
So what is the solution?
After testing I found out that this problem occurred when my internet connection drop suddenly, in this case Session will remain in active sessions.
|
|
• permalink
• reply with quote
|
16.03.2010 20:11:40
admin
Administrator
Posts: 881
|
You may add Session-Timeout attribute (Reply) to user/group profiles. Most access servers, including access-points, clear session and send a proper
RADIUS-Accounting stop after session timer expires. But keep in mind that it's the access server's responsibility to check existence of the user session. If user session drops for a reason access server must send a proper RADIUS Accounting stop message to the RADIUS server.
|
|
• permalink
• reply with quote
|
22.05.2010 20:01:21
oilesa
Posts: 13
|
Dear Yasin,
I have same problem, Sessions are no being cleared from sessions table and I should clear it manually from table after dropping of line and ... , (I should consider that in new version (3.5) problem for connecting to server after dropping line has been resolved and it is working fine. ) .So problem just is records that are remained in tables and it dose not shows real time information.
|
|
• permalink
• reply with quote
|
23.05.2010 14:58:05
admin
Administrator
Posts: 881
|
Please examine TekRADIUS.log if RADIUS Accounting-Stop packet has been received. I also recommend you to upgrade to version 3.5.
|
|
• permalink
• reply with quote
|