Olá a todos. Bem com tudo o que foi exposto, parti para a prática. Tudo
aparentemente dá certo. A configuração do wpa_supplicant.conf foi bem. A
placa é reconhecida a rede idem. Só que acabo por não conseguir conexão.
Ao aplicar o comando abaixo, não finaliza nunca:
#wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf -d -D wext
....................................................................................................
Starting AP scan for wildcard SSID
ioctl[SIOCSIWSCAN]: Network is down
Scan requested (ret=-1) - scan timeout 30 seconds
Failed to initiate AP scan.
State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
Setting scan request: 1 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan for wildcard SSID
ioctl[SIOCSIWSCAN]: Network is down
Scan requested (ret=-1) - scan timeout 30 seconds
Failed to initiate AP scan.
State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
Setting scan request: 1 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan for wildcard SSID
ioctl[SIOCSIWSCAN]: Network is down
Scan requested (ret=-1) - scan timeout 30 seconds
Failed to initiate AP scan.
State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
Setting scan request: 1 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan for wildcard SSID
ioctl[SIOCSIWSCAN]: Network is down
Scan requested (ret=-1) - scan timeout 30 seconds
Failed to initiate AP scan.
State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
Setting scan request: 1 sec 0 usec
^CCTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
No keys have been configured - skip key clearing
State: DISCONNECTED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Removed BSSID 00:21:29:d7:99:51 from blacklist (clear)
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)
Cancelling scan request
Cancelling authentication timeout
netlink: Operstate: linkmode=0, operstate=6
WPA: Key negotiation completed with 00:21:29:d7:99:51 [PTK=CCMP GTK=TKIP]
Cancelling authentication timeout
State: GROUP_HANDSHAKE -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:21:29:d7:99:51 completed (auth)
[id=0 id_str=]
wpa_driver_wext_set_operstate: operstate 0->1 (UP)
netlink: Operstate: linkmode=-1, operstate=6
EAPOL: External notification - portValid=1
EAPOL: External notification - EAP success=1
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state SUCCESS
EAP: EAP entering state DISABLED
EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: Supplicant port status: Authorized
EAPOL: SUPP_BE entering state IDLE
EAPOL authentication completed successfully
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
EAPOL: startWhen --> 0
EAPOL: disable timer tick
..............................................................................................
# iwconfig wlan0 key 78901iuytoplj88a
Error for wireless request "Set Encode" (8B2A) :
invalid argument "78901iuytoplj88a".
bash-4.1#
..............................................................................................
Já o comando abaixo dá retorno:
bash-4.1# wpa_passphrase razec 78901iuytoplj88a
network={
ssid="razec"
#psk="78901iuytoplj88a"
psk=d407b1adaabdd99d354cc8c0a1de863b9bf6fc72fa11655e1f7a32c954272192
}
Enfim, não estou conseguindo conectar
Em 26 de novembro de 2011 10:59, Marcelo ND <[email protected]>escreveu:
>
>
> Em 25 de novembro de 2011 00:11, Sergio Mira <[email protected]> escreveu:
>
>> Minha primeira pergunta seria: por que não utilizar o wicd?
>>
>
> Um porquê não usar wicd não existe. Mas.
> Quem quer aprender e ver como "as coisas" funcionam "vai na mão".
>
> --
> GUS-BR - Grupo de Usuários de Slackware Brasil
> http://www.slackwarebrasil.org/
> http://groups.google.com/group/slack-users-br
>
> Antes de perguntar:
> http://www.istf.com.br/perguntas/
>
> Para sair da lista envie um e-mail para:
> [email protected]
>
--
* Cezar Rangel*
*[email protected]*
--
GUS-BR - Grupo de Usuários de Slackware Brasil
http://www.slackwarebrasil.org/
http://groups.google.com/group/slack-users-br
Antes de perguntar:
http://www.istf.com.br/perguntas/
Para sair da lista envie um e-mail para:
[email protected]
