11.05.2011 04:31:26
khakim_sr
Posts: 2
|
Hi, I Love Tekradius,
I Use Mikrotik 3.22 with Tekradius authenticated . But , While i use Mikrotik 2.9.6 Is Work Perfectly, but i upgraded to 3.22 Version
My Mikrotik was hang when i login it. I search in other forum, maybe its a bug of mikrotik or Tekradius, it was always hang after i button login pressed on web Login Mikrotik 3.22 or 3.20. Can you ceck it up.
My tekradius said nothing problem with that.
Please Help me how to fix that, a lot of account was on it.
Thank you.
Regards,
Nor Khakim
|
|
|
0
• permalink
|
11.05.2011 10:11:22
Admin
Administrator
Posts: 1833
|
Hi,
Can you send TekRADIUS log entries (Accessible through File menu) after setting log level to debug at Settings / Service Parameters?
Best regards,
Yasin KAPLAN
|
|
|
0
• permalink
|
11.05.2011 10:29:50
khakim_sr
Posts: 2
|
5/11/2011 1:51:17 PM - TekRADIUS Service 4.2.0.0 is being started (Microsoft Windows NT 5.2.3790 Service Pack 2).
5/11/2011 1:53:52 PM - Clients table refreshed.
5/11/2011 1:54:46 PM - TekRADIUS Service 4.2.0.0 is being started (Microsoft Windows NT 5.2.3790 Service Pack 2).
5/11/2011 1:54:50 PM - TekRADIUS Service is listening on : 192.123.123.92 (2 client(s))
5/11/2011 1:54:50 PM - Sending alert message...
5/11/2011 1:54:53 PM - Alert message sent...
RadAuth req. from : 192.123.123.123:51095 - 5/11/2011 1:57:19 PM
Size : 210 / 210
Identifier : 3
Attributes :
5/11/2011 1:57:19 PM - Invalid Auth. packet received from : 192.123.123.123:51095
NAS-Port-Id = Lokalisasi
Framed-IP-Address = 10.10.10.57
NAS-Identifier = MK-INFORMATIKA
Calling-Station-Id = D4:85:64:A7 57
User-Name = 08621012
NAS-Port = 2154823680
WISPr-Logoff-URL = http://10.10.10.245/logout
Mikrotik-Host-IP = 10.10.10.57
Service-Type = 1
NAS-IP-Address = 192.123.123.123
Called-Station-Id = hotspot1
Acct-Session-Id = 80700000
NAS-Port-Type = 19
5/11/2011 1:57:19 PM - CHAP authentication successful (Group : Ang-2008-Pagi).
5/11/2011 1:57:19 PM - Authentication successfull for user '08621012'
RadAcct req. from : 192.123.123.123:36689 - 5/11/2011 2:00:55 PM
Size : 54 / 54
Identifier : 2
Attributes :
Acct-Delay-Time = 0
NAS-IP-Address = 192.123.123.123
NAS-Identifier = MK-INFORMATIKA
Acct-Status-Type = Accounting-On
User-Name =
RadAuth req. from : 192.123.123.123:57912 - 5/11/2011 2:01:02 PM
Size : 207 / 207
Identifier : 3
Attributes :
NAS-Port-Id = Lokalisasi
Framed-IP-Address = 10.10.10.57
NAS-Identifier = MK-INFORMATIKA
Calling-Station-Id = D4:85:64:A757
User-Name = 10622003
NAS-Port = 2155872256
WISPr-Logoff-URL = http://10.10.10.245/logout
Mikrotik-Host-IP = 10.10.10.57
Service-Type = 1
NAS-IP-Address = 192.123.123.123
Called-Station-Id = hotspot1
Acct-Session-Id = 80800000
NAS-Port-Type = 19
5/11/2011 2:01:02 PM - Authentication failed for user '10622003'
5/11/2011 2:24:30 PM - TekRADIUS Service 4.2.0.0 (Revision 0) is being stopped.
5/11/2011 2:24:30 PM - All active sessions stopped.
5/11/2011 2:24:36 PM - TekRADIUS Service 4.2.0.0 is being started (Microsoft Windows NT 5.2.3790 Service Pack 2).
5/11/2011 2:24:39 PM - TekRADIUS Service is listening on : 192.123.123.92 (2 client(s))
5/11/2011 2:24:39 PM - Sending alert message...
5/11/2011 2:24:42 PM - Alert message sent...
After Login, My Mikrotik was Hang..
I dont know why ??
|
|
|
0
• permalink
|
13.05.2011 11:05:35
Admin
Administrator
Posts: 1833
|
Hi,
It looks like TekRADIUS functions as expected. Which login attempt causes Mikrotik to hang? 08621012 or 10622003?
As far as I've investigated there is nothing about this problem in Mikrotik
resources. It may be a new case. I recommend you to contact with Mikrotik technic support.
|
|
|
0
• permalink
|