|
Lines 8-14
Link Here
|
| 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> |
|
Lines 22-28
Link Here
|
| 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. |
| 26 |
For a list of supported drivers, <uri |
26 |
For a list of supported drivers, <uri |
| 27 |
link="http://hostap.epitest.fi/wpa_supplicant">read the wpa_supplicant |
27 |
link="http://hostap.epitest.fi/wpa_supplicant">read the wpa_supplicant |
| 28 |
site</uri>. Also, <c>wpa_supplicant</c> can currently only connect to SSID's |
28 |
site</uri>. Also, <c>wpa_supplicant</c> can currently only connect to SSID's |
|
Lines 35-46
Link Here
|
| 35 |
</p> |
35 |
</p> |
| 36 |
|
36 |
|
| 37 |
<warn> |
37 |
<warn> |
| 38 |
The <c>linux-wlan-ng</c> driver is not supported by <c>baselayout</c> at this |
38 |
The <c>linux-wlan-ng</c> driver is not supported by baselayout at this |
| 39 |
time. This is because <c>linux-wlan-ng</c> have their own setup and |
39 |
time. This is because <c>linux-wlan-ng</c> have their own setup and |
| 40 |
configuration which is completely different to everyone else's. The |
40 |
configuration 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> |
| 43 |
with <c>baselayout</c>. |
43 |
with baselayout. |
| 44 |
</warn> |
44 |
</warn> |
| 45 |
|
45 |
|
| 46 |
</body> |
46 |
</body> |
|
Lines 82-88
Link Here
|
| 82 |
<note> |
82 |
<note> |
| 83 |
If you're using the host-ap driver you will need to put the card in <e>Managed |
83 |
If you're using the host-ap driver you will need to put the card in <e>Managed |
| 84 |
mode</e> before it can be used with <c>wpa_supplicant</c> correctly. You can use |
84 |
mode</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 |
|
|
Lines 205-211
Link Here
|
| 205 |
<note> |
205 |
<note> |
| 206 |
Although you can store your wireless settings in |
206 |
Although 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> |
|
Lines 222-228
Link Here
|
| 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> |
| 228 |
key_ESSID1="[1] s:yourkeyhere key [1] enc open" |
230 |
key_ESSID1="[1] s:yourkeyhere key [1] enc open" |
|
Lines 281-295
Link Here
|
| 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> |
| 289 |
Finally we have some <c>blacklist_aps</c> and <c>unique_ap</c> selection. |
291 |
Finally 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 |
| 292 |
can connect to the same Access Point as the first interface. |
294 |
wireless 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"> |
|
Lines 410-416
Link Here
|
| 410 |
<ti/> |
412 |
<ti/> |
| 411 |
<ti> |
413 |
<ti> |
| 412 |
Some drivers have to scan in ad-hoc mode, so if scanning fails |
414 |
Some drivers have to scan in ad-hoc mode, so if scanning fails |
| 413 |
try setting <c>ad-hoc</c> here |
415 |
try setting <c>ad-hoc</c> here. |
| 414 |
</ti> |
416 |
</ti> |
| 415 |
</tr> |
417 |
</tr> |
| 416 |
<tr> |
418 |
<tr> |
