| 1 |
jkt 05/12/21 13:16:02 |
| 2 |
|
| 3 |
Modified: xml/htdocs/doc/en/handbook hb-net-wireless.xml |
| 4 |
Log: |
| 5 |
coding style fixes, *no content change* |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.6 +66 -69 xml/htdocs/doc/en/handbook/hb-net-wireless.xml |
| 9 |
|
| 10 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-wireless.xml?rev=1.6&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 11 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-wireless.xml?rev=1.6&content-type=text/plain&cvsroot=gentoo |
| 12 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-wireless.xml.diff?r1=1.5&r2=1.6&cvsroot=gentoo |
| 13 |
|
| 14 |
Index: hb-net-wireless.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml,v |
| 17 |
retrieving revision 1.5 |
| 18 |
retrieving revision 1.6 |
| 19 |
diff -u -r1.5 -r1.6 |
| 20 |
--- hb-net-wireless.xml 2 Aug 2005 07:41:26 -0000 1.5 |
| 21 |
+++ hb-net-wireless.xml 21 Dec 2005 13:16:02 -0000 1.6 |
| 22 |
@@ -4,7 +4,7 @@ |
| 23 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 24 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 25 |
|
| 26 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml,v 1.5 2005/08/02 07:41:26 swift Exp $ --> |
| 27 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml,v 1.6 2005/12/21 13:16:02 jkt Exp $ --> |
| 28 |
|
| 29 |
<sections> |
| 30 |
|
| 31 |
@@ -16,30 +16,30 @@ |
| 32 |
<body> |
| 33 |
|
| 34 |
<p> |
| 35 |
-Currently we support wireless setup either by wireless-tools or |
| 36 |
-wpa_supplicant. The important thing to remember is that you configure for |
| 37 |
-wireless networks on a global basis and not an interface basis. |
| 38 |
+Currently we support wireless setup either by wireless-tools or wpa_supplicant. |
| 39 |
+The important thing to remember is that you configure for wireless networks on a |
| 40 |
+global basis and not an interface basis. |
| 41 |
</p> |
| 42 |
|
| 43 |
<p> |
| 44 |
-wpa_suppliant is the best choice, but it does not support all drivers. |
| 45 |
-For a list of supported drivers, |
| 46 |
-<uri link="http://hostap.epitest.fi/wpa_supplicant">read the wpa_supplicant |
| 47 |
+wpa_suppliant is the best choice, but it does not support all drivers. For a |
| 48 |
+list of supported drivers, <uri |
| 49 |
+link="http://hostap.epitest.fi/wpa_supplicant">read the wpa_supplicant |
| 50 |
site</uri>. Also, wpa_supplicant can currently only connect to SSID's that |
| 51 |
you have configured for. |
| 52 |
</p> |
| 53 |
|
| 54 |
<p> |
| 55 |
-wireless-tools supports nearly all cards and drivers, but it cannot connect |
| 56 |
-to WPA only Access Points. |
| 57 |
+wireless-tools supports nearly all cards and drivers, but it cannot connect to |
| 58 |
+WPA only Access Points. |
| 59 |
</p> |
| 60 |
|
| 61 |
<warn> |
| 62 |
-The linux-wlan-ng driver is not supported by baselayout at this time. |
| 63 |
-This is because linux-wlan-ng have their own setup and configuration |
| 64 |
-which is completely different to everyone else's. The linux-wlan-ng devs |
| 65 |
-are rumoured to be changing their setup over to wireless-tools - when this |
| 66 |
-happens you may use linux-wlan-ng with baselayout. |
| 67 |
+The linux-wlan-ng driver is not supported by baselayout at this time. This is |
| 68 |
+because linux-wlan-ng have their own setup and configuration which is completely |
| 69 |
+different to everyone else's. The linux-wlan-ng devs are rumoured to be changing |
| 70 |
+their setup over to wireless-tools - when this happens you may use linux-wlan-ng |
| 71 |
+with baselayout. |
| 72 |
</warn> |
| 73 |
|
| 74 |
</body> |
| 75 |
@@ -49,10 +49,9 @@ |
| 76 |
<body> |
| 77 |
|
| 78 |
<p> |
| 79 |
-<uri link="http://hostap.epitest.fi/wpa_supplicant">WPA Supplicant</uri> is |
| 80 |
-a package that allows you to connect to WPA enabled access points. It's setup |
| 81 |
-is fairly fluid as it is still in beta - however it works fine for the most |
| 82 |
-part. |
| 83 |
+<uri link="http://hostap.epitest.fi/wpa_supplicant">WPA Supplicant</uri> is a |
| 84 |
+package that allows you to connect to WPA enabled access points. It's setup is |
| 85 |
+fairly fluid as it is still in beta - however it works fine for the most part. |
| 86 |
</p> |
| 87 |
|
| 88 |
<pre caption="Install wpa_supplicant"> |
| 89 |
@@ -66,8 +65,8 @@ |
| 90 |
|
| 91 |
<p> |
| 92 |
Now we have to configure <path>/etc/conf.d/net</path> to so that we prefer |
| 93 |
-wpa_supplicant over wireless-tools (if both are installed, wireless-tools |
| 94 |
-is the default). |
| 95 |
+wpa_supplicant over wireless-tools (if both are installed, wireless-tools is the |
| 96 |
+default). |
| 97 |
</p> |
| 98 |
|
| 99 |
<pre caption="configure /etc/conf.d/net for wpa_supplicant"> |
| 100 |
@@ -80,18 +79,18 @@ |
| 101 |
</pre> |
| 102 |
|
| 103 |
<note> |
| 104 |
-If you're using the host-ap driver you will need to put the card in Managed |
| 105 |
-mode before it can be used with wpa_supplicant correctly. You can use |
| 106 |
+If you're using the host-ap driver you will need to put the card in Managed mode |
| 107 |
+before it can be used with wpa_supplicant correctly. You can use |
| 108 |
<e>iwconfig_eth0="mode managed"</e> to achieve this in |
| 109 |
<path>/etc/conf.d/net</path>. |
| 110 |
</note> |
| 111 |
|
| 112 |
<p> |
| 113 |
That was simple wasn't it? However, we still have to configure wpa_supplicant |
| 114 |
-itself which is a bit more tricky depending on how secure the Access Points |
| 115 |
-are that you are trying to connect to. The below example is taken and |
| 116 |
-simplified from <path>/etc/wpa_supplicant.conf.example</path> which ships |
| 117 |
-with wpa_supplicant. |
| 118 |
+itself which is a bit more tricky depending on how secure the Access Points are |
| 119 |
+that you are trying to connect to. The below example is taken and simplified |
| 120 |
+from <path>/etc/wpa_supplicant.conf.example</path> which ships with |
| 121 |
+wpa_supplicant. |
| 122 |
</p> |
| 123 |
|
| 124 |
<pre caption="an example /etc/wpa_supplicant.conf"> |
| 125 |
@@ -184,17 +183,18 @@ |
| 126 |
<body> |
| 127 |
|
| 128 |
<p> |
| 129 |
-<uri link="http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html"> |
| 130 |
-Wireless Tools</uri> provide a generic way to configure basic wireless |
| 131 |
-interfaces up to the WEP security level. While WEP is a weak security method |
| 132 |
-it's also the most prevalent. |
| 133 |
+<uri |
| 134 |
+link="http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html">Wireless |
| 135 |
+Tools</uri> provide a generic way to configure basic wireless interfaces up to |
| 136 |
+the WEP security level. While WEP is a weak security method it's also the most |
| 137 |
+prevalent. |
| 138 |
</p> |
| 139 |
|
| 140 |
<p> |
| 141 |
-Wireless Tools configuration is controlled by a few main variables. The |
| 142 |
-sample configuration file below should describe all you need. One thing to |
| 143 |
-bear in mind is that no configuration means "connect to the strongest |
| 144 |
-unencrypted Access Point" - we will always try and connect you to something. |
| 145 |
+Wireless Tools configuration is controlled by a few main variables. The sample |
| 146 |
+configuration file below should describe all you need. One thing to bear in mind |
| 147 |
+is that no configuration means "connect to the strongest unencrypted Access |
| 148 |
+Point" - we will always try and connect you to something. |
| 149 |
</p> |
| 150 |
|
| 151 |
<pre caption="Install wireless-tools"> |
| 152 |
@@ -208,9 +208,8 @@ |
| 153 |
</note> |
| 154 |
|
| 155 |
<impo> |
| 156 |
-You <e>will</e> need to consult the |
| 157 |
-<uri link="?part=4&chap=2#variable_name">variable name</uri> |
| 158 |
-documentation. |
| 159 |
+You <e>will</e> need to consult the <uri |
| 160 |
+link="?part=4&chap=2#variable_name">variable name</uri> documentation. |
| 161 |
</impo> |
| 162 |
|
| 163 |
<pre caption="sample iwconfig setup in /etc/conf.d/net"> |
| 164 |
@@ -242,16 +241,15 @@ |
| 165 |
<body> |
| 166 |
|
| 167 |
<p> |
| 168 |
-You can add some extra options to fine-tune your Access Point selection, |
| 169 |
-but these are not normally required. |
| 170 |
+You can add some extra options to fine-tune your Access Point selection, but |
| 171 |
+these are not normally required. |
| 172 |
</p> |
| 173 |
|
| 174 |
<p> |
| 175 |
-You can decide whether we only connect to preferred Access Points or not. |
| 176 |
-By default if everything configured has failed and we can connect to an |
| 177 |
-unencrypted Access Point then we will. This can be controlled by the |
| 178 |
-<c>associate_order</c> variable. Here's a table of values and how they |
| 179 |
-control this. |
| 180 |
+You can decide whether we only connect to preferred Access Points or not. By |
| 181 |
+default if everything configured has failed and we can connect to an unencrypted |
| 182 |
+Access Point then we will. This can be controlled by the <c>associate_order</c> |
| 183 |
+variable. Here's a table of values and how they control this. |
| 184 |
</p> |
| 185 |
|
| 186 |
<table> |
| 187 |
@@ -287,10 +285,10 @@ |
| 188 |
</table> |
| 189 |
|
| 190 |
<p> |
| 191 |
-Finally we have some blacklist_aps and unique_ap selection. blacklist_aps |
| 192 |
-works in a similar way to preferred_aps. unique_ap is a yes or no value |
| 193 |
-that says if a second wireless interface can connect to the same Access |
| 194 |
-Point as the first interface. |
| 195 |
+Finally we have some blacklist_aps and unique_ap selection. blacklist_aps works |
| 196 |
+in a similar way to preferred_aps. unique_ap is a yes or no value that says if a |
| 197 |
+second wireless interface can connect to the same Access Point as the first |
| 198 |
+interface. |
| 199 |
</p> |
| 200 |
|
| 201 |
<pre caption="blacklist_aps and unique_ap example"> |
| 202 |
@@ -311,8 +309,8 @@ |
| 203 |
<body> |
| 204 |
|
| 205 |
<p> |
| 206 |
-If you want to set yourself up as an Ad-Hoc node if you fail to connect to |
| 207 |
-any Access Point in managed mode, you can do that too. |
| 208 |
+If you want to set yourself up as an Ad-Hoc node if you fail to connect to any |
| 209 |
+Access Point in managed mode, you can do that too. |
| 210 |
</p> |
| 211 |
|
| 212 |
<pre caption="fallback to ad-hoc mode"> |
| 213 |
@@ -320,9 +318,9 @@ |
| 214 |
</pre> |
| 215 |
|
| 216 |
<p> |
| 217 |
-What about connecting to Ad-Hoc networks or running in Master mode to become |
| 218 |
-an Access Point? Here's a configuration just for that! You may need to |
| 219 |
-specify WEP keys as shown above. |
| 220 |
+What about connecting to Ad-Hoc networks or running in Master mode to become an |
| 221 |
+Access Point? Here's a configuration just for that! You may need to specify WEP |
| 222 |
+keys as shown above. |
| 223 |
</p> |
| 224 |
|
| 225 |
<pre caption="sample ad-hoc/master configuration"> |
| 226 |
@@ -340,16 +338,15 @@ |
| 227 |
</pre> |
| 228 |
|
| 229 |
<impo> |
| 230 |
-The below is taken verbatim from the BSD wavelan documentation found at |
| 231 |
-<uri link="http://www.netbsd.org/Documentation/network/wavelan.html"> |
| 232 |
-the NetBSD documentation</uri>. |
| 233 |
-There are 14 channels possible; We are told that channels 1-11 are legal for |
| 234 |
-North America, channels 1-13 for most of Europe, channels 10-13 for France, |
| 235 |
-and only channel 14 for Japan. If in doubt, please refer to the documentation |
| 236 |
-that came with your card or access point. Make sure that the channel you |
| 237 |
-select is the same channel your access point (or the other card in an ad-hoc |
| 238 |
-network) is on. The default for cards sold in North America and most of |
| 239 |
-Europe is 3; the default for cards sold in France is 11, and the default for |
| 240 |
+The below is taken verbatim from the BSD wavelan documentation found at <uri |
| 241 |
+link="http://www.netbsd.org/Documentation/network/wavelan.html">the NetBSD |
| 242 |
+documentation</uri>. There are 14 channels possible; We are told that channels |
| 243 |
+1-11 are legal for North America, channels 1-13 for most of Europe, channels |
| 244 |
+10-13 for France, and only channel 14 for Japan. If in doubt, please refer to |
| 245 |
+the documentation that came with your card or access point. Make sure that the |
| 246 |
+channel you select is the same channel your access point (or the other card in |
| 247 |
+an ad-hoc network) is on. The default for cards sold in North America and most |
| 248 |
+of Europe is 3; the default for cards sold in France is 11, and the default for |
| 249 |
cards sold in Japan is 14. |
| 250 |
</impo> |
| 251 |
|
| 252 |
@@ -360,9 +357,9 @@ |
| 253 |
<body> |
| 254 |
|
| 255 |
<p> |
| 256 |
-There are some more variables you can use to help get your wireless up |
| 257 |
-and running due to driver or environment problems. Here's a table of other |
| 258 |
-things you can try. |
| 259 |
+There are some more variables you can use to help get your wireless up and |
| 260 |
+running due to driver or environment problems. Here's a table of other things |
| 261 |
+you can try. |
| 262 |
</p> |
| 263 |
|
| 264 |
<table> |
| 265 |
@@ -442,9 +439,9 @@ |
| 266 |
<body> |
| 267 |
|
| 268 |
<p> |
| 269 |
-Someones when you connect to ESSID1 you need a static IP and when you |
| 270 |
-connect to ESSID2 you need DHCP. Infact most module variables we can |
| 271 |
-change per ESSID. Here's how we do this. |
| 272 |
+Someones when you connect to ESSID1 you need a static IP and when you connect to |
| 273 |
+ESSID2 you need DHCP. Infact most module variables we can change per ESSID. |
| 274 |
+Here's how we do this. |
| 275 |
</p> |
| 276 |
|
| 277 |
<note> |
| 278 |
|
| 279 |
|
| 280 |
|
| 281 |
-- |
| 282 |
gentoo-doc-cvs@g.o mailing list |
Archives