MrSinatra
Occasional Visitor
hi,
sorry if this is already reported. i have seen it in older firmwares as well.
i have the .9135 fw on the RT-AC66 and overall i like it. however there still is a bug which has been there for the past few versions. i use win7 with Chrome browser, but issue exists in IE as well.
when you click "Wireless" on the lefthand side, the first option on the right at the top is "Band" and you are supposed to be able to choose 5ghz or 2.4ghz. mine showed 5ghz, and when clicked, no other options! so 2.4 configs were not available!
i did eventually find a workaround. if you choose "Network Map" on the lefthand side, and then choose the 2.4 tab on the system status column, and then do back to "Wireless" the 2.4 config options now show! however, now the 5ghz can't be seen or clicked at "Band" ...the issue exists on the professional tab as well.
this is very obviously, imo, a bug of the fw UI, and even though i found this workaround, i think it should be fixed as it greatly impacts function, esp for those who are ignorant of the workaround.
i would love to hear if anyone else has experienced this issue? thx.
sorry if this is already reported. i have seen it in older firmwares as well.
i have the .9135 fw on the RT-AC66 and overall i like it. however there still is a bug which has been there for the past few versions. i use win7 with Chrome browser, but issue exists in IE as well.
when you click "Wireless" on the lefthand side, the first option on the right at the top is "Band" and you are supposed to be able to choose 5ghz or 2.4ghz. mine showed 5ghz, and when clicked, no other options! so 2.4 configs were not available!
i did eventually find a workaround. if you choose "Network Map" on the lefthand side, and then choose the 2.4 tab on the system status column, and then do back to "Wireless" the 2.4 config options now show! however, now the 5ghz can't be seen or clicked at "Band" ...the issue exists on the professional tab as well.
this is very obviously, imo, a bug of the fw UI, and even though i found this workaround, i think it should be fixed as it greatly impacts function, esp for those who are ignorant of the workaround.
i would love to hear if anyone else has experienced this issue? thx.