* No channels available (no IR) in 5Ghz band for intel 7260-ac
@ 2014-06-23 20:55 Victor
2014-06-24 0:50 ` Luis R. Rodriguez
0 siblings, 1 reply; 5+ messages in thread
From: Victor @ 2014-06-23 20:55 UTC (permalink / raw)
To: linux-wireless
Hello, first of all i'm not sure if this is the proper place to ask
since it seems mostly dev-related, but i have been looking everywhere
trying to find a solution without luck, so i'm not sure if i
encountered some kind of bug.
Context: Setup of wireless AP using an intel 7260-ac on 5Ghz+ band, linux 3.15.1
Problem found: the system shows all channels for Ghz band as (no IR),
so they can't be used
I have tried using "iw reg set" with several country codes, the only
change is which channels are set as "disabled", but on all the other
the (no IR) will remain anyways.
Also on the logs always appears the following: "cfg80211: DFS Master
region: unset"
Examples:
***********************
iw reg set US
iw reg get
country US: DFS-UNSET
(2402 - 2472 @ 40), (N/A, 30)
(5170 - 5250 @ 80), (N/A, 17)
(5250 - 5330 @ 80), (N/A, 23), DFS
(5735 - 5835 @ 80), (N/A, 30)
(57240 - 63720 @ 2160), (N/A, 40)
Frequencies:
* 5180 MHz [36] (16.0 dBm) (no IR)
* 5200 MHz [40] (16.0 dBm) (no IR)
* 5220 MHz [44] (16.0 dBm) (no IR)
* 5240 MHz [48] (16.0 dBm) (no IR)
* 5260 MHz [52] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 1 sec)
* 5280 MHz [56] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 1 sec)
* 5300 MHz [60] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 1 sec)
* 5320 MHz [64] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 1 sec)
* 5500 MHz [100] (disabled)
* 5520 MHz [104] (disabled)
* 5540 MHz [108] (disabled)
* 5560 MHz [112] (disabled)
* 5580 MHz [116] (disabled)
* 5600 MHz [120] (disabled)
* 5620 MHz [124] (disabled)
* 5640 MHz [128] (disabled)
* 5660 MHz [132] (disabled)
* 5680 MHz [136] (disabled)
* 5700 MHz [140] (disabled)
* 5720 MHz [144] (disabled)
* 5745 MHz [149] (16.0 dBm) (no IR)
* 5765 MHz [153] (16.0 dBm) (no IR)
* 5785 MHz [157] (16.0 dBm) (no IR)
* 5805 MHz [161] (16.0 dBm) (no IR)
* 5825 MHz [165] (16.0 dBm) (no IR)
***********************************************
iw reg set FR
iw reg get
country FR: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 80), (N/A, 20)
(5250 - 5330 @ 80), (N/A, 20), DFS
(5490 - 5710 @ 80), (N/A, 27), DFS
(57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR
Frequencies:
* 5180 MHz [36] (16.0 dBm) (no IR)
* 5200 MHz [40] (16.0 dBm) (no IR)
* 5220 MHz [44] (16.0 dBm) (no IR)
* 5240 MHz [48] (16.0 dBm) (no IR)
* 5260 MHz [52] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 27 sec)
* 5280 MHz [56] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 27 sec)
* 5300 MHz [60] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 27 sec)
* 5320 MHz [64] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 27 sec)
* 5500 MHz [100] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 27 sec)
* 5520 MHz [104] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 27 sec)
* 5540 MHz [108] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 27 sec)
* 5560 MHz [112] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 27 sec)
* 5580 MHz [116] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 27 sec)
* 5600 MHz [120] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 27 sec)
* 5620 MHz [124] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 27 sec)
* 5640 MHz [128] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 27 sec)
* 5660 MHz [132] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 27 sec)
* 5680 MHz [136] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 27 sec)
* 5700 MHz [140] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 27 sec)
* 5720 MHz [144] (disabled)
* 5745 MHz [149] (disabled)
* 5765 MHz [153] (disabled)
* 5785 MHz [157] (disabled)
* 5805 MHz [161] (disabled)
* 5825 MHz [165] (disabled)
******************************************
System & device info:
********************
lspci -k
04:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
Subsystem: Intel Corporation Dual Band Wireless-AC 7260
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
************************
dmesg | grep 7260
[ 1.473288] iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band
Wireless AC 7260, REV=0x144
***********************
dmesg | grep firmware
[ 1.430175] iwlwifi 0000:04:00.0: loaded firmware version
23.214.9.0 op_mode iwlmvm
***************************
uname -a
Linux 3.15.1 #1 SMP PREEMPT Mon Jun 23 12:48:38 CEST 2014 x86_64
******************
iw phy (previously used ES reg code)
Wiphy phy0
max # scan SSIDs: 20
max scan IEs length: 393 bytes
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Device supports AP-side u-APSD.
Supported Ciphers:
* CCMP (00-0f-ac:4)
* TKIP (00-0f-ac:2)
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* CMAC (00-0f-ac:6)
* WPI-SMS4 (00-14-72:1)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* P2P-client
* P2P-GO
* P2P-device
Band 1:
Capabilities: 0x11e2
HT20/HT40
Static SM Power Save
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: 4 usec (0x05)
HT TX/RX MCS rate indexes supported: 0-15, 32
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] (16.0 dBm)
* 2422 MHz [3] (16.0 dBm)
* 2427 MHz [4] (16.0 dBm)
* 2432 MHz [5] (16.0 dBm)
* 2437 MHz [6] (16.0 dBm)
* 2442 MHz [7] (16.0 dBm)
* 2447 MHz [8] (16.0 dBm)
* 2452 MHz [9] (16.0 dBm)
* 2457 MHz [10] (16.0 dBm)
* 2462 MHz [11] (16.0 dBm)
* 2467 MHz [12] (16.0 dBm) (no IR)
* 2472 MHz [13] (16.0 dBm) (no IR)
Band 2:
Capabilities: 0x11e2
HT20/HT40
Static SM Power Save
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: 4 usec (0x05)
HT TX/RX MCS rate indexes supported: 0-15, 32
VHT Capabilities (0x038071a0):
Max MPDU length: 3895
Supported Channel Width: neither 160 nor 80+80
short GI (80 MHz)
TX STBC
SU Beamformee
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
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: not supported
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] (16.0 dBm) (no IR)
* 5200 MHz [40] (16.0 dBm) (no IR)
* 5220 MHz [44] (16.0 dBm) (no IR)
* 5240 MHz [48] (16.0 dBm) (no IR)
* 5260 MHz [52] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 2 sec)
* 5280 MHz [56] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 2 sec)
* 5300 MHz [60] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 2 sec)
* 5320 MHz [64] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 2 sec)
* 5500 MHz [100] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 2 sec)
* 5520 MHz [104] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 2 sec)
* 5540 MHz [108] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 2 sec)
* 5560 MHz [112] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 2 sec)
* 5580 MHz [116] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 2 sec)
* 5600 MHz [120] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 2 sec)
* 5620 MHz [124] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 2 sec)
* 5640 MHz [128] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 2 sec)
* 5660 MHz [132] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 2 sec)
* 5680 MHz [136] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 2 sec)
* 5700 MHz [140] (16.0 dBm) (no IR, radar detection)
DFS state: usable (for 2 sec)
* 5720 MHz [144] (disabled)
* 5745 MHz [149] (disabled)
* 5765 MHz [153] (disabled)
* 5785 MHz [157] (disabled)
* 5805 MHz [161] (disabled)
* 5825 MHz [165] (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
* start_sched_scan
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* 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
WoWLAN support:
* wake up on disconnect
* wake up on magic packet
* wake up on pattern match, up to 20 patterns of 16-128 bytes,
maximum packet offset 0 bytes
* can do GTK rekeying
* wake up on GTK rekey failure
* wake up on EAP identity request
* wake up on 4-way handshake
* wake up on rfkill release
* wake up on TCP connection
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <=
1, #{ P2P-device } <= 1,
total <= 3, #channels <= 1
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 scan flush.
****************************
There isn't any error in dmesg or logs.
What can i do? If a try to create an AP with, for example, hostapd, on
802.11ac mode, it won't work at all saying "Configured channel (36)
not found from the channel list of current mode (2) IEEE 802.11a" etc,
the device works fine on 2.4Ghz band.
Thanks!
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: No channels available (no IR) in 5Ghz band for intel 7260-ac
2014-06-23 20:55 No channels available (no IR) in 5Ghz band for intel 7260-ac Victor
@ 2014-06-24 0:50 ` Luis R. Rodriguez
2014-06-24 7:37 ` Emmanuel Grumbach
2014-06-24 8:41 ` Setup of wireless AP using an intel 7260-ac on 5Ghz+ band, linux 3.15.1 (was: No channels available (no IR) in 5Ghz band for intel 7260-ac) Arend van Spriel
0 siblings, 2 replies; 5+ messages in thread
From: Luis R. Rodriguez @ 2014-06-24 0:50 UTC (permalink / raw)
To: Victor; +Cc: linux-wireless
On Mon, Jun 23, 2014 at 10:55:48PM +0200, Victor wrote:
> Hello, first of all i'm not sure if this is the proper place to ask
> since it seems mostly dev-related, but i have been looking everywhere
> trying to find a solution without luck, so i'm not sure if i
> encountered some kind of bug.
>
> Context: Setup of wireless AP using an intel 7260-ac on 5Ghz+ band, linux 3.15.1
>
> Problem found: the system shows all channels for Ghz band as (no IR),
> so they can't be used
NO-IR means you can't initiate radiation, it doesn't mean they are
disabled. The NO-IR flag then means you cannot use modes of operation
that require you to initiate radiation first, there are two ways that
can happen:
* beconing -- AP, IBSS, Mesh, P2P master mode
* active scanning
You are still able to do passive scanning. The NO-IR flag can be
lifted from channels if the driver does like the idea of trusting
beacon hints:
http://wireless.kernel.org/en/developers/Regulatory/processing_rules#Beacon_hints
If the driver does not like those then you won't get the NO-IR flag
lifted when a beacon is found. There device follows the desire by
the silicon manufacturer and whoever deploys the device and integrates
it into your system so anything beyond this should be checked with
Intel folks.
Luis
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: No channels available (no IR) in 5Ghz band for intel 7260-ac
2014-06-24 0:50 ` Luis R. Rodriguez
@ 2014-06-24 7:37 ` Emmanuel Grumbach
2014-06-24 8:07 ` Victor
2014-06-24 8:41 ` Setup of wireless AP using an intel 7260-ac on 5Ghz+ band, linux 3.15.1 (was: No channels available (no IR) in 5Ghz band for intel 7260-ac) Arend van Spriel
1 sibling, 1 reply; 5+ messages in thread
From: Emmanuel Grumbach @ 2014-06-24 7:37 UTC (permalink / raw)
To: Luis R. Rodriguez, Victor; +Cc: linux-wireless
On 06/24/2014 03:50 AM, Luis R. Rodriguez wrote:
> On Mon, Jun 23, 2014 at 10:55:48PM +0200, Victor wrote:
>> Hello, first of all i'm not sure if this is the proper place to ask
>> since it seems mostly dev-related, but i have been looking everywhere
>> trying to find a solution without luck, so i'm not sure if i
>> encountered some kind of bug.
>>
>> Context: Setup of wireless AP using an intel 7260-ac on 5Ghz+ band, linux 3.15.1
This configuration is not supported.
>>
>> Problem found: the system shows all channels for Ghz band as (no IR),
>> so they can't be used
>
> NO-IR means you can't initiate radiation, it doesn't mean they are
> disabled. The NO-IR flag then means you cannot use modes of operation
> that require you to initiate radiation first, there are two ways that
> can happen:
>
> * beconing -- AP, IBSS, Mesh, P2P master mode
> * active scanning
>
> You are still able to do passive scanning. The NO-IR flag can be
> lifted from channels if the driver does like the idea of trusting
> beacon hints:
>
> http://wireless.kernel.org/en/developers/Regulatory/processing_rules#Beacon_hints
>
> If the driver does not like those then you won't get the NO-IR flag
> lifted when a beacon is found. There device follows the desire by
> the silicon manufacturer and whoever deploys the device and integrates
> it into your system so anything beyond this should be checked with
> Intel folks.
>
> Luis
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: No channels available (no IR) in 5Ghz band for intel 7260-ac
2014-06-24 7:37 ` Emmanuel Grumbach
@ 2014-06-24 8:07 ` Victor
0 siblings, 0 replies; 5+ messages in thread
From: Victor @ 2014-06-24 8:07 UTC (permalink / raw)
To: Emmanuel Grumbach; +Cc: Luis R. Rodriguez, linux-wireless
2014-06-24 9:37 GMT+02:00 Emmanuel Grumbach <egrumbach@gmail.com>:
>
>
> On 06/24/2014 03:50 AM, Luis R. Rodriguez wrote:
>> On Mon, Jun 23, 2014 at 10:55:48PM +0200, Victor wrote:
>>> Hello, first of all i'm not sure if this is the proper place to ask
>>> since it seems mostly dev-related, but i have been looking everywhere
>>> trying to find a solution without luck, so i'm not sure if i
>>> encountered some kind of bug.
>>>
>>> Context: Setup of wireless AP using an intel 7260-ac on 5Ghz+ band, linux 3.15.1
>
> This configuration is not supported.
Do you know why? it is supported in other kernel version?, i got the
device mainly for to be used as 802.11ac AP :/, on the product brief
they state it is designed for AP mode
http://www.intel.es/content/dam/www/public/us/en/documents/product-briefs/dual-band-wireless-ac-7260-bluetooth-brief.pdf,
and in iw it appears as supported too
Thanks.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Setup of wireless AP using an intel 7260-ac on 5Ghz+ band, linux 3.15.1 (was: No channels available (no IR) in 5Ghz band for intel 7260-ac)
2014-06-24 0:50 ` Luis R. Rodriguez
2014-06-24 7:37 ` Emmanuel Grumbach
@ 2014-06-24 8:41 ` Arend van Spriel
1 sibling, 0 replies; 5+ messages in thread
From: Arend van Spriel @ 2014-06-24 8:41 UTC (permalink / raw)
To: Luis R. Rodriguez, Victor; +Cc: linux-wireless
updated subject
On 24-06-14 02:50, Luis R. Rodriguez wrote:
> On Mon, Jun 23, 2014 at 10:55:48PM +0200, Victor wrote:
>> Hello, first of all i'm not sure if this is the proper place to ask
>> since it seems mostly dev-related, but i have been looking everywhere
>> trying to find a solution without luck, so i'm not sure if i
>> encountered some kind of bug.
>>
>> Context: Setup of wireless AP using an intel 7260-ac on 5Ghz+ band, linux 3.15.1
>>
>> Problem found: the system shows all channels for Ghz band as (no IR),
>> so they can't be used
>
> NO-IR means you can't initiate radiation, it doesn't mean they are
> disabled. The NO-IR flag then means you cannot use modes of operation
> that require you to initiate radiation first, there are two ways that
> can happen:
>
> * beconing -- AP, IBSS, Mesh, P2P master mode
That is just the point, right? The context is "Setup of wireless AP".
Regards,
Arend
> * active scanning
>
> You are still able to do passive scanning. The NO-IR flag can be
> lifted from channels if the driver does like the idea of trusting
> beacon hints:
>
> http://wireless.kernel.org/en/developers/Regulatory/processing_rules#Beacon_hints
>
> If the driver does not like those then you won't get the NO-IR flag
> lifted when a beacon is found. There device follows the desire by
> the silicon manufacturer and whoever deploys the device and integrates
> it into your system so anything beyond this should be checked with
> Intel folks.
>
> Luis
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-06-24 8:41 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-06-23 20:55 No channels available (no IR) in 5Ghz band for intel 7260-ac Victor
2014-06-24 0:50 ` Luis R. Rodriguez
2014-06-24 7:37 ` Emmanuel Grumbach
2014-06-24 8:07 ` Victor
2014-06-24 8:41 ` Setup of wireless AP using an intel 7260-ac on 5Ghz+ band, linux 3.15.1 (was: No channels available (no IR) in 5Ghz band for intel 7260-ac) Arend van Spriel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).