Dear Coova Chilli Community<br><br>Firstly, my setup:<br><ol><li>Coova Chilli 1.013</li><li>Freeradius 2.1.5</li></ol>I am absolutely perplexed by this bug. Not only that, but I cannot think of any ways of reproducing it, so I am hoping someone in the community has come accross this before. My problem is my NAS is reporting incorrectly high usage over a short space of time. Where we are based (South Africa), the fastest one's ADSL line speed can be is 4 mega bits per second. This translates to about 0.47 megabytes per seconds, and that is if you are lucky. We have three such lines multiplexed together, which means we can get a throughput of about 0.47*3 = 1.41 megabytes per second. Unfortunately, we have received a complaint claiming that chilli has deducted more than what was used. Looking at the radius logs, I can ascertain that this is true.<br>
<br>Here is the initial start packet sent by chilli to radius (I have removed username and Nas Identifier to protect privacy):<br><br><i>Tue Oct 27 09:12:57 2009<br> ChilliSpot-Version = "1.0.13"<br> Acct-Status-Type = Start<br>
Calling-Station-Id = "00-1F-33-FF-BD-00"<br> NAS-Port-Type = Wireless-802.11<br> NAS-Port = 4<br> NAS-Port-Id = "00000004"<br> Framed-IP-Address = 172.25.0.168<br> Acct-Session-Id = "4ae69d6000000004"<br>
NAS-IP-Address = 172.25.0.1<br> Called-Station-Id = "00-16-B6-D9-5A-EB"<br> Acct-Unique-Session-Id = "f3bcc21590c1afd1"<br> Timestamp = 1256627577<br> Request-Authenticator = Verified</i><br>
<br>Then about 1 minute later, the following occurs<br><i>Tue Oct 27 09:13:59 2009<br> ChilliSpot-Version = "1.0.13"<br> Acct-Status-Type = Interim-Update<br> Calling-Station-Id = "00-1F-33-FF-BD-00"<br>
NAS-Port-Type = Wireless-802.11<br> NAS-Port = 4<br> NAS-Port-Id = "00000004"<br> Framed-IP-Address = 172.25.0.168<br> Acct-Session-Id = "4ae69d6000000004"<br> NAS-IP-Address = 172.25.0.1<br>
Called-Station-Id = "00-16-B6-D9-5A-EB"<br><b> Acct-Input-Octets = 1178355<br> Acct-Output-Octets = 52201523</b><br> Acct-Input-Gigawords = 0<br> Acct-Output-Gigawords = 0<br> Acct-Input-Packets = 19170<br>
Acct-Output-Packets = 36581<br> Acct-Session-Time = 63<br> Acct-Unique-Session-Id = "f3bcc21590c1afd1"<br> Timestamp = 1256627639<br> Request-Authenticator = Verified</i><br><br>
This is definitely in error (the bold parts), as the backbone line speed cannot handle this much traffic in such a short space of time. Another minute later:<br>Tue Oct 27 09:15:02 2009<br><i> ChilliSpot-Version = "1.0.13"<br>
Acct-Status-Type = Interim-Update<br> Calling-Station-Id = "00-1F-33-FF-BD-00"<br> NAS-Port-Type = Wireless-802.11<br> NAS-Port = 4<br> NAS-Port-Id = "00000004"<br> Framed-IP-Address = 172.25.0.168<br>
Acct-Session-Id = "4ae69d6000000004"<br> NAS-IP-Address = 172.25.0.1<br> Called-Station-Id = "00-16-B6-D9-5A-EB"<br><b> Acct-Input-Octets = 2132628<br> Acct-Output-Octets = 98448008</b><br>
Acct-Input-Gigawords = 0<br> Acct-Output-Gigawords = 0<br> Acct-Input-Packets = 36067<br> Acct-Output-Packets = 68754<br> Acct-Session-Time = 126<br> Acct-Unique-Session-Id = "f3bcc21590c1afd1"<br>
Timestamp = 1256627702<br> Request-Authenticator = Verified</i><br><br>Again, the amount of data usage is absolutely impossible for the backbone's capabaility. Another minute later:<br><i>Tue Oct 27 09:16:05 2009<br>
ChilliSpot-Version = "1.0.13"<br> Acct-Status-Type = Interim-Update<br> Calling-Station-Id = "00-1F-33-FF-BD-00"<br> NAS-Port-Type = Wireless-802.11<br> NAS-Port = 4<br>
NAS-Port-Id = "00000004"<br> Framed-IP-Address = 172.25.0.168<br> Acct-Session-Id = "4ae69d6000000004"<br> NAS-IP-Address = 172.25.0.1<br> Called-Station-Id = "00-16-B6-D9-5A-EB"<br>
<b> Acct-Input-Octets = 3097259<br> Acct-Output-Octets = 146070592</b><br> Acct-Input-Gigawords = 0<br> Acct-Output-Gigawords = 0<br> Acct-Input-Packets = 53364<br> Acct-Output-Packets = 101854<br>
Acct-Session-Time = 189<br> Acct-Unique-Session-Id = "f3bcc21590c1afd1"<br> Timestamp = 1256627765<br> Request-Authenticator = Verified</i><br><br>Again, impossibly high. There is just one more account interim update, and then the person is logged off due to insufficient credit:<br>
<i>Tue Oct 27 09:17:14 2009<br> ChilliSpot-Version = "1.0.13"<br> Acct-Status-Type = Stop<br> Calling-Station-Id = "00-1F-33-FF-BD-00"<br> NAS-Port-Type = Wireless-802.11<br>
NAS-Port = 4<br> NAS-Port-Id = "00000004"<br> Framed-IP-Address = 172.25.0.168<br> Acct-Session-Id = "4ae69d6000000004"<br> NAS-IP-Address = 172.25.0.1<br> Called-Station-Id = "00-16-B6-D9-5A-EB"<br>
<b> Acct-Input-Octets = 3701744<br> Acct-Output-Octets = 175905676</b><br> Acct-Input-Gigawords = 0<br> Acct-Output-Gigawords = 0<br> Acct-Input-Packets = 64216<br> Acct-Output-Packets = 122605<br>
Acct-Session-Time = 228<br> Acct-Terminate-Cause = Session-Timeout<br> Acct-Unique-Session-Id = "f3bcc21590c1afd1"<br> Timestamp = 1256627834<br> Request-Authenticator = Verified</i><br>
<br>All in all, chilli has told radius that the user has used 171.29 megabytes in 3.8 minutes. Of that, 167.76 megabytes were in downloads, and 3.53 megabytes were in uploads. Unfortunately, this is absolutely impossible with regards to the backbone speeds in South Africa.<br>
<br>Any help would be greatly appreciated, I have no idea how to solve this.<br><br>All the best<br>Jack J Allan<br>