Gargoyle Forum

I have an older TP-LINK Archer C7 v5 running gargoyle 1.12.0

I'd like to get a wifi connection running across 40mhs on 2.4G. This connection is to a ubiquiti bullet M2.

IT seems as though the router seems to refuse to go into 40MHZ mode. It runs perfectly fine in 20MHz. I have eliminated noise on adjacent channels (for hte most part) and tries 1, 6, and 11

GUI Entries:

Wireless Mode:
Access Point (AP)
2.4GHz Operation Mode:
B+G+N
2.4GHz Channel Width:
40MHz 2nd chan. below
2.4GHz Transmit Power:
Max

24
(0 - 24dBm)
5GHz Operation Mode:
A+N+AC
5GHz Channel Width:
80MHz
5GHz Transmit Power:
Max

30
(0 - 30dBm)
Wireless MAC Filter:
Disabled
AP 2.4GHz SSID:
SALCHHOME

AP 5GHz SSID:
SALCHHOME-5G
Wireless Channel (2.4GHz):
11
Wireless Channel (5GHz):
149
Encryption:
None
Broadcast SSID:
Enabled
Wireless Client Isolation:
Disabled

dsalch wrote: ↑

Fri Jun 13, 2025 12:27 pm

I have eliminated noise on adjacent channels (for hte most part) and tries 1, 6, and 11

viewtopic.php?p=36846&hilit=Noscan#p36846

You can manually add this option to your configuration to test.
Whether you choose to keep it in the configuration is up to you.

Ok, understood. I'd like to try this and see if it is my current problem. I assume this only needs to be set at the router end.

Please excuse my lack of familiarity with the system .. what is the best way to test, and later to permanently implement this change if I so chose?

If you have another wifi device which can have a wifi scanner app installed on it, that would be the best way to verify as you usually get a visual display and you would spot that it is now occupying double channel width.
Otherwise if everything is playing nicely, client negotiated connection speeds should be ~144mbps if I remember correctly instead of 72mbps.

When making this change manually in the /etc/config/wireless, it should remain untouched regardless of what you do in the Gargoyle GUI. We make very few changes to the wifi-device parts of the config file, focusing mostly on wifi-iface.
If you found that it was being overridden, it would require a tweak to the GUI code to add it back in.
I doubt you need to do this though and it should remain until you remove it yourself.