nikolai petrov

Make Atheros drivers ignore regulatory domain set in EEPROM I found the bottom link https://sites.google.com/site/twisteroidambassador/linux/ath-user-regd "For my purpose I need these two patches: 402-ath_regd_optional.patch and 404-regd_no_assoc_hints.patch. The first one ignores regdomain set in EEPROM, and the second one disables "picking up regulatory domains" from other APs." How can these two patches be included in official images on ARMbian?

After reading I found this link https://wireless.wiki.kernel.org/en/developers/Regulatory/CRDA there is a paragraph that describes my exact case "As an example if your device was programmed for operation in the US which allows operation on channels 1-11 on the 2.4 GHz band and you visit Japan which allows operation on channels 1-14 and you change your regulatory domain to JP you will not be able to use channel 12, 13 or 14 (CCK). But if you have a device programmed for operation in Japan and visit the US and you select US as your regulatory domain you will have channel 12-14 disabled." ----------------------------------------------------------- My WLE900VX programmed for operation in the US in eeprom, I have asked iw reg set BG and in practice I can use the channels that are allowed in the US and BG zones. root@espressobin:/# iw reg get global country BG: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS (5725 - 5875 @ 80), (N/A, 14), (N/A) (57000 - 66000 @ 2160), (N/A, 40), (N/A), NO-OUTDOOR phy#0 country US: DFS-FCC (2402 - 2472 @ 40), (N/A, 30), (N/A) (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 30), (N/A) (57240 - 63720 @ 2160), (N/A, 40), (N/A) I think need to get the driver ath10k to ignore country code in eeprom. For now there I no idea how to achieve it. P.S. I found a solution to the problem I have formulated https://sites.google.com/site/twisteroidambassador/linux/ath-user-regd But now I have another problem, I do not know how to do the actions on the link for Armbian.

Hard Not visible AP See the result of the command: root@espressobin:/# iw wlp0s0 info Interface wlp0s0 ifindex 9 wdev 0x1 addr 04:f0:21:38:c7:3b ssid ARMBIAN type AP wiphy 0 channel 44 (5220 MHz), width: 80 MHz, center1: 5210 MHz txpower 23.00 dBm -------------------------------------- change channel=48 on /etc/hostapd.conf -------------------------------------- root@espressobin:/# /etc/init.d/hostapd restart [ ok ] Restarting hostapd (via systemctl): hostapd.service. -------------------------------------- root@espressobin:/# iw wlp0s0 info Interface wlp0s0 ifindex 9 wdev 0x1 addr 04:f0:21:38:c7:3b type managed wiphy 0 txpower 23.00 dBm ------------------------------------- type NOT AP on cannel 48

tnx Change Stretch to Bionic. I have newest wireless-regdb root@espressobin:~# apt-get install wireless-regdb Reading package lists... Done Building dependency tree Reading state information... Done wireless-regdb is already the newest version (2018.05.09-0ubuntu1~18.04.1). 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. However, the problem remains the same. I create APs only at 36 and 44. I think the limitations are due to the limitations of phy#0 Any ideas for change phy#0 country code? root@espressobin:~# iw reg get global country BG: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS (5725 - 5875 @ 80), (N/A, 14), (N/A) (57000 - 66000 @ 2160), (N/A, 40), (N/A), NO-OUTDOOR phy#0 country US: DFS-FCC (2402 - 2472 @ 40), (N/A, 30), (N/A) (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 30), (N/A) (57240 - 63720 @ 2160), (N/A, 40), (N/A)

