Why you should NEVER select channel 165 in 5 GHz

[duckware]

Why should you never ever select channel 165 for 5 GHz for your home Netgear router?

I stumbled upon this doing some testing, and it makes perfect sense, but it is bizarre.

A solution checkbox is waiting for the first correct answer.

[duckware · Accepted solution]

Because when channel 165 is selected, connecting wifi clients will be forced to use a 20 MHz channel.  Example: the fastest PHY *any* 2x2 client can connect to the (channel 165) router is 173.3 Mbps -- instead of the normal 866.6 Mbps (you only get 20% of the PHY speed you expected).

When a 5 GHz channel is selected in the router interface, you are only selecting the primary 20 MHz channel -- and letting the router automatically pick the 160/80/40 channels (that overlap that primary channel).  However, channel 165 has *NO* overlapping 160/80/40 channels.  So any client connecting to the router (using channel 165) will be forced to connect in only 20 MHz channel mode -- even when the router is configured to use the highest possible 'Mode' (the widest channels).

[duckware · Accepted solution]

Because when channel 165 is selected, connecting wifi clients will be forced to use a 20 MHz channel.  Example: the fastest PHY *any* 2x2 client can connect to the (channel 165) router is 173.3 Mbps -- instead of the normal 866.6 Mbps (you only get 20% of the PHY speed you expected).

When a 5 GHz channel is selected in the router interface, you are only selecting the primary 20 MHz channel -- and letting the router automatically pick the 160/80/40 channels (that overlap that primary channel).  However, channel 165 has *NO* overlapping 160/80/40 channels.  So any client connecting to the router (using channel 165) will be forced to connect in only 20 MHz channel mode -- even when the router is configured to use the highest possible 'Mode' (the widest channels).