Community discussions

MikroTik App
 
vicmkrtk
just joined
Topic Author
Posts: 1
Joined: Mon Jun 29, 2020 2:05 am

Bug? Hotspot + Radius: NAS-Port-Id Attribute lost in Stop packet when HS server has been disabled (CCR1036, v6.47)

Mon Jun 29, 2020 3:23 am

Hi All

The radius stop packets' content are different when customer disconnected normally and when I disable hotspot server.
When I disable HS server the stop packet doesn't contain NAS-Port-Id.
Below are the content samples for these two cases.

The normal packet (user logoff, lost service, deleted in WinBOX):
(5) Received Accounting-Request Id 193 from 10.1.5.9:44375 to 10.1.0.25:1813 length 242
(5)   Acct-Status-Type = Stop
(5)   Acct-Terminate-Cause = Lost-Carrier
(5)   NAS-Port-Type = Wireless-802.11
(5)   Calling-Station-Id = "30:**:**:**:**:C1"
(5)   Called-Station-Id = "HS-Test"
(5)   NAS-Port-Id = "net-HS-test"
(5)   User-Name = "192.168.9.30"
(5)   MS-CHAP-Domain = "Hotspot"
(5)   NAS-Port = 2149580800
(5)   Acct-Session-Id = "80200000"
(5)   Framed-IP-Address = 192.168.9.30
(5)   Mikrotik-Host-IP = 192.168.9.30
(5)   Event-Timestamp = "Jun 28 2020 19:27:25 AST"
...
(5)   Acct-Session-Time = 24
(5)   NAS-Identifier = "CCR1036"
(5)   Acct-Delay-Time = 0
(5)   Mikrotik-Realm = "Hotspot"
(5)   NAS-IP-Address = 10.1.5.9
The packet content when HS server disabled (NAS-Port-Id lost):
(8) Received Accounting-Request Id 196 from 10.1.5.9:45743 to 10.1.0.25:1813 length 229
(8)   Acct-Status-Type = Stop
(8)   Acct-Terminate-Cause = Lost-Carrier
(8)   NAS-Port-Type = Wireless-802.11
(8)   Calling-Station-Id = "30:**:**:**:**:C1"
(8)   Called-Station-Id = "HS-Test"
(8)   User-Name = "192.168.9.30"
(8)   MS-CHAP-Domain = "Hotspot"
(8)   NAS-Port = 2149580801
(8)   Acct-Session-Id = "80200001"
(8)   Framed-IP-Address = 192.168.9.30
(8)   Mikrotik-Host-IP = 192.168.9.30
(8)   Event-Timestamp = "Jun 28 2020 19:28:56 AST"
...
(8)   Acct-Session-Time = 23
(8)   NAS-Identifier = "CCR1036"
(8)   Acct-Delay-Time = 0
(8)   Mikrotik-Realm = "Hotspot"
(8)   NAS-IP-Address = 10.1.5.9
What affects: Freeradius (FR3) calculates an unique session id based on many attributes include NAS-Port-Id.
FR uses new session ID and creates new accounting session in additional to previously created (start and interim packets contains NAS-Port-Id).
As work around I deleted NAS-Port-Id from sessions' hash.

Who is online

Users browsing this forum: No registered users and 154 guests