Actions
Bug #8097
closed
Captive Portal RADIUS bw_up/bw_down can feed a non-integer value to ipfw, resulting in incorrectly parsed throughput values
Start date:
11/15/2017
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.x
Affected Architecture:
All
Description
The Limiter GUI and Captive Portal GUI locations to set bandwidth up/down enforce that the bandwidth value must be an integer, but if a value is given in a reply attribute from RADIUS, it is divided by 1000 which can lead to a non-integer float value passed to ipfw.
When this happens, ipfw appears to ignore anything after the decimal place and also ignores the bandwidth scale. For example, when passed "200.50Kbit/s", the resulting pipe ends up as 200 bits/s in the "ipfw pipe show" output. Due to the low throughput on the pipe, it appears as though the user has no connectivity.
Rounding the value to the nearest integer appears to correct the problem.
Updated by
Actions