40 Mhz channel setting bug on 2.4GHz / RT66U

[richto]

I have noticed that on my RT66U running 374.41 whatever channel I set under Wireless / General / 2.4 GHz - when set to 20/40 or 40MHz mode - the router always only uses channel 6 (according to inSSIDer) regardless of the channel I have chosen - if I switch the router to 20MHZ only mode, then the channel I have actually selected is then used.


I want to be able to use a pair of the recommended adjacent but non interfering channels of 1, 5, 9 or 13 but can't due to this bug. Anyone else see this?

 

[jim769]

Yep been discussed many times i think the only work around is to use 20Mhz only.

 

[saytr79]

I have noticed that on my RT66U running 374.41 whatever channel I set under Wireless / General / 2.4 GHz - when set to 20/40 or 40MHz mode - the router always only uses channel 6 (according to inSSIDer) regardless of the channel I have chosen - if I switch the router to 20MHZ only mode, then the channel I have actually selected is then used.


I want to be able to use a pair of the recommended adjacent but non interfering channels of 1, 5, 9 or 13 but can't due to this bug. Anyone else see this?

I was able to get around this by changing the router from 40MHZ to 20MHZ (saved setting), changed to channel 11 (saved setting), and changed back to 40MHZ (saved setting).

After that my device was / is using 11+9 @ 40MHZ

 

[richto]

Yep been discussed many times i think the only work around is to use 20Mhz only.

Thanks. How come it hasn't been fixed then - is it a closed source driver issue?

 

[jim769]

Thanks. How come it hasn't been fixed then - is it a closed source driver issue?

Good question maybe Merlin could better answer it.

 

[RMerlin]

Sigh. I seem to have to answer that one every couple of weeks

The RT-N66U uses a special driver build that resolves the range/performance issue, and is NOT an official driver. Therefore, it's unlikely anything will ever change with that driver.

 

[richto]

Thanks - so it is a driver issue - understand then.

(I havn't seen this specific issue raised before - and I did try a quick search).

 

[KGB7]

Thanks - so it is a driver issue - understand then.

(I havn't seen this specific issue raised before - and I did try a quick search).

Long search works flawlessly, but its a bit more time consuming.