We’re investigating moving toward bursting, but I’ve run into a problem with RADIUS auth on my wireless access points.
Current setup:
- RADIUS auth for wireless APs
- RADIUS auth for DHCP (looking at moving to hotspot)
- Using the Mikrotik-Rate-Limit RADIUS attribute to send rx-rate/tx-rate rx-burst-rate/tx-burst-rate rx-burst-threshold/tx-burst-threshold rx-burst-time/tx-burst-time
When I connect to my test unit via wireless, the Simple Queue is being dynamically created with the correct settings, for max-limit, limit-at, burst-limit, and burst-threshold. However, the AP Tx Limit and Client Tx Limit for the wireless registration are being set to the tx-rate and rx-rate settings, respectively. This results in my test client never bursting above the rx-rate/tx-rate speeds. If I turn off RADIUS Auth for the Wireless AP, the AP Tx Limit & Client Tx Limit don’t get set and bursting works as expected. I’m getting the same behavior in v5.24 and v6.0rc14.
Is there something I can do so that I can use RADIUS for MAC authorization on the wireless but have the wireless disregard the Mikrotik-Rate-Limit attribute?