Differences

This shows you the differences between two versions of the page.

doc:uci:wireless [2014/07/28 20:11]
valentt
doc:uci:wireless [2014/09/13 09:00] (current)
jkdf2 Updated beacon_interval var and removed 11ng and 11na from available options
Line 36: Line 36:
| ''macaddr'' | MAC address | yes/no | //(autodetected)// | Specifies the radio adapter associated to this section, it is //not// used to change the device mac but to identify the underlying interface. | | ''macaddr'' | MAC address | yes/no | //(autodetected)// | Specifies the radio adapter associated to this section, it is //not// used to change the device mac but to identify the underlying interface. |
| ''disabled'' | boolean | no | ''0'' | Disables the radio adapter if set to ''1''. Removing this option or setting it to ''0'' will enable the adapter | | ''disabled'' | boolean | no | ''0'' | Disables the radio adapter if set to ''1''. Removing this option or setting it to ''0'' will enable the adapter |
-| ''channel'' | integer or "auto" | yes | ''auto'' | Specifies the wireless channel to use. | +| ''channel'' | integer or "auto" | yes | ''auto'' | Specifies the wireless channel to use. "auto" defaults to the minimum channel available
-| ''hwmode'' | string | no | //(driver default)// | Selects the wireless protocol to use, possible values are ''11b'', ''11g'', ''11a'', ''11ng'' (11N+11G, 2.4GHz, mac80211 only), ''11na'' (11N+11A, 5GHz, mac80211 only) |+| ''hwmode'' | string | no | //(driver default)// | Selects the wireless protocol to use, possible values are ''11b'', ''11g'', and ''11a'' (note that ''11ng'' and ''11na'' are not available options, see [[https://dev.openwrt.org/ticket/17541|ticket 17541]]) |
| ''htmode'' | string | no | //(driver default)// | Specifies the channel width in 802.11n and 802.11ac mode, possible values are:\\ ''HT20'' (single 20MHz channel),\\ ''HT40-'' (2x 20MHz channels, primary/control channel is upper, secondary channel is below)\\ ''HT40+'' (2x 20MHz channels, primary/control channel is lower, secondary channel is above).\\ ''VHT20'' / ''VHT40'' / ''VHT80'' / ''VHT160'' (channel width in 802.11ac, extra channels are picked according to the specification) \\ Cf. [[doc/faq/faq.wireless#why.can.t.i.use.ht40.with.channel.11]] and [[http://hostap.epitest.fi/cgit/hostap/tree/hostapd/hostapd.conf]] (search for HT40) in the web page. \\ :!: **This option is only used for type ''mac80211''** | | ''htmode'' | string | no | //(driver default)// | Specifies the channel width in 802.11n and 802.11ac mode, possible values are:\\ ''HT20'' (single 20MHz channel),\\ ''HT40-'' (2x 20MHz channels, primary/control channel is upper, secondary channel is below)\\ ''HT40+'' (2x 20MHz channels, primary/control channel is lower, secondary channel is above).\\ ''VHT20'' / ''VHT40'' / ''VHT80'' / ''VHT160'' (channel width in 802.11ac, extra channels are picked according to the specification) \\ Cf. [[doc/faq/faq.wireless#why.can.t.i.use.ht40.with.channel.11]] and [[http://hostap.epitest.fi/cgit/hostap/tree/hostapd/hostapd.conf]] (search for HT40) in the web page. \\ :!: **This option is only used for type ''mac80211''** |
| ''chanbw'' | integer | no | 20 | Specifies a narrow channel width, possible values are: ''5'' (5MHz channel), ''10'' (10MHz channel) or ''20'' (20MHz channel). \\ :!: **Only supported by the ''ath9k''/''ath5k'' driver (since Attitude Adjustment)** | | ''chanbw'' | integer | no | 20 | Specifies a narrow channel width, possible values are: ''5'' (5MHz channel), ''10'' (10MHz channel) or ''20'' (20MHz channel). \\ :!: **Only supported by the ''ath9k''/''ath5k'' driver (since Attitude Adjustment)** |
Line 50: Line 50:
| ''distance'' | integer | no | //(driver default)// | Distance between the ap and the furthest client in meters .\\ :!: **Only supported by ''madwifi'',  and the ''mac80211'' type (in trunk)**| | ''distance'' | integer | no | //(driver default)// | Distance between the ap and the furthest client in meters .\\ :!: **Only supported by ''madwifi'',  and the ''mac80211'' type (in trunk)**|
| ''noscan'' | boolean | no | ''0'' | Do not scan for overlapping BSSs in HT40+/- mode.\\ :!: **Only supported by ''mac80211''** \\ :!: **Turning this on will violate regulatory requirements!** | | ''noscan'' | boolean | no | ''0'' | Do not scan for overlapping BSSs in HT40+/- mode.\\ :!: **Only supported by ''mac80211''** \\ :!: **Turning this on will violate regulatory requirements!** |
-| ''beacon_int'' | integer | no | //100 (hostapd default)// | Set the beacon interval. This is the time interval between beacon frames, measured in units of 1.024 ms. hostapd permits this to be set between 15 and 65535. This option only has an effect on ''ap'' and ''adhoc'' wifi-ifaces. \\ :!: **Only supported by ''mac80211'' (in trunk)** |+| ''beacon_interval'' | integer | no | //100 (hostapd default)// | Set the beacon interval. This is the time interval between beacon frames, measured in units of 1.024 ms. hostapd permits this to be set between 15 and 65535. This option only has an effect on ''ap'' and ''adhoc'' wifi-ifaces. \\ :!: **Only supported by ''mac80211'' (in trunk)** |
| ''basic_rate'' | list | no | //(hostapd/driver default)// | Set the supported basic rates. Each basic_rate is measured in kb/s. This option only has an effect on ''ap'' and ''adhoc'' wifi-ifaces. \\ :!: **Only supported by ''mac80211'' (in trunk)** | | ''basic_rate'' | list | no | //(hostapd/driver default)// | Set the supported basic rates. Each basic_rate is measured in kb/s. This option only has an effect on ''ap'' and ''adhoc'' wifi-ifaces. \\ :!: **Only supported by ''mac80211'' (in trunk)** |
| ''require_mode'' | string | no | //none// | (AP mode) Set the minimum mode that connecting clients need to support to be allowed to connect. Supported values: g = 802.11g, n = 802.11n, ac = 802.11ac | | ''require_mode'' | string | no | //none// | (AP mode) Set the minimum mode that connecting clients need to support to be allowed to connect. Supported values: g = 802.11g, n = 802.11n, ac = 802.11ac |
Line 261: Line 261:
  * opkg install wpad hostapd-utils   * opkg install wpad hostapd-utils
  * reboot   * reboot
 +
 +After rebooting, instead of pushing the WPS button, you can manually initiate the WPS process (which is safer than using the button if it doubles as a reset button, like on the [[toh:tp-link/tl-wr1043nd|TL-WR1043ND v2]] e.g.):
 +
 +<code>hostapd_cli wps_pbc</code>
