5GHz not working

That makes sense indeed. What about the “40”? What does that mean…the 40 Mhz? If so, does that mean 20 MHz is not supported?

(2402 - 2482 @ 40), (N/A, 20), (N/A)

I understand it that its the max channel width available in 2,4GHz (as you can see 80 or 160 lower for 5GHz)

you can see it also on the wiki link I’ve send in my previous post

1 Like

Thanks, that also makes sense. And indeed some 5 GHz channels support up to 160 MHz, while others are limited to 80 MHz. Learned something new today :slight_smile:

Yes, it should work.

Oke, i found something new just now about the whole “5 GHz not working”

When this occurs, the wlan0 is just being turned off for starters when looking to the output of “ifconfig”. I turned it back on still it stayed like that. Then i looked at the log.

2016-11-23T15:29:50+01:00 crit dnsmasq[24284]: bad dhcp-option at line 32 of /var/etc/dnsmasq.conf
2016-11-23T15:29:50+01:00 crit dnsmasq[24284]: FAILED to start up
2016-11-23T15:29:50+01:00 notice netifd[]: radio0 (24335): command failed: Not supported (-95)
2016-11-23T15:29:50+01:00 notice netifd[]: radio0 (24335): Configuration file: /var/run/hostapd-phy0.conf
2016-11-23T15:29:51+01:00 notice netifd[]: radio0 (24335): wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
2016-11-23T16:29:51+01:00 info kernel[]: [ 2987.767382] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
2016-11-23T15:29:51+01:00 notice netifd[]: radio0 (24335): wlan0: interface state COUNTRY_UPDATE->HT_SCAN
2016-11-23T15:29:52+01:00 notice netifd[]: radio0 (24335): wlan0: interface state HT_SCAN->DFS
2016-11-23T15:29:52+01:00 notice netifd[]: radio0 (24335): wlan0: DFS-CAC-START freq=5500 chan=100 sec_chan=1, width=1, seg0=106, seg1=0, cac_time=60s
2016-11-23T15:30:01+01:00 info cron[24580]: (root) CMD (   /usr/bin/notifier)
2016-11-23T15:30:01+01:00 info cron[24576]: (root) CMD (/usr/bin/get-api-crl)
2016-11-23T15:30:01+01:00 info cron[24582]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2016-11-23T15:30:01+01:00 info cron[24583]: (root) CMD (majordomo_db.sh downsize)
2016-11-23T15:30:01+01:00 info cron[24588]: (root) CMD (nethist_stats.lua)
2016-11-23T15:30:01+01:00 info cron[24584]: (root) CMD (/usr/bin/watchdog.sh)
2016-11-23T15:30:02+01:00 warning watchdog[]: Restarted nethist
2016-11-23T15:30:24+01:00 crit dnsmasq[25109]: bad dhcp-option at line 32 of /var/etc/dnsmasq.conf
2016-11-23T15:30:24+01:00 crit dnsmasq[25109]: FAILED to start up
2016-11-23T15:30:34+01:00 notice netifd[]: radio0 (25372): command failed: Not supported (-95)
2016-11-23T15:30:34+01:00 notice netifd[]: radio0 (25372): Configuration file: /var/run/hostapd-phy0.conf
2016-11-23T15:30:35+01:00 notice netifd[]: radio0 (25372): nl80211: Could not configure driver mode
2016-11-23T15:30:35+01:00 notice netifd[]: radio0 (25372): nl80211: deinit ifname=wlan0 disabled_11b_rates=0
2016-11-23T15:30:35+01:00 notice netifd[]: radio0 (25372): nl80211 driver initialization failed.
2016-11-23T15:30:35+01:00 notice netifd[]: radio0 (25372): wlan0: interface state UNINITIALIZED->DISABLED
2016-11-23T15:30:35+01:00 notice netifd[]: radio0 (25372): wlan0: AP-DISABLED 
2016-11-23T15:30:35+01:00 notice netifd[]: radio0 (25372): hostapd_free_hapd_data: Interface wlan0 wasn't started
2016-11-23T15:30:35+01:00 notice netifd[]: radio0 (25372): Device setup failed: HOSTAPD_START_FAILED
2016-11-23T15:30:45+01:00 notice netifd[]: radio0 (25514): command failed: Not supported (-95)
2016-11-23T15:30:45+01:00 notice netifd[]: radio0 (25514): Configuration file: /var/run/hostapd-phy0.conf
2016-11-23T15:30:47+01:00 notice netifd[]: radio0 (25514): nl80211: Could not configure driver mode
2016-11-23T15:30:47+01:00 notice netifd[]: radio0 (25514): nl80211: deinit ifname=wlan0 disabled_11b_rates=0
2016-11-23T15:30:47+01:00 notice netifd[]: radio0 (25514): nl80211 driver initialization failed.
2016-11-23T15:30:47+01:00 notice netifd[]: radio0 (25514): wlan0: interface state UNINITIALIZED->DISABLED
2016-11-23T15:30:47+01:00 notice netifd[]: radio0 (25514): wlan0: AP-DISABLED 
2016-11-23T15:30:47+01:00 notice netifd[]: radio0 (25514): hostapd_free_hapd_data: Interface wlan0 wasn't started
2016-11-23T15:30:47+01:00 notice netifd[]: radio0 (25514): Device setup failed: HOSTAPD_START_FAILED
2016-11-23T15:31:01+01:00 info cron[25698]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2016-11-23T15:32:01+01:00 info cron[26144]: (root) CMD (nethist_stats.lua)
2016-11-23T15:32:01+01:00 info cron[26145]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2016-11-23T15:33:01+01:00 info cron[26591]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2016-11-23T16:33:58+01:00 info kernel[]: [ 3234.937064] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
2016-11-23T15:34:01+01:00 info cron[27118]: (root) CMD (nethist_stats.lua)
2016-11-23T15:34:01+01:00 info cron[27119]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2016-11-23T16:34:01+01:00 warning kernel[]: [ 3237.692945] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:01+01:00 warning kernel[]: [ 3237.696829] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:01+01:00 warning kernel[]: [ 3237.697934] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:05+01:00 warning kernel[]: [ 3241.516215] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:05+01:00 warning kernel[]: [ 3241.522510] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:05+01:00 warning kernel[]: [ 3241.534860] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:05+01:00 warning kernel[]: [ 3241.569156] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:05+01:00 warning kernel[]: [ 3241.629899] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:15+01:00 warning kernel[]: [ 3251.640272] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:16+01:00 warning kernel[]: [ 3252.156645] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:21+01:00 warning kernel[]: [ 3257.712859] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:22+01:00 warning kernel[]: [ 3258.114029] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:22+01:00 warning kernel[]: [ 3258.712755] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:25+01:00 warning kernel[]: [ 3261.857964] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:31+01:00 warning kernel[]: [ 3267.678094] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:35+01:00 warning kernel[]: [ 3271.913929] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:36+01:00 warning kernel[]: [ 3272.230981] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:42+01:00 warning kernel[]: [ 3278.109371] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T15:34:45+01:00 crit dnsmasq[27989]: bad dhcp-option at line 32 of /var/etc/dnsmasq.conf
2016-11-23T15:34:45+01:00 crit dnsmasq[27989]: FAILED to start up
2016-11-23T16:34:45+01:00 warning kernel[]: [ 3281.762977] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:46+01:00 warning kernel[]: [ 3282.007864] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:46+01:00 warning kernel[]: [ 3282.007989] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:51+01:00 warning kernel[]: [ 3287.509135] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:56+01:00 warning kernel[]: [ 3292.003104] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:56+01:00 warning kernel[]: [ 3292.197228] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:34:58+01:00 warning kernel[]: [ 3294.460506] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:35:00+01:00 warning kernel[]: [ 3296.001838] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T15:35:01+01:00 info cron[28281]: (root) CMD (   /usr/bin/notifier)
2016-11-23T15:35:01+01:00 info cron[28284]: (root) CMD (majordomo_db.sh downsize)
2016-11-23T15:35:01+01:00 info cron[28283]: (root) CMD (/usr/bin/watchdog.sh)
2016-11-23T15:35:01+01:00 info cron[28285]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2016-11-23T16:35:02+01:00 warning kernel[]: [ 3298.106200] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:35:06+01:00 warning kernel[]: [ 3302.202198] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:35:21+01:00 warning kernel[]: [ 3317.906998] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:35:26+01:00 warning kernel[]: [ 3322.511091] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:35:26+01:00 warning kernel[]: [ 3322.527363] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:35:26+01:00 warning kernel[]: [ 3322.530290] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:35:26+01:00 warning kernel[]: [ 3322.548770] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:35:26+01:00 warning kernel[]: [ 3322.563622] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:35:26+01:00 warning kernel[]: [ 3322.580202] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:35:31+01:00 warning kernel[]: [ 3327.756924] ath10k_warn: 16 callbacks suppressed
2016-11-23T16:35:31+01:00 warning kernel[]: [ 3327.756936] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:35:32+01:00 warning kernel[]: [ 3328.351312] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:35:33+01:00 warning kernel[]: [ 3329.232150] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T15:35:33+01:00 crit dnsmasq[28695]: bad dhcp-option at line 32 of /var/etc/dnsmasq.conf
2016-11-23T15:35:33+01:00 crit dnsmasq[28695]: FAILED to start up
2016-11-23T16:35:36+01:00 warning kernel[]: [ 3332.304731] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:35:45+01:00 warning kernel[]: [ 3341.209564] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:35:53+01:00 warning kernel[]: [ 3349.445227] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:35:54+01:00 warning kernel[]: [ 3350.310204] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T15:36:01+01:00 info cron[28916]: (root) CMD (nethist_stats.lua)
2016-11-23T15:36:01+01:00 info cron[28917]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2016-11-23T16:36:02+01:00 warning kernel[]: [ 3358.058235] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:36:02+01:00 warning kernel[]: [ 3358.059844] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:36:17+01:00 warning kernel[]: [ 3373.506196] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:36:30+01:00 warning kernel[]: [ 3386.606459] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:36:34+01:00 warning kernel[]: [ 3390.602292] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T16:36:48+01:00 warning kernel[]: [ 3404.004033] ath10k_pci 0000:02:00.0: no channel configured; ignoring frame(s)!
2016-11-23T15:37:01+01:00 info cron[29241]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2016-11-23T15:38:01+01:00 info cron[29711]: (root) CMD (nethist_stats.lua)
2016-11-23T15:38:01+01:00 info cron[29712]: (root) CMD (/usr/bin/rainbow_button_sync.sh)

