Attachment 75271 Details for Bug 116267 – hb-net-wireless.patch

[patch] hb-net-wireless.patch

hb-net-wireless.patch (text/plain), 8.93 KB, created by Jan Kundrát (RETIRED) on 2005-12-21 05:25:53 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Jan Kundrát (RETIRED)

Created: 2005-12-21 05:25:53 UTC

Size: 8.93 KB

patch

obsolete

>Index: doc/en/handbook/hb-net-wireless.xml
>===================================================================
>RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml,v
>retrieving revision 1.6
>diff -u -b -B -r1.6 hb-net-wireless.xml
>--- doc/en/handbook/hb-net-wireless.xml	21 Dec 2005 13:16:02 -0000	1.6
>+++ doc/en/handbook/hb-net-wireless.xml	21 Dec 2005 13:25:26 -0000
>@@ -8,38 +8,39 @@
> 
> <sections>
> 
>-<version>1.2</version>
>-<date>2005-08-02</date>
>+<version>1.3</version>
>+<date>2005-12-21</date>
> 
> <section>
> <title>Introduction</title>
> <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 <c>wireless-tools</c> or
>+<c>wpa_supplicant</c>. 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
>+<c>wpa_suppliant</c> 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.
>+site</uri>. Also, <c>wpa_supplicant</c> 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.
>+<c>wireless-tools</c> 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 <c>linux-wlan-ng</c> driver is not supported by <c>baselayout</c> at this
>+time. This is because <c>linux-wlan-ng</c> have their own setup and
>+configuration which is completely different to everyone else's. The
>+<c>linux-wlan-ng</c> devs are rumoured to be changing their setup over to
>+<c>wireless-tools</c> - when this happens you may use <c>linux-wlan-ng</c>
>+with <c>baselayout</c>.
> </warn>
> 
> </body>
>@@ -59,14 +60,14 @@
> </pre>
> 
> <impo>
>-You have to have CONFIG_PACKET enabled in your kernel for wpa_supplicant to
>-work.
>+You have to have <c>CONFIG_PACKET</c> enabled in your kernel for
>+<c>wpa_supplicant</c> to work.
> </impo>
> 
> <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).
>+<c>wpa_supplicant</c> over <c>wireless-tools</c> (if both are installed,
>+<c>wireless-tools</c> is the default).
> </p>
> 
> <pre caption="configure /etc/conf.d/net for wpa_supplicant">
>@@ -79,18 +80,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 <e>Managed
>+mode</e> before it can be used with <c>wpa_supplicant</c> 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.
>+That was simple wasn't it? However, we still have to configure
>+<c>wpa_supplicant</c> 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 <c>wpa_supplicant</c>.
> </p>
> 
> <pre caption="an example /etc/wpa_supplicant.conf">
>@@ -258,37 +259,37 @@
>   <th>Description</th>
> </tr>
> <tr>
>-  <ti>any</ti>
>+  <ti><c>any</c></ti>
>   <ti>Default behaviour</ti>
> </tr>
> <tr>
>-  <ti>preferredonly</ti>
>+  <ti><c>preferredonly</c></ti>
>   <ti>We will only connect to visible APs in the preferred list</ti>
> </tr>
> <tr>
>-  <ti>forcepreferred</ti>
>+  <ti><c>forcepreferred</c></ti>
>   <ti>
>     We will forceably connect to APs in the preferred order if they are not
>     found in a scan
>   </ti>
> </tr>
> <tr>
>-  <ti>forcepreferredonly</ti>
>+  <ti><c>forcepreferredonly</c></ti>
>   <ti>
>     Do not scan for APs - instead just try to connect to each one in order
>   </ti>
> </tr>
> <tr>
>-  <ti>forceany</ti>
>+  <ti><c>forceany</c></ti>
>   <ti>Same as forcepreferred + connect to any other available AP</ti>
> </tr>
> </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 <c>blacklist_aps</c> and <c>unique_ap</c> selection.
>+<c>blacklist_aps</c> works in a similar way to <c>preferred_aps</c>.
>+<c>unique_ap</c> 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">
>@@ -369,64 +370,63 @@
>   <th>Description</th>
> </tr>
> <tr>
>-  <ti>iwconfig_eth0</ti>
>+  <ti><c>iwconfig_eth0</c></ti>
>   <ti/>
>-  <ti>See the iwconfig man page for details on what to send iwconfig</ti>
>+  <ti>See the iwconfig man page for details on what to send <c>iwconfig</c></ti>
> </tr>
> <tr>
>-  <ti>iwpriv_eth0</ti>
>+  <ti><c>iwpriv_eth0</c></ti>
>   <ti/>
>-  <ti>See the iwpriv man page for details on what to send iwpriv</ti>
>+  <ti>See the iwpriv man page for details on what to send <c>iwpriv</c></ti>
> </tr>
> <tr>
>-  <ti>sleep_scan_eth0</ti>
>-  <ti>0</ti>
>+  <ti><c>sleep_scan_eth0</c></ti>
>+  <ti><c>0</c></ti>
>   <ti>
>     The number of seconds to sleep before attempting to scan. This is needed
>     when the driver/firmware needs more time to active before it can be used.
>   </ti>
> </tr>
> <tr>
>-  <ti>sleep_associate_eth0</ti>
>-  <ti>5</ti>
>+  <ti><c>sleep_associate_eth0</c></ti>
>+  <ti><c>5</c></ti>
>   <ti>
>     The number of seconds to wait for the interface to associate with the
>     Access Point before moving onto the next one
>   </ti>
> </tr>
> <tr>
>-  <ti>associate_test_eth0</ti>
>-  <ti>MAC</ti>
>+  <ti><c>associate_test_eth0</c></ti>
>+  <ti><c>MAC</c></ti>
>   <ti>
>-    Some drivers do not reset the MAC address associated with to an
>-    invalid one when they loose or attempt to associate.
>-    Some drivers do not reset the quality level when they loose
>-    or attempt assocciation.
>-    Valid settings are MAC, quality and all.
>+    Some drivers do not reset the MAC address associated with to an invalid one
>+    when they loose or attempt to associate. Some drivers do not reset the
>+    quality level when they loose or attempt assocciation. Valid settings are
>+    <c>MAC</c>, <c>quality</c> and <c>all</c>.
>   </ti>
> </tr>
> <tr>
>-  <ti>scan_mode_eth0</ti>
>+  <ti><c>scan_mode_eth0</c></ti>
>   <ti/>
>   <ti>
>     Some drivers have to scan in ad-hoc mode, so if scanning fails
>-    try setting ad-hoc here
>+    try setting <c>ad-hoc</c> here
>   </ti>
> </tr>
> <tr>
>-  <ti>iwpriv_scan_pre_eth0</ti>
>+  <ti><c>iwpriv_scan_pre_eth0</c></ti>
>   <ti/>
>   <ti>
>-    Sends some iwpriv commands to the interface before scanning.
>-    See the iwpriv man page for more details
>+    Sends some <c>iwpriv</c> commands to the interface before scanning.
>+    See the iwpriv man page for more details.
>   </ti>
> </tr>
> <tr>
>-  <ti>iwpriv_scan_post_eth0</ti>
>+  <ti><c>iwpriv_scan_post_eth0</c></ti>
>   <ti/>
>   <ti>
>-    Sends some iwpriv commands to the interface after scanning.
>-    See the iwpriv man page for more details
>+    Sends some <c>iwpriv</c> commands to the interface after scanning.
>+    See the iwpriv man page for more details.
>   </ti>
> </tr>
> </table>
>@@ -439,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 <e>ESSID1</e> you need a static IP and when you
>+connect to <e>ESSID2</e> you need DHCP. Infact most module variables we can
>+change per ESSID. Here's how we do this.
> </p>
> 
> <note>
>@@ -449,9 +449,8 @@
> </note>
> 
> <impo>
>-You <e>will</e> need to consult the
>-<uri link="?part=4&amp;chap=2#variable_name">variable name</uri>
>-documentation.
>+You <e>will</e> need to consult the <uri
>+link="?part=4&amp;chap=2#variable_name">variable name</uri> documentation.
> </impo>
> 
> <pre caption="override network settings per ESSID">

Actions: View | Diff

Attachments on bug 116267: 75265 | 75266 | 75267 | 75270 | 75271 | 75272 | 75273 | 76467 | 76483