===== Configuring Encryption ===== ===== Configuring Encryption =====
Line 298: Line 302:
===== DFS / Radar Detection ===== ===== DFS / Radar Detection =====
-In many countries, operating WiFi devices in the 5GHz band requires radar detection and DFS ([[http://wifi-insider.com/wlan/dfs.htm|explanation)]]. More technical details of the Linux implementation can be found at [[http://wireless.kernel.org/en/developers/DFS]]. +In many countries, operating WiFi devices in the 5GHz band requires radar detection and DFS ([[http://wifi-insider.com/wlan/dfs.htm|explanation)]]. More technical details of the Linux implementation can be found [[http://wireless.kernel.org/en/developers/DFS|here]].
DFS works roughly as follows in Linux: The driver (e.g. ath9k) detects radar pulses and reports this to nl80211 where the information is processed. If a series of pulses matches one of the defined radar patterns, this will be reported to user space application (hostapd) which in turn reacts by switching to another channel. DFS works roughly as follows in Linux: The driver (e.g. ath9k) detects radar pulses and reports this to nl80211 where the information is processed. If a series of pulses matches one of the defined radar patterns, this will be reported to user space application (hostapd) which in turn reacts by switching to another channel.
-As of July 2014, DFS and radar detection are supported in OpenWRT trunk (Barrier Braker). Both features are not supported in currect stable release (Attitude Adjustment).+[[https://lists.openwrt.org/pipermail/openwrt-devel/2014-July/026497.html|As of July 2014]], DFS and radar detection are supported from OpenWrt 14.07 (Barrier Breaker) on, 12.09 (Attitude Adjustment) and earlier do not support this. By default, however, OpenWrt uses [[http://wiki.openwrt.org/doc/devel/packages/wpad-mini|wpad-mini]], which **does not support DFS**. To use DFS, rebuild your image (using the [[http://wiki.openwrt.org/doc/howto/obtain.firmware.generate|image generator]] or the [[http://wiki.openwrt.org/about/toolchain|buildroot]]), include both hostapd and wpa_supplicant as static packages, and remove wpad-mini.
Currently, many members of the mac80211 family of WiFi drivers do support radar detection.  DFS is mandatory for most channels in the 5GHz band (exception: indoor-only channels) in many countries.  If you define a channel in your wireless config that requires DFS according to your country regulations, the 5GHz radio device won't start up if you run an OpenWRT version that lacks DFS support or if your system is not configured properly. Currently, many members of the mac80211 family of WiFi drivers do support radar detection.  DFS is mandatory for most channels in the 5GHz band (exception: indoor-only channels) in many countries.  If you define a channel in your wireless config that requires DFS according to your country regulations, the 5GHz radio device won't start up if you run an OpenWRT version that lacks DFS support or if your system is not configured properly.
Line 331: Line 335:
option ssid    OpenWrt option ssid    OpenWrt
option encryption none option encryption none
 +</code>
 +
 +If in doubt, double check your hostapd-phy.conf to make sure it contains the following values, and that your country code is set:
 +<code>
 +country_code=DE
 +ieee80211n=1
 +ieee80211d=1
 +ieee80211h=1
 +hw_mode=a
 +</code>
 +
 +
 +If radar detection is working, DFS channels will show up like this (here for Belgium, //iw phy1 info// output trimmed):
 +<code>
 + Frequencies:
 + * 5220 MHz [44] (17.0 dBm)
 + * 5240 MHz [48] (17.0 dBm)
 + * 5260 MHz [52] (20.0 dBm) (radar detection)
 +   DFS state: usable (for 2155257 sec)
 +   DFS CAC time: 60000 ms
 + * 5280 MHz [56] (20.0 dBm) (radar detection)
 +   DFS state: usable (for 2155257 sec)
 +   DFS CAC time: 60000 ms
</code> </code>
Line 338: Line 365:
Patches for IBSS / Ad-Hoc mode were posted in linux-wireless mailing list: [[http://marc.info/?l=linux-wireless&m=137823021907805&w=2|2013-09-03 [PATCH 0/4] add IBSS-DFS support]]. Patches for IBSS / Ad-Hoc mode were posted in linux-wireless mailing list: [[http://marc.info/?l=linux-wireless&m=137823021907805&w=2|2013-09-03 [PATCH 0/4] add IBSS-DFS support]].
-Output of //iw phy <5ghz> info//+Output of //iw phy <5ghz> info// (trimmed)
<code> <code>
Frequencies: Frequencies:
- * 5180 MHz [36] (15.0 dBm) 
- * 5200 MHz [40] (19.0 dBm) 
* 5220 MHz [44] (15.0 dBm) * 5220 MHz [44] (15.0 dBm)
* 5240 MHz [48] (15.0 dBm) * 5240 MHz [48] (15.0 dBm)
Line 348: Line 373:
  DFS state: usable (for 2731982 sec)   DFS state: usable (for 2731982 sec)
* 5280 MHz [56] (15.0 dBm) (radar detection) * 5280 MHz [56] (15.0 dBm) (radar detection)
-   DFS state: usable (for 2731982 sec) 
- * 5300 MHz [60] (15.0 dBm) (radar detection) 
-   DFS state: usable (for 2731982 sec) 
- * 5320 MHz [64] (15.0 dBm) (radar detection) 
-   DFS state: usable (for 2731982 sec) 
- * 5500 MHz [100] (15.0 dBm) (radar detection) 
-   DFS state: usable (for 2731982 sec) 
- * 5520 MHz [104] (19.0 dBm) (radar detection) 
  DFS state: usable (for 2731982 sec)   DFS state: usable (for 2731982 sec)
</code> </code>

Back to top

doc/uci/wireless.1406571116.txt.bz2 · Last modified: 2014/07/28 20:11 by valentt