3.7 bug: opposite Ap/client tx limit

I use mac authentication on the Ap to get the rate for each client.

This is a common reply radius attribute I use: “Ascend-Data-Rate=1900000,Ascend-Xmit-Rate=1080000”

From 2.9.xx up to 3.6 that string generated an AP TX limit of 1900kbps and a client tx limit of 1080kbps.

From 3.7 it generates the follwing limits: Ap TX limit=1080kbps and client tx limit=1900kbps
It is not only a cosmetic bug but a really one, infact the cliente are not able to download more then a megabitpersecond.

Giving the fact that no one reported the changes i think it is a bug.

So please correct it asap.

Regards
Ros

any confirmation from MT guys?

regards
Ros