Tech Focus
Regular Contributor
Up until recently, I have been relying on auto channel selection by my router/access points. However, I know there are many experienced network user talks about 1, 6 and 11 for 2.4 GHz. The reasoning here makes total sense, which is because these 3 are only channels that do not overlap in 2.4 GHz 20 MHz channel width setting.
The part I am still not convinced/understand is the whole point of above is to avoid adjacent channel interference. So I believe the true goal should be finding a channel that has minimum interference. Let me illustrates this by couple example.
Case 1
Let's say, this is is what I see from my neighbors. Clearly Channel 6 is the most saturated/utilized. Based on 1, 6 and 11 rule, if I had a two APs, I would have easy time choosing as only 2 channels left after 6 are 1 and 11.
But technically speaking (may be a bit hard see on this image), channel 8, 9 and even 10 are less congested/utilized than channel 11. All those channels won't overlap with channel 1 that I am about to use. So if I go by congestion/utilization those channels look to be a better option.
Non-overlap rule: 1 & 11
Least utilized rule: 1 & 8/9/10
Case 2
Here Channel 6 is wide open and if I have one AP, it make sense to use it. But if I have two APs, I feel 3 & 8 (two are non-overlapping channel) is better because if I use channel 1 and 6, 1 is more congested than either 3 or 8.
Non-overlap rule: 1 and 6.
Least utilized rule: 3 and 8
So I feel like in an ideal world, every neighbor are elite students and follow 1,6 and 11 rule, then everyone should be using one of those channel perhaps but as soon as someone starts to violate the rule, utilization/congestion are harder to predict.
One question I have is which one would be considered a better practice, for situation like if I had 3 APs, say left, middle and right in home. Based on less congestion, choosing 1, 6 and 1 where two of own APs are using the same channels or forcefully separating all 3 own AP and use 1, 6 and 11 even if I know 11 is congested/more utilized.
I'd appreciate if there is a good reference/test someone has performed for congestion/utilization based vs. non-overlapping based channel setting practice.
Thanks
The part I am still not convinced/understand is the whole point of above is to avoid adjacent channel interference. So I believe the true goal should be finding a channel that has minimum interference. Let me illustrates this by couple example.
Case 1
Let's say, this is is what I see from my neighbors. Clearly Channel 6 is the most saturated/utilized. Based on 1, 6 and 11 rule, if I had a two APs, I would have easy time choosing as only 2 channels left after 6 are 1 and 11.
But technically speaking (may be a bit hard see on this image), channel 8, 9 and even 10 are less congested/utilized than channel 11. All those channels won't overlap with channel 1 that I am about to use. So if I go by congestion/utilization those channels look to be a better option.
Non-overlap rule: 1 & 11
Least utilized rule: 1 & 8/9/10
Case 2
Here Channel 6 is wide open and if I have one AP, it make sense to use it. But if I have two APs, I feel 3 & 8 (two are non-overlapping channel) is better because if I use channel 1 and 6, 1 is more congested than either 3 or 8.
Non-overlap rule: 1 and 6.
Least utilized rule: 3 and 8
So I feel like in an ideal world, every neighbor are elite students and follow 1,6 and 11 rule, then everyone should be using one of those channel perhaps but as soon as someone starts to violate the rule, utilization/congestion are harder to predict.
One question I have is which one would be considered a better practice, for situation like if I had 3 APs, say left, middle and right in home. Based on less congestion, choosing 1, 6 and 1 where two of own APs are using the same channels or forcefully separating all 3 own AP and use 1, 6 and 11 even if I know 11 is congested/more utilized.
I'd appreciate if there is a good reference/test someone has performed for congestion/utilization based vs. non-overlapping based channel setting practice.
Thanks
Last edited: