I have two GrooveA 52HPn with ROS 5.25 and I would like to force them to stay at a MCS. It’s quite basic but after many invests I didn’t find any solution to prevent the MCS from changing even if I specified the ht-basics-mcs and the ht-supported-mcs.
Paste this on your board, if the name of wlan is not wlan1 change each occurrence accordingly:
/interface wireless
set wlan1 rate-selection=advanced rate-set=configured basic-rates-b="" supported-rates-b="" basic-rates-a/g="" supported-rates-a/g="";
set wlan1 ht-basic-mcs=mcs-0,mcs-1,mcs-2,mcs-3,mcs-4,mcs-5,mcs-6,mcs-7 ht-supported-mcs="mcs-0,mcs-1,mcs-2,mcs-3,mcs-4,mcs-5,mcs-6,mcs-7,mcs-8,mcs-9,mcs-10,mcs-11,mcs-12,mcs-13,mcs-14,mcs-15,mcs-16,mcs-17,mcs-18,mcs-19,mcs-20,mcs-21,mcs-22,mcs-23";
:if ( [ :find [ /interface wireless info get wlan1 supported-bands ] "2ghz-n" -1 ] >= 0 ) do={
set wlan1 band=2ghz-onlyn;
};
:if ( [ :find [ /interface wireless info get wlan1 supported-bands ] "5ghz-n" -1 ] >= 0 ) do={
set wlan1 band=5ghz-onlyn;
};
But if you would force mcs because the device do not go to MCS remember: not go to MCS because noise environment… if you force MCS do not solve anything
Thanks for the answers.
We’ve successfully locked on n band and so on HT MCS. The problem we’re facing is now to lock on a given mcs, let’s say mcs-0. We’ve limited both basic and supported mcs to mcs-0 and we’re experiencing switches to mcs-1 or 2 … which shouldn’t happen. Any idea of the cause ?
We’re using groove A-52HPn so we’ve only updated to 5.26 and so far no progress… We’ve tried to limit the power on unwanted HT-MCS but can’t make it works. Does it seem a convenient approach ? Any other idea or hack to force the MCS ? We can provide any information necessary, just ask
You were given both viable options - one to configure what basic-rates, and rates to set up, second, do not worry regarding what MCS is used as the best possible rate will be selected by RouterOS. If you want to limit maximal available rates you have to go rextended way and deselect higher rates.
Trying to limit that setting tx-power manually is wrong.