However this is my wireless config file.

config wifi-device 'radio0'
        option type 'mac80211'
        option path 'platform/soc/soc:pcie-controller/pci0000:00/0000:00:02.0/0000:02:00.0'
        option hwmode '11a'
        option country 'NL'
        option htmode 'VHT80'
        option txpower '19'
        option channel '36'

config wifi-device 'radio1'
        option type 'mac80211'
        option hwmode '11g'
        option path 'platform/soc/soc:pcie-controller/pci0000:00/0000:00:03.0/0000:03:00.0'
        option htmode 'HT20'
        option txpower '19'
        option channel 'auto'
        option country 'NL'

config wifi-iface
        option ssid '<DELETED>'
        option device 'radio1'
        option mode 'sta'
        option bssid '<DELETED>'
        option key '<DELETED>'
        option network '<DELETED> wan'
        option hidden '0'
        option encryption 'psk2+tkip+aes'

config wifi-iface
        option device 'radio0'
        option mode 'ap'
        option ssid '<DELETED>'
        option key '<DELETED>'
        option encryption 'psk2+tkip+aes'

config wifi-device 'radio2'
        option type 'mac80211'
        option channel '11'
        option hwmode '11g'
        option path 'platform/soc/soc:internal-regs/f10f8000.usb3/usb4/4-1/4-1:1.0'
        option country 'NL'
        option htmode 'HT20'
        option txpower '20'