root@AP:~# iw list | less Wiphy phy0 max # scan SSIDs: 16 max scan IEs length: 195 bytes max # sched scan SSIDs: 0 max # match sets: 0 max # scan plans: 1 max scan plan interval: -1 max scan plan iterations: 0 Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Device supports RSN-IBSS. Device supports AP-side u-APSD. Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP-128 (00-0f-ac:4) * CMAC (00-0f-ac:6) * CMAC-256 (00-0f-ac:13) * GMAC-128 (00-0f-ac:11) * GMAC-256 (00-0f-ac:12) Available Antennas: TX 0x7 RX 0x7 Configured Antennas: TX 0x7 RX 0x7 Supported interface modes: * managed * AP * monitor * mesh point Band 1: Capabilities: 0x19ef RX LDPC HT20/HT40 SM Power Save disabled RX HT20 SGI RX HT40 SGI TX STBC RX STBC 1-stream Max AMSDU length: 7935 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 8 usec (0x06) HT TX/RX MCS rate indexes supported: 0-23 Bitrates (non-HT): * 1.0 Mbps * 2.0 Mbps (short preamble supported) * 5.5 Mbps (short preamble supported) * 11.0 Mbps (short preamble supported) * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps Frequencies: * 2412 MHz [1] (20.0 dBm) * 2417 MHz [2] (20.0 dBm) * 2422 MHz [3] (20.0 dBm) * 2427 MHz [4] (20.0 dBm) * 2432 MHz [5] (20.0 dBm) * 2437 MHz [6] (20.0 dBm) * 2442 MHz [7] (20.0 dBm) * 2447 MHz [8] (20.0 dBm) * 2452 MHz [9] (20.0 dBm) * 2457 MHz [10] (20.0 dBm) * 2462 MHz [11] (20.0 dBm) * 2467 MHz [12] (disabled) * 2472 MHz [13] (disabled) * 2484 MHz [14] (disabled) Band 2: Capabilities: 0x19ef RX LDPC HT20/HT40 SM Power Save disabled RX HT20 SGI RX HT40 SGI TX STBC RX STBC 1-stream Max AMSDU length: 7935 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 8 usec (0x06) HT TX/RX MCS rate indexes supported: 0-23 VHT Capabilities (0x338001b2): Max MPDU length: 11454 Supported Channel Width: neither 160 nor 80+80 RX LDPC short GI (80 MHz) TX STBC RX antenna pattern consistency TX antenna pattern consistency VHT RX MCS set: 1 streams: MCS 0-9 2 streams: MCS 0-9 3 streams: MCS 0-9 4 streams: not supported 5 streams: not supported 6 streams: not supported 7 streams: not supported 8 streams: not supported VHT RX highest supported: 0 Mbps VHT TX MCS set: 1 streams: MCS 0-9 2 streams: MCS 0-9 3 streams: MCS 0-9 4 streams: not supported 5 streams: not supported 6 streams: not supported 7 streams: not supported 8 streams: not supported VHT TX highest supported: 0 Mbps Bitrates (non-HT): * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps Frequencies: * 5180 MHz [36] (23.0 dBm) * 5200 MHz [40] (23.0 dBm) * 5220 MHz [44] (23.0 dBm) * 5240 MHz [48] (23.0 dBm) * 5260 MHz [52] (20.0 dBm) (radar detection) * 5280 MHz [56] (20.0 dBm) (radar detection) * 5300 MHz [60] (20.0 dBm) (radar detection) * 5320 MHz [64] (20.0 dBm) (radar detection) * 5500 MHz [100] (23.0 dBm) (radar detection) * 5520 MHz [104] (23.0 dBm) (radar detection) * 5540 MHz [108] (23.0 dBm) (radar detection) * 5560 MHz [112] (23.0 dBm) (radar detection) * 5580 MHz [116] (23.0 dBm) (radar detection) * 5600 MHz [120] (23.0 dBm) (radar detection) * 5620 MHz [124] (23.0 dBm) (radar detection) * 5640 MHz [128] (23.0 dBm) (radar detection) * 5660 MHz [132] (23.0 dBm) (radar detection) * 5680 MHz [136] (23.0 dBm) (radar detection) * 5700 MHz [140] (23.0 dBm) (radar detection) * 5720 MHz [144] (disabled) * 5745 MHz [149] (14.0 dBm) * 5765 MHz [153] (14.0 dBm) * 5785 MHz [157] (14.0 dBm) * 5805 MHz [161] (14.0 dBm) * 5825 MHz [165] (14.0 dBm) * 5845 MHz [169] (disabled) Supported commands: * new_interface * set_interface * new_key * start_ap * new_station * new_mpath * set_mesh_config * set_bss * authenticate * associate * deauthenticate * disassociate * join_ibss * join_mesh * remain_on_channel * set_tx_bitrate_mask * frame * frame_wait_cancel * set_wiphy_netns * set_channel * set_wds_peer * probe_client * set_noack_map * register_beacons * start_p2p_device * set_mcast_rate * connect * disconnect * channel_switch * set_qos_map * Unknown command (121) Supported TX frame types: * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 Supported RX frame types: * IBSS: 0x40 0xb0 0xc0 0xd0 * managed: 0x40 0xd0 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * mesh point: 0xb0 0xc0 0xd0 * P2P-client: 0x40 0xd0 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * P2P-device: 0x40 0xd0 software interface modes (can always be added): * monitor valid interface combinations: * #{ AP, mesh point } <= 8, #{ managed } <= 1, total <= 8, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz } HT Capability overrides: * MCS: ff ff ff ff ff ff ff ff ff ff * maximum A-MSDU length * supported channel width * short GI for 40 MHz * max A-MPDU length exponent * min MPDU start spacing Device supports TX status socket option. Device supports HT-IBSS. Device supports SAE with AUTHENTICATE command Device supports scan flush. Device supports AP scan. Device supports per-vif TX power setting Driver supports full state transitions for AP/GO clients Driver supports a userspace MPM Driver/device bandwidth changes during BSS lifetime (AP/GO mode) Device supports static SMPS Device supports configuring vdev MAC-addr on create. Device supports VHT-IBSS. thanks sfx2000 I just put a short sheet on the frequencies above. Here is the full sheet. Do you see anything worrying that limits me only to channels 36 and 44?

