Differences

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

doc:howto:clientmode [2012/11/29 16:36]
uvray313
doc:howto:clientmode [2014/05/08 05:52] (current)
natehardison Typo fix
Line 1: Line 1:
====== Client Mode Wireless ====== ====== Client Mode Wireless ======
-This article outlines several methods of connecting devices wirelessly using //Client// or //Station// mode.+This article outlines several methods of connecting devices wirelessly using [[Client Mode|Client]] or [[Station Mode|Station]] mode.
There are a variety of different possibilities: There are a variety of different possibilities:
Line 8: Line 8:
  * Create a point-to-point link,   * Create a point-to-point link,
  * Reverse the roles of access point and client to accomodate driver limitations.   * Reverse the roles of access point and client to accomodate driver limitations.
-  * Allow shutting down a single device without effecting the rest of the network.+  * Allow shutting down a single device without affecting the rest of the network.
-OpenWrt supports various client modes, including //[[wp>Wireless_distribution_system|WDS (Wireless Distribution System)]]//, //routed client mode// or //bridged client mode// (only on //brcm-2.4//).+OpenWrt supports various client modes, including bridging using //[[wp>Wireless_distribution_system|WDS (Wireless Distribution System)]]//, //routed client mode// or a //bridged client mode// implemented only on (old) //brcm-2.4// hardware).
===== WDS - Wireless Distribution System ===== ===== WDS - Wireless Distribution System =====
-WDS mode is a non-standard extension to the wireless [[wp>802.11]] standard using a //4-address-format// to allow transparent ethernet bridging on the station and to implement seamingless //hand-over// for wireless clients roaming between different access points.+WDS mode is a non-standard extension to the wireless [[wp>802.11]] standard using a //4-address-format// to allow transparent ethernet bridging on the station and to implement seamless //hand-over// for wireless clients roaming between different access points.
Due to its non-standard nature, WDS is often implemented differently in wireless drivers and vendor firmwares making them incompatible with each other. In order to use WDS, one should use the same hardware and software on all deployed wireless devices to maintain compatibility. Due to its non-standard nature, WDS is often implemented differently in wireless drivers and vendor firmwares making them incompatible with each other. In order to use WDS, one should use the same hardware and software on all deployed wireless devices to maintain compatibility.
Line 21: Line 21:
  * [[wp>Broadcom]] WDS - available on Broadcom wireless chipsets using the proprietary //wl.o// driver   * [[wp>Broadcom]] WDS - available on Broadcom wireless chipsets using the proprietary //wl.o// driver
-  * AP-to-Sta WDS - available for both //[[http://madwifi-project.org/|Madwifi]]// and //[[http://wireless.kernel.org/en/developers/Documentation/mac80211|mac80211]]// supported wireless devices+  * AP-to-Sta WDS - available for both //[[http://madwifi-project.org/|Madwifi]]// and //[[http://wireless.kernel.org/en/developers/Documentation/mac80211|mac80211]]// supported wireless devices (such as Atheros wireless chipsets)
The biggest advantage of WDS is the [[wp>OSI_layer_2|Layer 2]] transparency enabling [[wp>Bridging_(networking)|bridging]] and [[wp>Broadcasting_(networking)|broadcasting]] across wireless connections - all connected network devices form one common [[wp>Broadcast_domain|broadcast domain]]. The biggest advantage of WDS is the [[wp>OSI_layer_2|Layer 2]] transparency enabling [[wp>Bridging_(networking)|bridging]] and [[wp>Broadcasting_(networking)|broadcasting]] across wireless connections - all connected network devices form one common [[wp>Broadcast_domain|broadcast domain]].
Line 32: Line 32:
==== AP-to-Sta WDS (Madwifi, mac80211) === ==== AP-to-Sta WDS (Madwifi, mac80211) ===
-[[doc:recipes:atheroswds|WDS (atheros)]]+The setup of Madwifi or mac80211 WDS is explained in the recipe article [[doc:recipes:atheroswds|WDS (atheros)]].
 +This option is the preferred approach for wireless chipsets that support the Linux mac80211 wireless drivers (e.g. Atheros wireless chipsets). If the file /etc/config/wireless looks like the following, then mac80211 drivers are in use.
 +
 +<code>
 +config wifi-device 'radio0'
 +        option type 'mac80211'
 +        ...
 +</code>
===== Routed Client Mode ===== ===== Routed Client Mode =====
Line 117: Line 124:
==== Why it works on brcm-2.4 ==== ==== Why it works on brcm-2.4 ====
-The propretary //wl.o// Broadcom wireless driver implements an ARP-NAT (Layer 2 address translation) mechanism called //WET mode//.+The proprietary //wl.o// Broadcom wireless driver implements an ARP-NAT (Layer 2 address translation) mechanism called //WET mode//.
ARP-NAT is comparable to //Masquerading// used on Layer 3 to connect multiple hosts using only one globally routed public IP address. ARP-NAT is comparable to //Masquerading// used on Layer 3 to connect multiple hosts using only one globally routed public IP address.
Line 157: Line 164:
 +===== Client Mode with WPA2 Enterprise PEAP-GTC Authentication =====
 +  -Make sure you have the full wpa_supplicant package that support EAP/PEAP authentication.
 +  -Use UCI or modify the /etc/config/wireless file to set the following options
 +        option network 'wwan'
 +        option device 'radio0'
 +        #set device and network as necessary
 +        option mode 'sta'
 +        option ssid 'CHANGE_THIS_TO_YOUR_SSID'
 +        option encryption 'wpa2+ccmp'
 +        option eap_type 'peap'
 +        option auth 'gtc'
 +        option identity 'CHANGE_THIS_TO_YOUR_ID'
 +  -Enter //uci commit wireless// on the command line
 +  -Enter //wifi// on the command line
 +When the wireless configuration is committed and wifi is commanded, a wpa_supplicant-wlan0.conf (may be something besides wlan0 if you are using a different interface) file is created in the /var/run (same as /tmp/run) directory containing the necessary variables. This looks like the following
 +  ctrl_interface=/var/run/wpa_supplicant-wlan0
 + 
 +  network={
 +        scan_ssid=1
 +        ssid="YOUR_SSID_HERE"
 +        key_mgmt=WPA-EAP
 +        proto=WPA2
 +        eap=PEAP
 +        phase2="auth=gtc"
 +        identity="YOUR_ID_HERE"
 +        password=""  <----delete this line and save the file
 +  }
- +There is a bug that prevents PEAP-GTC from working. Because no password was specified in the wireless configuration file, uci translated this to password="" in the wpa_supplicant conf file, when the time comes to enter your OTP (one time pin) you will not get the prompt because wpa_supplicant accepts "" as a valid null password. 
 + -edit the wpa_supplicant-wlan0.conf file by removing the //password=""// line. 
 +  -from the command line enter //wpa_cli -p /var/run/wpa_supplicant-wlan0// (change wlan0 to your interface as necessary) 
 +This will bring up the wpa command line interface. This is necessary because the command line interface receives the OTP query from the wpa_supplicant. 
 +  -First, reload the modified wpa supplicant configuration file by type //reconfigure// in the wpa_cli interactive prompt. 
 +  -Then, type //reassociate// 
 +  -After a few seconds you should receive a prompt to enter your one time pin. 
 +  -If you have more than one interface on which the wpa supplicant is running determine the //id// of the desired interface by typing //status// at the wpa_cli prompt. If you have only one interface it has id=0 
 +  -At the wpa_cli prompt type //otp 0 your_password_here// 
 +  -If you are lucky and have been a good boy (or girl) you will receive a message saying that you have been authenticated and the interface is connected. 
 +  -You may now quit wpa_cli 
 +  -Continue with whatever else you were up to.

Back to top

doc/howto/clientmode.1354203415.txt.bz2 · Last modified: 2012/11/29 16:36 by uvray313