I am having the same problem. It seems to be a driver issue. Has anyone found a solution? I can’t get 5Ghz to work at all.

Im having the same problem as well. I got it to work briefly (as in once, for about 15 minutes), but nothing seems to get it to work consistently. Ive reseated the card like 5 times to no avail.

Is there any command to see if the OS can “see” the card?? Im trying to understand if this is a hw or driver problem.

HELP???


JohnC

Do an ‘lspci’ first to see if it appears on the PCI bus.
If it shows up there, do ‘iw phy | grep Wiphy’ to see if it’s recognizing them both as wireless devices.

You need to install pciutils which provides the tool lspci.
You can do it via Luci under System -> Software.
Update list first and then look for pciutils under available packages and install it.

Or you can do it using opkg from the terminal:

opkg update
opkg install pciutils

Then run lspci. When both cards are recognized you should see something like this:

lspci
00:01.0 PCI bridge: Marvell Technology Group Ltd. Device 6820 (rev 04)
00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6820 (rev 04)
00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6820 (rev 04)
01:00.0 Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) (rev 01)
02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter

@jimmy try to set the right country code in the wireless settings in Luci.
It has helped me at least.

Thanks for the install tip. It seems the other card is not visible. I have an ssd installed and it is working. Ill try to do some bisecting tomorrow and remove the ssd and see if the wifi card becomes visible…

root@turris:~# lspci
00:01.0 PCI bridge: Marvell Technology Group Ltd. Device 6820 (rev 04)
00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6820 (rev 04)
00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6820 (rev 04)
03:00.0 Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) (rev 01)
root@turris:~#

I did receive a reply from support. They told me to send back the card to replace the card. Hope that will work.

Thanks, I have done this. What helped was setting the correct channel according to the link someone else posted above (https://w.wol.ph/2015/08/28/maximum-wifi-transmission-power-country/), but the card still disappears if I make any adjustments to its settings. It will only reappear on a reboot.

I posted that URL but i am also not sure about all that to be honest. I also experienced a lot of trouble.

Since then i have just used

iw reg set NL
(NL being the Netherlands)
In the rc.local just in case it wants to switch back to CZ. Also in
/etc/config/wireless

I have changed the country in the radio 0 section to “NL” (my country). After doing all those things, i still had problems. I then just put it on channel 36 and kept it on that. The TX-power isn’t that spectacular, because of restrictions on that channel. I am having a MAX TX-power of 20 dBm (100 mW), however the 5 GHz card only supports up to 21 dBm so i am not missing out that much.

Try to also set it on channel 36 and see how it goes. That way you will not be having problems with channel-hopping because of external influences such as weather-radars.

I think I may have found something that could affect some users using 802.11ac

https://wireless.wiki.kernel.org/en/users/drivers/ath10k/configuration#configuring_hostapd

Current implementation of ath radar pattern detector supports only ETSI regulatory domain. It means radar detection works only when master region is set to ETSI. It can be done by setting regulatory domain to country from Europe (DE, FI, FR, PL, …):

Other regulatory domains like JP (Japan), US (FCC master region) are currently not supported. Starting AP on DFS channel in DFS master region different that ETSI will cause radar event at first suspicious RF signal even it was not radar.

I’m in AU and having problems with the wifi in general on the Omnia. Changing settings on the 5 GHz channel sometimes stops the interface from coming back up without a soft restart, so I think that might be something different entirely.

Does anyone know what the current (3.2.1 Turris OS) ath10k driver and firmware version are?
The following command should print out the required information.

sudo ethtool -i wlan0

I think this is the ath10k driver branch in use on the Omnia.

1 Like

About the version…

There are two packages installed regarding ath10k-firmware

root@K-Router:/etc# opkg files ath10k-firmware-qca988x
Package ath10k-firmware-qca988x (2014-10-28-7d14e337ad25c0ef3e78fc47eac336697ca612e8-1) is installed on root and has the following files:
/lib/firmware/ath10k/QCA988X/hw2.0/firmware-5.bin
/lib/firmware/ath10k/QCA988X/hw2.0/board.bin

root@K-Router:/lib/firmware/ath10k/QCA988X/hw2.0# opkg info ath10k-firmware-qca9
88x
Package: ath10k-firmware-qca988x
Version: 2014-10-28-7d14e337ad25c0ef3e78fc47eac336697ca612e8-1
Depends: libc, kmod-ath10k
Status: install user installed
Section: kernel
Architecture: mvebu
Maintainer: Felix Fietkau <nbd@openwrt.org>
MD5Sum: e5ae790903b779c7bb7f37e09abe8bb2
Size: 216569
Filename: ath10k-firmware-qca988x_2014-10-28-7d14e337ad25c0ef3e78fc47eac336697ca612e8-1_mvebu.ipk
Source: package/firmware/ath10k-firmware
Description: ath10k firmware for QCA988x devices
Installed-Time: 1473084997

root@K-Router:/etc# opkg files kmod-ath10k
Package kmod-ath10k (4.4.13+2015-12-03-3-05df79f63527051ea0071350f86faf76-9) is installed on root and has the following files:
/lib/modules/4.4.13-05df79f63527051ea0071350f86faf76-9/ath10k_core.ko
/etc/modules.d/55-ath10k
/lib/modules/4.4.13-05df79f63527051ea0071350f86faf76-9/ath10k_pci.ko

root@K-Router:/lib/firmware/ath10k/QCA988X/hw2.0# opkg info kmod-ath10k
Package: kmod-ath10k
Version: 4.4.13+2015-12-03-3-05df79f63527051ea0071350f86faf76-9
Depends: kernel (= 4.4.13-1-05df79f63527051ea0071350f86faf76-9), kmod-ath
Status: install user installed
Section: kernel
Architecture: mvebu
Maintainer: Felix Fietkau <nbd@openwrt.org>
MD5Sum: 74cf884cfd8e32d329a01ccbf0ba42dc
Size: 129718
Filename: kmod-ath10k_4.4.13+2015-12-03-3-05df79f63527051ea0071350f86faf76-9_mvebu.ipk
Source: package/kernel/mac80211
Description: This module adds support for wireless adapters based on
 Atheros IEEE 802.11ac family of chipsets. For now only
 PCI is supported.
Installed-Time: 1480282069

If you open

vi /lib/firmware/ath10k/QCA988X/hw2.0/firmware-5.bin

This is what you at least can “read”…10.2.4.70

So we can assume that we are on the *.70 branche. There is also a 2, so maybe is referring to that exact version.

there’s a common issue with the 5GHz card - it’s not recognized when the system is warm-started (i.e. after a reboot). Try to completely unplug your router from the power, leave it unplugged for 20 minutes, and then plug it back in. See lspci if it’s recognized.
In my case, this issue is 100% reproductible.
If it doesn’t work even after this, your card might be faulty.

Same case as @ssl here. After reboot the 5GHz card it’s not recognized, after full power cycle the 5GHz card it’s recognized (I have a SSD mSATA installed)

I have you checked how much power the SSD mSATA card takes? More than 3.6W?

I have tested today also a bit with the 5 GHz settings. For the people who are NOT aware of the certain channels available for your wifi card.

https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2016.06.10.tar.xz

extract this file and open “db.txt”.

There you can see the settings. This is the latest reg regulations for each country.

As an example to take the Netherlands:

country NL: DFS-ETSI
	(2402 - 2482 @ 40), (20)
	(5170 - 5250 @ 80), (20), NO-OUTDOOR, AUTO-BW
	(5250 - 5330 @ 80), (20), NO-OUTDOOR, DFS, AUTO-BW
	(5490 - 5710 @ 160), (27), DFS
	# short range devices (ETSI EN 300 440-1)
	(5725 - 5875 @ 80), (25 mW)
	# 60 GHz band channels 1-4, ref: Etsi En 302 567
	(57000 - 66000 @ 2160), (40)
  • Line 1: (2402 - 2482 @ 40), (20) - translates as: All the channels on the 2.4 GHz (channels 1-13) can function at width 40 with tx-power of max 20.

  • line 2: (5170 - 5250 @ 80), (20) - translates as: Channels on the 5 GHz (channel 36-48) can function at 80 width with tx-power of max 20.

  • line 3: (5250 - 5330 @ 80), (20) - translates as: Channels on the 5 GHz (channels 52-64) can function at 80 width with tx-power of max 20.

  • line 4: (5490 - 5710 @ 160), (27), - Translates as: Channels on the 5 GHz (channels 100-140) can function at 160 width with tx-power of max 27. Keep in mind to avoid channels 120, 124, 128. These channels are used by weather-radar. You can use them, but there is a BIG chance the 5GHz card will hop to another channel that may not even be supported by the country and thus not visible for your devices For example a two weeks ago or so, i experienced this with my smartphone not seeing the 5GHz wifi-network, because it hopped to channel 149, which is not supported in the Netherlands.

  • last line: # 60 GHz band channels 1-4, ref: Etsi En 302 567 (57000 - 66000 @ 2160), (40) - translates as: The 60GHz band is as far as i know used for 802.11AD. Devices that support 802.11AD aren’t that many right now.

Keep the tx-power in mind, i have set it higher and also then it does not work. As long as you keep it on the regulations, things should work.