You are not logged in.
I'm using the create_ap script from the AUR to create a software access point using my laptop, but I cannot create an AP that broadcasts on any channel above 11 or on any 5Ghz channels. My laptop is a gaming laptop from the US, but I want to use channel 13 since I'm outside the US at the moment. My regulatory domain is set to 00 at boot. I've tried changing my regulatory domain to GB using iw, but the channels are still unusable, so I modified my regulatory.bin to have the following.
country 00: DFS-UNSET
(2402.000 - 2495.000 @ 40.000), (30.00), (N/A)
(5170.000 - 5250.000 @ 80.000), (17.00), (N/A), AUTO-BW
(5250.000 - 5330.000 @ 80.000), (23.00), (N/A), DFS, AUTO-BW
(5490.000 - 5600.000 @ 80.000), (23.00), (N/A), DFS
(5650.000 - 5710.000 @ 40.000), (23.00), (N/A), DFS
(5735.000 - 5835.000 @ 80.000), (30.00), (N/A)
(57240.000 - 63720.000 @ 2160.000), (40.00), (N/A)The script checks if the channel is usable by calling
iw phy0 infowhich returns
Wiphy phy0
max # scan SSIDs: 4
max scan IEs length: 2257 bytes
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Device supports AP-side u-APSD.
Device supports T-DLS.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
* CMAC (00-0f-ac:6)
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* WDS
* monitor
* mesh point
* P2P-client
* P2P-GO
Band 1:
Capabilities: 0x11ef
RX LDPC
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 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-15
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] (16.0 dBm)
* 2417 MHz [2] (17.0 dBm)
* 2422 MHz [3] (17.0 dBm)
* 2427 MHz [4] (17.0 dBm)
* 2432 MHz [5] (17.0 dBm)
* 2437 MHz [6] (17.0 dBm)
* 2442 MHz [7] (17.0 dBm)
* 2447 MHz [8] (17.0 dBm)
* 2452 MHz [9] (17.0 dBm)
* 2457 MHz [10] (16.0 dBm)
* 2462 MHz [11] (17.0 dBm)
* 2467 MHz [12] (17.0 dBm) (no IR)
* 2472 MHz [13] (16.0 dBm) (no IR)
* 2484 MHz [14] (disabled)
Band 2:
Capabilities: 0x11ef
RX LDPC
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 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-15
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] (15.0 dBm) (no IR)
* 5200 MHz [40] (15.0 dBm) (no IR)
* 5220 MHz [44] (15.0 dBm) (no IR)
* 5240 MHz [48] (15.0 dBm) (no IR)
* 5260 MHz [52] (17.0 dBm) (no IR, radar detection)
DFS state: usable (for 531 sec)
DFS CAC time: 0 ms
* 5280 MHz [56] (15.0 dBm) (no IR, radar detection)
DFS state: usable (for 531 sec)
DFS CAC time: 0 ms
* 5300 MHz [60] (15.0 dBm) (no IR, radar detection)
DFS state: usable (for 531 sec)
DFS CAC time: 0 ms
* 5320 MHz [64] (15.0 dBm) (no IR, radar detection)
DFS state: usable (for 531 sec)
DFS CAC time: 0 ms
* 5500 MHz [100] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 531 sec)
DFS CAC time: 0 ms
* 5520 MHz [104] (17.0 dBm) (no IR, radar detection)
DFS state: usable (for 531 sec)
DFS CAC time: 0 ms
* 5540 MHz [108] (17.0 dBm) (no IR, radar detection)
DFS state: usable (for 531 sec)
DFS CAC time: 0 ms
* 5560 MHz [112] (17.0 dBm) (no IR, radar detection)
DFS state: usable (for 531 sec)
DFS CAC time: 0 ms
* 5580 MHz [116] (17.0 dBm) (no IR, radar detection)
DFS state: usable (for 531 sec)
DFS CAC time: 0 ms
* 5600 MHz [120] (17.0 dBm) (no IR, radar detection)
DFS state: usable (for 531 sec)
DFS CAC time: 0 ms
* 5620 MHz [124] (17.0 dBm) (no IR, radar detection)
DFS state: usable (for 531 sec)
DFS CAC time: 0 ms
* 5640 MHz [128] (17.0 dBm) (no IR, radar detection)
DFS state: usable (for 531 sec)
DFS CAC time: 0 ms
* 5660 MHz [132] (17.0 dBm) (no IR, radar detection)
DFS state: usable (for 531 sec)
DFS CAC time: 0 ms
* 5680 MHz [136] (17.0 dBm) (no IR, radar detection)
DFS state: usable (for 531 sec)
DFS CAC time: 0 ms
* 5700 MHz [140] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 531 sec)
DFS CAC time: 0 ms
* 5745 MHz [149] (17.0 dBm) (no IR)
* 5765 MHz [153] (17.0 dBm) (no IR)
* 5785 MHz [157] (17.0 dBm) (no IR)
* 5805 MHz [161] (17.0 dBm) (no IR)
* 5825 MHz [165] (17.0 dBm) (no IR)
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
* tdls_mgmt
* tdls_oper
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* channel_switch
* Unknown command (104)
* connect
* disconnect
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):
* AP/VLAN
* monitor
valid interface combinations:
* #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client, P2P-GO } <= 1,
total <= 2048, #channels <= 1, STA/AP BI must match
* #{ WDS } <= 2048,
total <= 2048, #channels <= 1, STA/AP BI must match
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 low priority scan.
Device supports scan flush.
Device supports AP scan.
Device supports per-vif TX power setting
P2P GO supports CT window setting
Driver supports a userspace MPM
Device supports active monitor (which will ACK incoming frames)
Driver/device bandwidth changes during BSS lifetime (AP/GO mode)If the channel has "no IR" or "disabled" listed it quits with an error such as "Your adapter can not transmit to channel 13, frequency band 2.4GHz." This makes it impossible to use 5Ghz channels since they all have "no-IR" and any 2.4Ghz channel above 11.
iwlist shows channel 13 on it's list of channels though.
iwlist wlan0 freq
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 12 : 2.467 GHz
Channel 13 : 2.472 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 132 : 5.66 GHz
Channel 136 : 5.68 GHz
Channel 140 : 5.7 GHz
Channel 149 : 5.745 GHz
Channel 153 : 5.765 GHz
Channel 157 : 5.785 GHzHere is some info about my wireless card:
# lspci -vv | grep "Network" -A10
pcilib: sysfs_read_vpd: read failed: Connection timed out
06:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-size Mini PCIe Card
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 19
Region 0: Memory at f7800000 (64-bit, non-prefetchable) [size=512K]
Expansion ROM at f7880000 [disabled] [size=64K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+Why is iw phy0 info saying channels 12-14 aren't usable when I've enabled them in regulatory.bin? Why does iwlist show 13, but iw phy0 info show it as no IR? Why can't I use any 5Ghz channels at all.
Does anyone know how I can make create_ap broadcast on channel 13 or any 5Ghz channel?
I've been working on this for a while, but can't seem to get it. Any help is appreciated.
Last edited by Twilight_Genesis (2015-02-13 01:26:15)
Offline
It was that the ath9k driver was adhering to what was set in the wireless card's eeprom, so I recompiled my kernel using the 1000-ath-Ignore-regdomain-in-eeprom.patch from this page and was able to use channels 12-14 and 5Ghz channels.
I cannot change the txpower anymore with iwconfig to anything above 20dBm now which sucks, but at least I can use 5Ghz channels.
This is working for me with linux-ck 3.18.7-1
Last edited by Twilight_Genesis (2015-02-13 01:27:28)
Offline
Thanks for this very interesting info.
I am looking to do the same with Intel iwlwifi driver. I can't use OpenWRT resources because AFAICT Intel chips are not found in dedicated APs and thus they don't make patches for them. Do you have any clue where could I start?
Last edited by Lockheed (2015-02-23 16:54:08)
Offline