You can indeed set these channels with 'iw'.
First find out the capabiltiies of your chipset with
Then:
iw dev wlan0 set channel 36 HT80
That should be it.
Ok, here's relevant output from iw phy:
valid interface combinations:
* #{ managed } <= 1, #{ AP, mesh point } <= 16,
total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz
80 MHz is clearly there. FYI, this is phy0 (wlan0), the 5 GHz radio. Here's the help output from iw when using the command you suggest:
root@OpenWrt ~# iw dev wlan0 set channel 36 HT80
Usage: iw [options] dev <devname> set channel <channel> [HT20|HT40+|HT40-]
Options:
--debug enable netlink debugging
Clearly, the command doesn't like the HT80 syntax. 11ac is the "very" high throughput phy, so perhaps "VHT80" works:
root@OpenWrt ~# iw dev wlan0 set channel 36 VHT80
Usage: iw [options] dev <devname> set channel <channel> [HT20|HT40+|HT40-]
Options:
--debug enable netlink debugging
Nope. Here's what the iw command says about setting channel/frequency in its help when you type a wrong command:
dev <devname> set channel <channel> [HT20|HT40+|HT40-]
phy <phyname> set channel <channel> [HT20|HT40+|HT40-]
dev <devname> set freq <freq> [HT20|HT40+|HT40-]
dev <devname> set freq <control freq> [20|40|80|80+80|160] [<center freq 1>] [<center freq 2>]
phy <phyname> set freq <freq> [HT20|HT40+|HT40-]
Set frequency/channel the hardware is using, including HT
configuration.
So I tried just "80":
root@OpenWrt ~# iw dev wlan0 set channel 36 80
command failed: Invalid argument (-22)
Same result if I try to use the frequency as in
root@OpenWrt ~# iw dev wlan0 set freq 5220 80
command failed: Invalid argument (-22)
My guess is this is the right way to specify in iw, but that the driver is rejecting the values. FYI, I'm running DD from http://luci.subsignal.org/~trondah/c2600/r49005/
Charles