root@AP:~# dmesg | grep cfg80211 [ 5.463292] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 5.509242] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 5.511853] cfg80211: failed to load regulatory.db the last row has bothered me -------------------------------------------------------------------------- root@AP:~# apt-get install wireless-regdb ... wireless-regdb is already the newest version (2016.06.10-1). ---------------------------------------------------------------------------- root@AP:~# dpkg -L wireless-regdb /. /lib /lib/crda /lib/crda/regulatory.bin /usr /usr/share /usr/share/doc /usr/share/doc/wireless-regdb /usr/share/doc/wireless-regdb/changelog.Debian.gz /usr/share/doc/wireless-regdb/copyright /usr/share/man /usr/share/man/man5 /usr/share/man/man5/regulatory.bin.5.gz Missing expected rows: /lib/firmware /lib/firmware/regulatory.db /lib/firmware/regulatory.db.p7s For this problem, I found a solution that works for me at the end of: https://forums.kali.org/showthread.php?40049-platform-regulatory-0-firmware-failed-to-load-regulatory-db-(-2)-Error BUT USE OTHER CHANNELS IS FAIL

I set the regulatory domain... root@AP:~# cat /etc/default/crda # Set REGDOMAIN to a ISO/IEC 3166-1 alpha2 country code so that iw(8) may set # the initial regulatory domain setting for IEEE 802.11 devices which operate # on this system. # # Governments assert the right to regulate usage of radio spectrum within # their respective territories so make sure you select a ISO/IEC 3166-1 alpha2 # country code suitable for your location or you may infringe on local # legislature. See `/usr/share/zoneinfo/zone.tab' for a table of timezone # descriptions containing ISO/IEC 3166-1 alpha2 country codes. REGDOMAIN=BG -------------------------------------------------------------------------------------------------- root@AP:~# iw reg get global country BG: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS (5725 - 5875 @ 80), (N/A, 14), (N/A) (57000 - 66000 @ 2160), (N/A, 40), (N/A), NO-OUTDOOR phy#0 country US: DFS-FCC (2402 - 2472 @ 40), (N/A, 30), (N/A) (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 30), (N/A) (57240 - 63720 @ 2160), (N/A, 40), (N/A) -------------------------------------------------------------------------------------------------------- root@AP:~# iwlist wlp0s0 frequency wlp0s0 32 channels in total; available frequencies : Channel 01 : 2.412 GHz Channel 02 : 2.417 GHz Channel 03 : 2.422 GHz Channel 04 : 2.427 GHz Channel 05 : 2.432 GHz Channel 06 : 2.437 GHz Channel 07 : 2.442 GHz Channel 08 : 2.447 GHz Channel 09 : 2.452 GHz Channel 10 : 2.457 GHz Channel 11 : 2.462 GHz Channel 36 : 5.18 GHz Channel 40 : 5.2 GHz Channel 44 : 5.22 GHz Channel 48 : 5.24 GHz Channel 52 : 5.26 GHz Channel 56 : 5.28 GHz Channel 60 : 5.3 GHz Channel 64 : 5.32 GHz Channel 100 : 5.5 GHz Channel 104 : 5.52 GHz Channel 108 : 5.54 GHz Channel 112 : 5.56 GHz Channel 116 : 5.58 GHz Channel 120 : 5.6 GHz Channel 124 : 5.62 GHz Channel 128 : 5.64 GHz Channel 132 : 5.66 GHz Channel 136 : 5.68 GHz Channel 140 : 5.7 GHz Channel 149 : 5.745 GHz Channel 153 : 5.765 GHz I tested all available frequencies in 5Ghz, but only works in 30 and 44 channels. And now I do not know what to do? Those of 100 to 140 are very tempting because of 160 Mhz flame. P.S. I use wifi card WLE900VX with 3 inbox antennas uder 5 dbm 2.4/5Ghz. I have 2 identical devices at a distance of 4 meters across a brick wall and a test of 36 and 44 channels can achieve the following speeds: iperf3 -c 172.24.1.1 -P 16 ... [SUM] 0.00-10.01 sec 237 MBytes 199 Mbits/sec 0 sender [SUM] 0.00-10.01 sec 211 MBytes 177 Mbits/sec receiver

I copied the image of the USB flash. Boot of him. I had an image on USB flash, which I copy to an emmc espressobin. Boot from emmc and everything is ok. ----------------------------------------------- U-Boot 2017.03-armada-17.10.2-g14aeedc (Jun 01 2018 - 15:39:10 +0800) ----------------------------------------------- Linux espressobin 4.18.16-mvebu64 #402 SMP PREEMPT Fri Oct 26 17:23:18 CEST 2018 aarch64 GNU/Linux

I have Espressobin v7 1G and PCIe card WLE900VX. With armbian-config create AP. Starts successfully on 36 channels. I tried all the channels in 5Ghz, but works only successfully at 36 and 44. By selecting another channel tells me after trying that I can not start AP on 5Ghz and start at 2GHz successfull. Any idea how to deal with this?