From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1EvySY-000333-28 for garchives@archives.gentoo.org; Mon, 09 Jan 2006 14:57:22 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k09Ev6Uw023933; Mon, 9 Jan 2006 14:57:06 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k09Ev5QZ026719 for ; Mon, 9 Jan 2006 14:57:05 GMT Message-Id: <200601091457.k09Ev5QZ026719@robin.gentoo.org> Received: from lark.gentoo.osuosl.org ([140.211.166.177] helo=lark.gentoo.org) by smtp.gentoo.org with smtp (Exim 4.54) id 1EvySG-0002XE-Tx for gentoo-doc-cvs@lists.gentoo.org; Mon, 09 Jan 2006 14:57:05 +0000 Received: by lark.gentoo.org (sSMTP sendmail emulation); Mon, 9 Jan 2006 14:57:04 +0000 From: "Jan Kundrat" Date: Mon, 9 Jan 2006 14:57:04 +0000 To: gentoo-doc-cvs@lists.gentoo.org Subject: [gentoo-doc-cvs] cvs commit: hb-net-wireless.xml Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-doc-cvs@gentoo.org Reply-to: docs-team@lists.gentoo.org X-Archives-Salt: 8522e0d1-f8fa-41f4-8553-bfce4153d1e4 X-Archives-Hash: d49c2b91dd4d7b22db983018802be6d1 jkt 06/01/09 14:57:04 Modified: xml/htdocs/doc/en/handbook hb-net-wireless.xml Log: #116267: - s/wpa_suppliant/wpa_supplicant/ - some magic :) Revision Changes Path 1.9 +12 -10 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.9&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.9&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.8&r2=1.9&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.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- hb-net-wireless.xml 23 Dec 2005 21:28:18 -0000 1.8 +++ hb-net-wireless.xml 9 Jan 2006 14:57:04 -0000 1.9 @@ -4,11 +4,11 @@ - + -1.3 +1.4 2005-12-22
@@ -22,7 +22,7 @@

-wpa_suppliant is the best choice, but it does not support all drivers. +wpa_supplicant is the best choice, but it does not support all drivers. For a list of supported drivers, read the wpa_supplicant site. Also, wpa_supplicant can currently only connect to SSID's @@ -35,12 +35,12 @@

-The linux-wlan-ng driver is not supported by baselayout at this +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. +with baselayout. @@ -82,7 +82,7 @@ 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 -iwconfig_eth0="mode managed" to achieve this in +iwconfig_eth0="mode managed" to achieve this in /etc/conf.d/net. @@ -205,7 +205,7 @@ Although you can store your wireless settings in /etc/conf.d/wireless this guide recommends you store them in -/etc/conf.d/net +/etc/conf.d/net. @@ -222,7 +222,9 @@ # any time so we supply a default index of [1] to set key [1] and then # again afterwards to change the active key to [1] # We do this incase you define other ESSID's to use WEP keys other than 1 +# # Prefixing the key with s: means it's an ASCII key, otherwise a HEX key +# # enc open specified open security (most secure) # enc restricted specified restricted security (least secure) key_ESSID1="[1] s:yourkeyhere key [1] enc open" @@ -281,15 +283,15 @@ forceany - Same as forcepreferred + connect to any other available AP + Same as forcepreferred + connect to any other available AP

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. +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. 




-- 
gentoo-doc-cvs@gentoo.org mailing list