Em 16-01-2011 18:29, Valmor de Almeida escreveu:
> On 01/15/2011 06:03 AM, doherty pete wrote:
>> yeah!it can work,now,this is my configure:
>> /etc/conf.d/net
>>
>> config_eth0=("null")
>>
>> modules="wpa_supplicant"
>>
>> wpa_supplicant_wlan0="-Dwext"
>>
>> config_wlan0="192.168.1.99 netmask 255.255.255.0"
>>
>> routes_wlan0="default gw 192.168.1.1"
>>
>> //etc/wpa_supplicant/wpa_supplicant.conf/
>> /
>> /
>> /
>> ctrl_interface=/var/run/wpa_supplicant
>>
>> ctrl_interface_group=0
>>
>> ap_scan=1
>>
>> network={
>>     ssid="huang"
>>     proto=WPA2
>>     key_mgmt=WPA-PSK
>>     pairwise=CCMP TKIP
>>     group=CCMP TKIP
>>     psk="Xda111524*&^"
>> }
>>
>> /
>>
>> 2011/1/15 Zhu Sha Zang <zhushaz...@yahoo.com.br
>> <mailto:zhushaz...@yahoo.com.br>>
>>
>>     Em 14-01-2011 14:02, Mick escreveu:
>>>     On 14 January 2011 15:24, doherty pete <nishizaw...@gmail.com> 
>>> <mailto:nishizaw...@gmail.com> wrote:
>>>>     i donn't known what different form wext and madwifi....
>>>>     i just known my wireless is bcm4357...
>>>     If there's a driver in the kernel for your wireless hardware, select
>>>     it and use -Dwext.  The madwifi driver will work with particular
>>>     wireless chipsets only (atheros).  If there is no wireless driver in
>>>     Linux, then use ndiswrapper (you'll need to emerge it) and use the
>>>     MSWindows driver with it - it may work.
>>>
>>     I'm using wpa with openrc:
>>     /
>>     [rodolfo@asgard ~]$ cat /etc/wpa_supplicant/wpa_supplicant.conf
>>
>>     ctrl_interface=/var/run/wpa_supplicant
>>     ctrl_interface_group=0
>>     eapol_version=1
>>
>>     ap_scan=2
>>     fast_reauth=1
>>
>>     network={
>>             ssid="VALHALLA"
>>             proto=RSN
>>             key_mgmt=WPA-PSK
>>             pairwise=CCMP TKIP
>>             group=CCMP TKIP
>>             psk="****************"
>>     }/
>>
>>     /[rodolfo@asgard ~]$ cat
>>     /etc/conf.d/net                                                          
>>         
>>
>>     modules="wpa_supplicant"
>>
>>
>>     wpa_supplicant_wlan0="-Dwext"
>>     wpa_timeout_wlan0=60
>>
>>     config_wlan0="10.10.10.25 netmask 255.255.255.0"
>>     routes_wlan0="default gw 10.10.10.1"
>>
>>
>>     /And works well with /etc/init.d/net.wlan0 start (in boot too)
>>
>>     Att
>>     /
>>     /
>>
>>
>>
>>
>> -- 
>> pete_doherty
> Check the e-mail thread on this list with the subject:
>
>    starting wlan0 only when wireless is turned on
>
>
> http://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg108144.html
>
>
> Just dump all of the network config and use wicd.
>
> --
> Valmor
>
>
>
I think that this software, wicd, is just to ubuntu's users not to
Gentoo. If work without gui,, why i need a gui?

Att



Reply via email to