/[gentoo]/xml/htdocs/doc/en/handbook/hb-net-wireless.xml
Gentoo

Diff of /xml/htdocs/doc/en/handbook/hb-net-wireless.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.8 Revision 1.9
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> 2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3 3
4<!-- The content of this document is licensed under the CC-BY-SA license --> 4<!-- The content of this document is licensed under the CC-BY-SA license -->
5<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 5<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml,v 1.8 2005/12/23 21:28:18 neysx Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml,v 1.9 2006/01/09 14:57:04 jkt Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>1.3</version> 11<version>1.4</version>
12<date>2005-12-22</date> 12<date>2005-12-22</date>
13 13
14<section> 14<section>
15<title>Introduction</title> 15<title>Introduction</title>
16<body> 16<body>
20<c>wpa_supplicant</c>. The important thing to remember is that you configure for 20<c>wpa_supplicant</c>. The important thing to remember is that you configure for
21wireless networks on a global basis and not an interface basis. 21wireless networks on a global basis and not an interface basis.
22</p> 22</p>
23 23
24<p> 24<p>
25<c>wpa_suppliant</c> is the best choice, but it does not support all drivers. 25<c>wpa_supplicant</c> is the best choice, but it does not support all drivers.
26For a list of supported drivers, <uri 26For a list of supported drivers, <uri
27link="http://hostap.epitest.fi/wpa_supplicant">read the wpa_supplicant 27link="http://hostap.epitest.fi/wpa_supplicant">read the wpa_supplicant
28site</uri>. Also, <c>wpa_supplicant</c> can currently only connect to SSID's 28site</uri>. Also, <c>wpa_supplicant</c> can currently only connect to SSID's
29that you have configured for. 29that you have configured for.
30</p> 30</p>
33<c>wireless-tools</c> supports nearly all cards and drivers, but it cannot 33<c>wireless-tools</c> supports nearly all cards and drivers, but it cannot
34connect to WPA only Access Points. 34connect to WPA only Access Points.
35</p> 35</p>
36 36
37<warn> 37<warn>
38The <c>linux-wlan-ng</c> driver is not supported by <c>baselayout</c> at this 38The <c>linux-wlan-ng</c> driver is not supported by baselayout at this
39time. This is because <c>linux-wlan-ng</c> have their own setup and 39time. This is because <c>linux-wlan-ng</c> have their own setup and
40configuration which is completely different to everyone else's. The 40configuration which is completely different to everyone else's. The
41<c>linux-wlan-ng</c> devs are rumoured to be changing their setup over to 41<c>linux-wlan-ng</c> devs are rumoured to be changing their setup over to
42<c>wireless-tools</c> - when this happens you may use <c>linux-wlan-ng</c> 42<c>wireless-tools</c> - when this happens you may use <c>linux-wlan-ng</c>
43with <c>baselayout</c>. 43with baselayout.
44</warn> 44</warn>
45 45
46</body> 46</body>
47</section> 47</section>
48<section> 48<section>
80</pre> 80</pre>
81 81
82<note> 82<note>
83If you're using the host-ap driver you will need to put the card in <e>Managed 83If you're using the host-ap driver you will need to put the card in <e>Managed
84mode</e> before it can be used with <c>wpa_supplicant</c> correctly. You can use 84mode</e> before it can be used with <c>wpa_supplicant</c> correctly. You can use
85<e>iwconfig_eth0="mode managed"</e> to achieve this in 85<c>iwconfig_eth0="mode managed"</c> to achieve this in
86<path>/etc/conf.d/net</path>. 86<path>/etc/conf.d/net</path>.
87</note> 87</note>
88 88
89<p> 89<p>
90That was simple wasn't it? However, we still have to configure 90That was simple wasn't it? However, we still have to configure
203</pre> 203</pre>
204 204
205<note> 205<note>
206Although you can store your wireless settings in 206Although you can store your wireless settings in
207<path>/etc/conf.d/wireless</path> this guide recommends you store them in 207<path>/etc/conf.d/wireless</path> this guide recommends you store them in
208<path>/etc/conf.d/net</path> 208<path>/etc/conf.d/net</path>.
209</note> 209</note>
210 210
211<impo> 211<impo>
212You <e>will</e> need to consult the <uri 212You <e>will</e> need to consult the <uri
213link="?part=4&amp;chap=2#variable_name">variable name</uri> documentation. 213link="?part=4&amp;chap=2#variable_name">variable name</uri> documentation.
220<comment># Configure WEP keys for Access Points called ESSID1 and ESSID2</comment> 220<comment># Configure WEP keys for Access Points called ESSID1 and ESSID2</comment>
221<comment># You may configure up to 4 WEP keys, but only 1 can be active at 221<comment># You may configure up to 4 WEP keys, but only 1 can be active at
222# any time so we supply a default index of [1] to set key [1] and then 222# any time so we supply a default index of [1] to set key [1] and then
223# again afterwards to change the active key to [1] 223# again afterwards to change the active key to [1]
224# We do this incase you define other ESSID's to use WEP keys other than 1 224# We do this incase you define other ESSID's to use WEP keys other than 1
225#
225# Prefixing the key with s: means it's an ASCII key, otherwise a HEX key 226# Prefixing the key with s: means it's an ASCII key, otherwise a HEX key
227#
226# enc open specified open security (most secure) 228# enc open specified open security (most secure)
227# enc restricted specified restricted security (least secure)</comment> 229# enc restricted specified restricted security (least secure)</comment>
228key_ESSID1="[1] s:yourkeyhere key [1] enc open" 230key_ESSID1="[1] s:yourkeyhere key [1] enc open"
229key_ESSID2="[1] aaaa-bbbb-cccc-dd key [1] enc restricted" 231key_ESSID2="[1] aaaa-bbbb-cccc-dd key [1] enc restricted"
230 232
279 Do not scan for APs - instead just try to connect to each one in order 281 Do not scan for APs - instead just try to connect to each one in order
280 </ti> 282 </ti>
281</tr> 283</tr>
282<tr> 284<tr>
283 <ti><c>forceany</c></ti> 285 <ti><c>forceany</c></ti>
284 <ti>Same as forcepreferred + connect to any other available AP</ti> 286 <ti>Same as <c>forcepreferred</c> + connect to any other available AP</ti>
285</tr> 287</tr>
286</table> 288</table>
287 289
288<p> 290<p>
289Finally we have some <c>blacklist_aps</c> and <c>unique_ap</c> selection. 291Finally we have some <c>blacklist_aps</c> and <c>unique_ap</c> selection.
290<c>blacklist_aps</c> works in a similar way to <c>preferred_aps</c>. 292<c>blacklist_aps</c> works in a similar way to <c>preferred_aps</c>.
291<c>unique_ap</c> is a yes or no value that says if a second wireless interface 293<c>unique_ap</c> is a <c>yes</c> or <c>no</c> value that says if a second
292can connect to the same Access Point as the first interface. 294wireless interface can connect to the same Access Point as the first interface.
293</p> 295</p>
294 296
295<pre caption="blacklist_aps and unique_ap example"> 297<pre caption="blacklist_aps and unique_ap example">
296<comment># Sometimes you never want to connect to certain access points</comment> 298<comment># Sometimes you never want to connect to certain access points</comment>
297blacklist_aps=( "ESSID3" "ESSID4" ) 299blacklist_aps=( "ESSID3" "ESSID4" )

Legend:
Removed from v.1.8  
changed lines
  Added in v.1.9

  ViewVC Help
Powered by ViewVC 1.1.20