X-Git-Url: https://git.rohieb.name/openwrt.git/blobdiff_plain/8aab380dded91464d39d1ad1221b75d8a50ed539..d8c14cad1031af274a143787b0dafc3f9e7befbc:/docs/wireless.tex?ds=inline diff --git a/docs/wireless.tex b/docs/wireless.tex index 861e04dc4..d92fa76cd 100644 --- a/docs/wireless.tex +++ b/docs/wireless.tex @@ -1,13 +1,13 @@ The WiFi settings are configured in the file \texttt{/etc/config/wireless} -(currently supported on Broadcom and Atheros). When booting the router for the first time +(currently supported on Broadcom, Atheros and mac80211). When booting the router for the first time it should detect your card and create a sample configuration file. By default '\texttt{option network lan}' is commented. This prevents unsecured sharing of the network over the wireless interface. Each wireless driver has its own configuration script in \texttt{/lib/wifi/driver\_name.sh} which handles driver specific options and configurations. This script is also calling driver specific binaries like wlc for -Broadcom, or hostapd and wpa\_supplicant for atheros. +Broadcom, or hostapd and wpa\_supplicant for atheros and mac80211. -The reason for using such architecture, is that it abstracts the driver configuration +The reason for using such architecture, is that it abstracts the driver configuration. \paragraph{Generic Broadcom wireless config:} @@ -31,7 +31,7 @@ config wifi-iface config wifi-device "wifi0" option type "atheros" option channel "5" - option agmode "11g" + option hwmode "11g" config wifi-iface option device "wifi0" @@ -42,6 +42,22 @@ config wifi-iface option encryption "none" \end{Verbatim} +\paragraph{Generic mac80211 wireless config:} + +\begin{Verbatim} +config wifi-device "wifi0" + option type "mac80211" + option channel "5" + +config wifi-iface + option device "wlan0" +# option network lan + option mode "ap" + option ssid "OpenWrt" + option hidden "0" + option encryption "none" +\end{Verbatim} + \paragraph{Generic multi-radio Atheros wireless config:} \begin{Verbatim} @@ -77,21 +93,25 @@ of that (if supported by the driver). A full outline of the wireless configuration file with description of each field: \begin{Verbatim} -config wifi-device wifi device name - option type broadcom, atheros - option country us, uk, fr, de, etc. - option channel 1-14 - option maxassoc 1-128 (broadcom only) - option distance 1-n - option agmode 11b, 11g, 11a, 11bg (atheros only) +config wifi-device wifi device name + option type broadcom, atheros, mac80211 + option country us, uk, fr, de, etc. + option channel 1-14 + option maxassoc 1-128 (broadcom only) + option distance 1-n (meters) + option hwmode 11b, 11g, 11a, 11bg (atheros, mac80211) + option rxantenna 0,1,2 (atheros, broadcom) + option txantenna 0,1,2 (atheros, broadcom) + option txpower transmission power in dBm config wifi-iface - option network the interface you want wifi to bridge with + option network the interface you want wifi to bridge with option device wifi0, wifi1, wifi2, wifiN - option mode ap, sta, adhoc, or wds + option mode ap, sta, adhoc, monitor, mesh, or wds + option txpower (deprecated) transmission power in dBm option ssid ssid name option bssid bssid address - option encryption none, wep, psk, psk2, wpa, wpa2 + option encryption none, wep, psk, psk2, wpa, wpa2 option key encryption key option key1 key 1 option key2 key 2 @@ -100,7 +120,7 @@ config wifi-iface option server ip address option port port option hidden 0,1 - option isolate 0,1 + option isolate 0,1 (broadcom) \end{Verbatim} \paragraph{Options for the \texttt{wifi-device}:} @@ -116,14 +136,25 @@ config wifi-iface The wifi channel (e.g. 1-14, depending on your country setting). \item \texttt{maxassoc} \\ - Optional: Maximum number of associated clients. This feature is supported only on the broadcom chipset. + Optional: Maximum number of associated clients. This feature is supported only on the Broadcom chipsets. \item \texttt{distance} \\ - Optional: Distance between the ap and the furthest client in meters. This feature is supported only on the atheros chipset. + Optional: Distance between the ap and the furthest client in meters. This feature is supported only on the Atheros chipsets. \item \texttt{mode} \\ - The frequency band (\texttt{b}, \texttt{g}, \texttt{bg}, \texttt{a}). This feature is only supported on the atheros chipset. + The frequency band (\texttt{b}, \texttt{g}, \texttt{bg}, \texttt{a}). This feature is only supported on the Atheros chipsets. + + \item \texttt{diversity} \\ + Optional: Enable diversity for the Wi-Fi device. This feature is supported only on the Atheros chipsets. + + \item \texttt{rxantenna} \\ + Optional: Antenna identifier (0, 1 or 2) for reception. This feature is supported by Atheros and some Broadcom chipsets. + + \item \texttt{txantenna} \\ + Optional: Antenna identifier (0, 1 or 2) for emission. This feature is supported by Atheros and some Broadcom chipsets. + \item \texttt{txpower} + Set the transmission power to be used. The amount is specified in dBm. \end{itemize} @@ -150,6 +181,12 @@ config wifi-iface \item \texttt{adhoc} \\ Ad-Hoc mode + \item \texttt{monitor} \\ + Monitor mode + + \item \texttt{mesh} \\ + Mesh Point mode (802.11s) + \item \texttt{wds} \\ WDS point-to-point link @@ -161,6 +198,9 @@ config wifi-iface \item \texttt{bssid} Set the BSSID address to be used for wds to set the mac address of the other wds unit. + \item \texttt{txpower} + (Deprecated, set in wifi-device) Set the transmission power to be used. The amount is specified in dBm. + \item \texttt{encryption} \\ Encryption setting. Accepts the following values: @@ -181,7 +221,7 @@ config wifi-iface The RADIUS server ip address \item \texttt{port} (wpa) \\ - The RADIUS server port + The RADIUS server port (defaults to 1812) \item \texttt{hidden} \\ 0 broadcasts the ssid; 1 disables broadcasting of the ssid @@ -192,6 +232,118 @@ config wifi-iface \end{itemize} +\paragraph{Mesh Point} + +Mesh Point (802.11s) is only supported by some mac80211 drivers. It requires the iw package +to be installed to setup mesh links. OpenWrt creates mshN mesh point interfaces. A sample +configuration looks like this: + +\begin{Verbatim} +config wifi-device "wlan0" + option type "mac80211" + option channel "5" + +config wifi-iface + option device "wlan0" + option network lan + option mode "mesh" + option mesh_id "OpenWrt" +\end{Verbatim} + +\paragraph{Wireless Distribution System} + +WDS is a non-standard mode which will be working between two Broadcom devices for instance +but not between a Broadcom and Atheros device. + +\subparagraph{Unencrypted WDS connections} + +This configuration example shows you how to setup unencrypted WDS connections. +We assume that the peer configured as below as the BSSID ca:fe:ba:be:00:01 +and the remote WDS endpoint ca:fe:ba:be:00:02 (option bssid field). + +\begin{Verbatim} +config wifi-device "wl0" + option type "broadcom" + option channel "5" + +config wifi-iface + option device "wl0" + option network lan + option mode "ap" + option ssid "OpenWrt" + option hidden "0" + option encryption "none" + +config wifi-iface + option device "wl0" + option network lan + option mode wds + option ssid "OpenWrt WDS" + option bssid "ca:fe:ba:be:00:02" +\end{Verbatim} + +\subparagraph{Encrypted WDS connections} + +It is also possible to encrypt WDS connections. \texttt{psk}, \texttt{psk2} and +\texttt{psk+psk2} modes are supported. Configuration below is an example +configuration using Pre-Shared-Keys with AES algorithm. + +\begin{Verbatim} +config wifi-device wl0 + option type broadcom + option channel 5 + +config wifi-iface + option device "wl0" + option network lan + option mode ap + option ssid "OpenWrt" + option encryption psk2 + option key "" + +config wifi-iface + option device "wl0" + option network lan + option mode wds + option bssid ca:fe:ba:be:00:02 + option ssid "OpenWrt WDS" + option encryption psk2 + option key "" +\end{Verbatim} + +\paragraph{802.1x configurations} + +OpenWrt supports both 802.1x client and Access Point +configurations. 802.1x client is only working with +drivers supported by wpa-supplicant. Configuration +only supports EAP types TLS, TTLS or PEAP. + +\subparagraph{EAP-TLS} + +\begin{Verbatim} +config wifi-iface + option device "ath0" + option network lan + option ssid OpenWrt + option eap_type tls + option ca_cert "/etc/config/certs/ca.crt" + option priv_key "/etc/config/certs/priv.crt" + option priv_key_pwd "PKCS#12 passphrase" +\end{Verbatim} + +\subparagraph{EAP-PEAP} + +\begin{Verbatim} +config wifi-iface + option device "ath0" + option network lan + option ssid OpenWrt + option eap_type peap + option ca_cert "/etc/config/certs/ca.crt" + option auth MSCHAPV2 + option identity username + option password password +\end{Verbatim} \paragraph{Limitations:} @@ -204,6 +356,7 @@ Only the following mode combinations are supported: \item 1x \texttt{sta}, 0-3x \texttt{ap} \item 1-4x \texttt{ap} \item 1x \texttt{adhoc} + \item 1x \texttt{monitor} \end{itemize} WDS links can only be used in pure AP mode and cannot use WEP (except when sharing the @@ -211,15 +364,18 @@ Only the following mode combinations are supported: \item \textbf{Atheros}: \\ \begin{itemize} - \item 1x \texttt{sta}, 0-4x \texttt{ap} - \item 1-4x \texttt{ap} + \item 1x \texttt{sta}, 0-Nx \texttt{ap} + \item 1-Nx \texttt{ap} \item 1x \texttt{adhoc} \end{itemize} + + N is the maximum number of VAPs that the module allows, it defaults to 4, but can be + changed by loading the module with the maxvaps=N parameter. \end{itemize} \paragraph{Adding a new driver configuration} -Since we currently only support two different wireless drivers : Broadcom and Atheros, +Since we currently only support thread different wireless drivers : Broadcom, Atheros and mac80211, you might be interested in adding support for another driver like Ralink RT2x00, Texas Instruments ACX100/111. @@ -235,30 +391,84 @@ include several functions providing : Each driver script should append the driver to a global DRIVERS variable : -\begin{verbatim} +\begin{Verbatim} append DRIVERS "driver name" -\end{verbatim} +\end{Verbatim} -\subparagraph{scan\_driver} +\subparagraph{\texttt{scan\_}} This function will parse the \texttt{/etc/config/wireless} and make sure there are no configuration incompatibilities, like enabling hidden SSIDS with ad-hoc mode for instance. This can be more complex if your driver supports a lof of configuration -options. It does not enable your wireless driver to work. +options. It does not change the state of the interface. -\subparagraph{enable\_driver} +Example: +\begin{Verbatim} +scan_dummy() { + local device="$1" + + config_get vifs "$device" vifs + for vif in $vifs; do + # check config consistency for wifi-iface sections + done + # check mode combination +} +\end{Verbatim} -This function will enable the driver and read the configuration file to create application -specific configuration files for the NAS or supplicant program. It will not check the -configuration consistency. +\subparagraph{\texttt{enable\_}} -\subparagraph{disable\_driver} +This function will bring up the wifi device and optionally create application specific +configuration files, e.g. for the WPA authenticator or supplicant. -This function should properly shutdown the wireless interfaces and kill associated programs -running on top of it. +Example: +\begin{Verbatim} +enable_dummy() { + local device="$1" + + config_get vifs "$device" vifs + for vif in $vifs; do + # bring up virtual interface belonging to + # the wifi-device "$device" + done +} +\end{Verbatim} + +\subparagraph{\texttt{disable\_}} + +This function will bring down the wifi device and all its virtual interfaces (if supported). + +Example: +\begin{Verbatim} +disable_dummy() { + local device="$1" + + # bring down virtual interfaces belonging to + # "$device" regardless of whether they are + # configured or not. Don't rely on the vifs + # variable at this point +} +\end{Verbatim} + +\subparagraph{\texttt{detect\_}} -\subparagraph{detec\_driver} +This function looks for interfaces that are usable with the driver. Template config sections +for new devices should be written to stdout. Must check for already existing config sections +belonging to the interfaces before creating new templates. -This function should reliably report the existence of the driver and of one or more of its -wireless interfaces. A basic configuration file has to be generated in the meantime. +Example: +\begin{Verbatim} +detect_dummy() { + [ wifi-device = "$(config_get dummydev type)" ] && return 0 + cat <