From: "Jan Kundrat" <jkt@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: hb-net-wireless.xml
Date: Wed, 21 Dec 2005 13:16:02 +0000 [thread overview]
Message-ID: <200512211316.jBLDG38R017910@robin.gentoo.org> (raw)
jkt 05/12/21 13:16:02
Modified: xml/htdocs/doc/en/handbook hb-net-wireless.xml
Log:
coding style fixes, *no content change*
Revision Changes Path
1.6 +66 -69 xml/htdocs/doc/en/handbook/hb-net-wireless.xml
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
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
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
Index: hb-net-wireless.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- hb-net-wireless.xml 2 Aug 2005 07:41:26 -0000 1.5
+++ hb-net-wireless.xml 21 Dec 2005 13:16:02 -0000 1.6
@@ -4,7 +4,7 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml,v 1.5 2005/08/02 07:41:26 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml,v 1.6 2005/12/21 13:16:02 jkt Exp $ -->
<sections>
@@ -16,30 +16,30 @@
<body>
<p>
-Currently we support wireless setup either by wireless-tools or
-wpa_supplicant. The important thing to remember is that you configure for
-wireless networks on a global basis and not an interface basis.
+Currently we support wireless setup either by wireless-tools or wpa_supplicant.
+The important thing to remember is that you configure for wireless networks on a
+global basis and not an interface basis.
</p>
<p>
-wpa_suppliant is the best choice, but it does not support all drivers.
-For a list of supported drivers,
-<uri link="http://hostap.epitest.fi/wpa_supplicant">read the wpa_supplicant
+wpa_suppliant is the best choice, but it does not support all drivers. For a
+list of supported drivers, <uri
+link="http://hostap.epitest.fi/wpa_supplicant">read the wpa_supplicant
site</uri>. Also, wpa_supplicant can currently only connect to SSID's that
you have configured for.
</p>
<p>
-wireless-tools supports nearly all cards and drivers, but it cannot connect
-to WPA only Access Points.
+wireless-tools supports nearly all cards and drivers, but it cannot connect to
+WPA only Access Points.
</p>
<warn>
-The linux-wlan-ng driver is not supported by baselayout at this time.
-This is because linux-wlan-ng have their own setup and configuration
-which is completely different to everyone else's. The linux-wlan-ng devs
-are rumoured to be changing their setup over to wireless-tools - when this
-happens you may use linux-wlan-ng with baselayout.
+The linux-wlan-ng driver is not supported by baselayout at this time. This is
+because linux-wlan-ng have their own setup and configuration which is completely
+different to everyone else's. The linux-wlan-ng devs are rumoured to be changing
+their setup over to wireless-tools - when this happens you may use linux-wlan-ng
+with baselayout.
</warn>
</body>
@@ -49,10 +49,9 @@
<body>
<p>
-<uri link="http://hostap.epitest.fi/wpa_supplicant">WPA Supplicant</uri> is
-a package that allows you to connect to WPA enabled access points. It's setup
-is fairly fluid as it is still in beta - however it works fine for the most
-part.
+<uri link="http://hostap.epitest.fi/wpa_supplicant">WPA Supplicant</uri> is a
+package that allows you to connect to WPA enabled access points. It's setup is
+fairly fluid as it is still in beta - however it works fine for the most part.
</p>
<pre caption="Install wpa_supplicant">
@@ -66,8 +65,8 @@
<p>
Now we have to configure <path>/etc/conf.d/net</path> to so that we prefer
-wpa_supplicant over wireless-tools (if both are installed, wireless-tools
-is the default).
+wpa_supplicant over wireless-tools (if both are installed, wireless-tools is the
+default).
</p>
<pre caption="configure /etc/conf.d/net for wpa_supplicant">
@@ -80,18 +79,18 @@
</pre>
<note>
-If you're using the host-ap driver you will need to put the card in Managed
-mode before it can be used with wpa_supplicant correctly. You can use
+If you're using the host-ap driver you will need to put the card in Managed mode
+before it can be used with wpa_supplicant correctly. You can use
<e>iwconfig_eth0="mode managed"</e> to achieve this in
<path>/etc/conf.d/net</path>.
</note>
<p>
That was simple wasn't it? However, we still have to configure wpa_supplicant
-itself which is a bit more tricky depending on how secure the Access Points
-are that you are trying to connect to. The below example is taken and
-simplified from <path>/etc/wpa_supplicant.conf.example</path> which ships
-with wpa_supplicant.
+itself which is a bit more tricky depending on how secure the Access Points are
+that you are trying to connect to. The below example is taken and simplified
+from <path>/etc/wpa_supplicant.conf.example</path> which ships with
+wpa_supplicant.
</p>
<pre caption="an example /etc/wpa_supplicant.conf">
@@ -184,17 +183,18 @@
<body>
<p>
-<uri link="http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html">
-Wireless Tools</uri> provide a generic way to configure basic wireless
-interfaces up to the WEP security level. While WEP is a weak security method
-it's also the most prevalent.
+<uri
+link="http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html">Wireless
+Tools</uri> provide a generic way to configure basic wireless interfaces up to
+the WEP security level. While WEP is a weak security method it's also the most
+prevalent.
</p>
<p>
-Wireless Tools configuration is controlled by a few main variables. The
-sample configuration file below should describe all you need. One thing to
-bear in mind is that no configuration means "connect to the strongest
-unencrypted Access Point" - we will always try and connect you to something.
+Wireless Tools configuration is controlled by a few main variables. The sample
+configuration file below should describe all you need. One thing to bear in mind
+is that no configuration means "connect to the strongest unencrypted Access
+Point" - we will always try and connect you to something.
</p>
<pre caption="Install wireless-tools">
@@ -208,9 +208,8 @@
</note>
<impo>
-You <e>will</e> need to consult the
-<uri link="?part=4&chap=2#variable_name">variable name</uri>
-documentation.
+You <e>will</e> need to consult the <uri
+link="?part=4&chap=2#variable_name">variable name</uri> documentation.
</impo>
<pre caption="sample iwconfig setup in /etc/conf.d/net">
@@ -242,16 +241,15 @@
<body>
<p>
-You can add some extra options to fine-tune your Access Point selection,
-but these are not normally required.
+You can add some extra options to fine-tune your Access Point selection, but
+these are not normally required.
</p>
<p>
-You can decide whether we only connect to preferred Access Points or not.
-By default if everything configured has failed and we can connect to an
-unencrypted Access Point then we will. This can be controlled by the
-<c>associate_order</c> variable. Here's a table of values and how they
-control this.
+You can decide whether we only connect to preferred Access Points or not. By
+default if everything configured has failed and we can connect to an unencrypted
+Access Point then we will. This can be controlled by the <c>associate_order</c>
+variable. Here's a table of values and how they control this.
</p>
<table>
@@ -287,10 +285,10 @@
</table>
<p>
-Finally we have some blacklist_aps and unique_ap selection. blacklist_aps
-works in a similar way to preferred_aps. unique_ap is a yes or no value
-that says if a second wireless interface can connect to the same Access
-Point as the first interface.
+Finally we have some blacklist_aps and unique_ap selection. blacklist_aps works
+in a similar way to preferred_aps. unique_ap is a yes or no value that says if a
+second wireless interface can connect to the same Access Point as the first
+interface.
</p>
<pre caption="blacklist_aps and unique_ap example">
@@ -311,8 +309,8 @@
<body>
<p>
-If you want to set yourself up as an Ad-Hoc node if you fail to connect to
-any Access Point in managed mode, you can do that too.
+If you want to set yourself up as an Ad-Hoc node if you fail to connect to any
+Access Point in managed mode, you can do that too.
</p>
<pre caption="fallback to ad-hoc mode">
@@ -320,9 +318,9 @@
</pre>
<p>
-What about connecting to Ad-Hoc networks or running in Master mode to become
-an Access Point? Here's a configuration just for that! You may need to
-specify WEP keys as shown above.
+What about connecting to Ad-Hoc networks or running in Master mode to become an
+Access Point? Here's a configuration just for that! You may need to specify WEP
+keys as shown above.
</p>
<pre caption="sample ad-hoc/master configuration">
@@ -340,16 +338,15 @@
</pre>
<impo>
-The below is taken verbatim from the BSD wavelan documentation found at
-<uri link="http://www.netbsd.org/Documentation/network/wavelan.html">
-the NetBSD documentation</uri>.
-There are 14 channels possible; We are told that channels 1-11 are legal for
-North America, channels 1-13 for most of Europe, channels 10-13 for France,
-and only channel 14 for Japan. If in doubt, please refer to the documentation
-that came with your card or access point. Make sure that the channel you
-select is the same channel your access point (or the other card in an ad-hoc
-network) is on. The default for cards sold in North America and most of
-Europe is 3; the default for cards sold in France is 11, and the default for
+The below is taken verbatim from the BSD wavelan documentation found at <uri
+link="http://www.netbsd.org/Documentation/network/wavelan.html">the NetBSD
+documentation</uri>. There are 14 channels possible; We are told that channels
+1-11 are legal for North America, channels 1-13 for most of Europe, channels
+10-13 for France, and only channel 14 for Japan. If in doubt, please refer to
+the documentation that came with your card or access point. Make sure that the
+channel you select is the same channel your access point (or the other card in
+an ad-hoc network) is on. The default for cards sold in North America and most
+of Europe is 3; the default for cards sold in France is 11, and the default for
cards sold in Japan is 14.
</impo>
@@ -360,9 +357,9 @@
<body>
<p>
-There are some more variables you can use to help get your wireless up
-and running due to driver or environment problems. Here's a table of other
-things you can try.
+There are some more variables you can use to help get your wireless up and
+running due to driver or environment problems. Here's a table of other things
+you can try.
</p>
<table>
@@ -442,9 +439,9 @@
<body>
<p>
-Someones when you connect to ESSID1 you need a static IP and when you
-connect to ESSID2 you need DHCP. Infact most module variables we can
-change per ESSID. Here's how we do this.
+Someones when you connect to ESSID1 you need a static IP and when you connect to
+ESSID2 you need DHCP. Infact most module variables we can change per ESSID.
+Here's how we do this.
</p>
<note>
--
gentoo-doc-cvs@gentoo.org mailing list
next reply other threads:[~2005-12-21 13:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 13:16 Jan Kundrat [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-20 10:14 [gentoo-doc-cvs] cvs commit: hb-net-wireless.xml Josh Saddler
2006-01-27 16:56 Marcelo Goes
2006-01-09 14:59 Jan Kundrat
2006-01-09 14:57 Jan Kundrat
2005-12-23 21:28 Xavier Neys
2005-08-02 7:41 Sven Vermeulen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200512211316.jBLDG38R017910@robin.gentoo.org \
--to=jkt@lark.gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox