2013-04-25 - [GRASE-Hotspot] #102: Clarify Kibits vs Kbits in Bandwidth

Header Data

From: GRASE Trac <tr***c@grasehotspot.org>
Message Hash: 12dd1d9f929474e3c1b401651ed0777ba3bea246e451edeb349797acfc4725c6
Message ID: <039.9204cfe96e961a249fb9d6cc01f9223a@grasehotspot.org>
Reply To: N/A
UTC Datetime: 2013-04-25 18:28:21 UTC
Raw Date: Fri, 26 Apr 2013 01:28:21 -0000

Raw message 

#102: Clarify Kibits vs Kbits in Bandwidth
--------------------------------------+-----------------
 Reporter:  tim                       |      Owner:
     Type:  defect                    |     Status:  new
 Priority:  minor                     |  Milestone:  3.9
Component:  Coova Chilli              |    Version:  3.7
 Keywords:  bandwidth, kbits, kibits  |
--------------------------------------+-----------------
 According to http://forum.pfsense.org/index.php?topic=6679.10;wap2 it
 appears that the Coova bandwidth attributes we use, are doing kbit/s *
 1000 to get bit/s a second, instead of kibit/s * 1024. GUI currently
 assumes kibits.

 Potentially going to the WISPr attributes might be a better solution?

   Chilli vendor specific attributes for setting the maximum bandwidth rate
 in kbits per second. Internally, chilli multiplies this value by 1000 in
 converting to bits per second.
   In all cases, the ChilliSpot vendor specific attributes override WISPr
 attribute values. However, using the WISPr attributes is perhaps the more
 standard way to go.

--
Ticket URL: <http://trac.grasehotspot.org/ticket/102>
GRASE Hotspot <http://grasehotspot.org/>
GRASE Hotspot bug tracker

Thread