Pessoal......
Esse problema ta dificil de resolver.
@José
O comando "journalctl -bu wpa_supplicant.service" não rolou na minha
máquina.
[root@localhost broadcom-wl-4.178.10.4]# journalctl -bu
wpa_supplicant.service
Failed to parse boot descriptor 'u'
Consegui com o seguinte comando:
[root@localhost broadcom-wl-4.178.10.4]# journalctl -fu
wpa_supplicant.service
Segue resultado....
Dec 21 15:52:45 localhost.localdomain wpa_supplicant[7145]: wlan0: SME:
Trying to authenticate with <mac_addr> (SSID='ssid_name' freq=2462 MHz)
Dec 21 15:52:45 localhost.localdomain wpa_supplicant[7145]: wlan0: Trying
to associate with <mac_addr> (SSID='ssid_name' freq=2462 MHz)
Dec 21 15:52:45 localhost.localdomain wpa_supplicant[7145]: wlan0:
Associated with <mac_addr>
Dec 21 15:52:45 localhost.localdomain wpa_supplicant[7145]: wlan0:
CTRL-EVENT-EAP-STARTED EAP authentication started
Dec 21 15:52:45 localhost.localdomain wpa_supplicant[7145]: wlan0:
CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=BR
Dec 21 15:52:57 localhost.localdomain wpa_supplicant[7145]: wlan0:
CTRL-EVENT-DISCONNECTED bssid=<mac_addr> reason=23
Dec 21 15:52:57 localhost.localdomain wpa_supplicant[7145]: wlan0:
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="ssid_name" auth_failures=1
duration=10 reason=AUTH_FAILED
Dec 21 15:52:57 localhost.localdomain wpa_supplicant[7145]: wlan0:
CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Dec 21 15:52:57 localhost.localdomain wpa_supplicant[7145]: wlan0:
CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=BR
Dec 21 15:53:08 localhost.localdomain wpa_supplicant[7145]: wlan0:
CTRL-EVENT-SSID-REENABLED id=0 ssid="ssid_name"
Dec 21 15:53:08 localhost.localdomain wpa_supplicant[7145]: wlan0: SME:
Trying to authenticate with <mac_addr> (SSID='ssid_name' freq=2462 MHz)
Dec 21 15:53:08 localhost.localdomain wpa_supplicant[7145]: wlan0: Trying
to associate with <mac_addr> (SSID='ssid_name' freq=2462 MHz)
Dec 21 15:53:08 localhost.localdomain wpa_supplicant[7145]: wlan0:
Associated with <mac_addr>
Dec 21 15:53:08 localhost.localdomain wpa_supplicant[7145]: wlan0:
CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=BR
Dec 21 15:53:08 localhost.localdomain wpa_supplicant[7145]: wlan0:
CTRL-EVENT-EAP-STARTED EAP authentication started
Dec 21 15:53:10 localhost.localdomain wpa_supplicant[7145]: wlan0:
CTRL-EVENT-DISCONNECTED bssid=<mac_addr> reason=3 locally_generated=1
Dec 21 15:53:10 localhost.localdomain wpa_supplicant[7145]: wlan0:
CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Dec 21 15:53:10 localhost.localdomain wpa_supplicant[7145]: wlan0:
CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=BR
Atenciosamente,
*Guilherme Maioque Rocha*
Em 20 de dezembro de 2016 16:09, José Neto <josenetodino(a)gmail.com>
escreveu:
Entao tenta isso aqui:
journalctl -bu wpa_supplicant
Em 20 de dezembro de 2016 13:49, Guilherme Rocha
<guilhermerocha000(a)gmail.com> escreveu:
> ****
> CORREÇÃO
> ****
> Amigos o texto anterior tinha ficado meio estanho... Então só pra
> esclarecer.
>
> não existe esse aquivo de log para o wpa_supplicant na minha
> máquina. OK?!?
>
> Não estou discordando de vocês... rsss
>
> Só pra esclarecer mesmo..
>
> Abs...
>
>
>
> Atenciosamente,
> Guilherme Maioque Rocha
>
>
> Em 20 de dezembro de 2016 14:01, Guilherme Rocha
> <guilhermerocha000(a)gmail.com> escreveu:
>>
>> Amigos não existe esse aquivo de log para o wpa_supplicant
>>
>> Verifiquei que o serviço está ativo, segue status:
>>
>> [root@localhost broadcom-wl-4.178.10.4]# service wpa_supplicant status
>> wpa_supplicant.service - WPA supplicant
>> Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service;
>> disabled; vendor preset: disabled)
>> Active: active (running) since Tue 2016-12-20 13:56:10 BRST; 1min 33s
>> ago
>> Main PID: 7145 (wpa_supplicant)
>> Tasks: 1 (limit: 512)
>> CGroup: /system.slice/wpa_supplicant.service
>> └─7145 /usr/sbin/wpa_supplicant -c
>> /etc/wpa_supplicant/wpa_supplicant.conf -u -s
>>
>> Dec 20 13:57:24 localhost.localdomain wpa_supplicant[7145]: wlan0:
>> CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=BR
>> Dec 20 13:57:35 localhost.localdomain wpa_supplicant[7145]: wlan0:
>> CTRL-EVENT-SSID-REENABLED id=0 ssid="ssid_name"
>> Dec 20 13:57:35 localhost.localdomain wpa_supplicant[7145]: wlan0: SME:
>> Trying to authenticate with <mac_addr> (SSID='ssid_name' freq=2462
MHz)
>> Dec 20 13:57:35 localhost.localdomain wpa_supplicant[7145]: wlan0:
Trying
>> to associate with <mac_addr> (SSID='ssid_name' freq=2462 MHz)
>> Dec 20 13:57:35 localhost.localdomain wpa_supplicant[7145]: wlan0:
>> Associated with <mac_addr>
>> Dec 20 13:57:35 localhost.localdomain wpa_supplicant[7145]: wlan0:
>> CTRL-EVENT-EAP-STARTED EAP authentication started
>> Dec 20 13:57:35 localhost.localdomain wpa_supplicant[7145]: wlan0:
>> CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=BR
>> Dec 20 13:57:38 localhost.localdomain wpa_supplicant[7145]: wlan0:
>> CTRL-EVENT-DISCONNECTED bssid=<mac_addr> reason=3 locally_generated=1
>> Dec 20 13:57:38 localhost.localdomain wpa_supplicant[7145]: wlan0:
>> CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
>> Dec 20 13:57:38 localhost.localdomain wpa_supplicant[7145]: wlan0:
>> CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=BR
>> ~
>> ~
>>
>>
>> Atenciosamente,
>> Guilherme Maioque Rocha
>>
>>
>> Em 20 de dezembro de 2016 10:24, José Neto <josenetodino(a)gmail.com>
>> escreveu:
>>>
>>> Fica de olho nesse log tambem
>>>
>>> tail -f /var/log/wpa_supplicant.log
>>>
>>> Em 20 de dezembro de 2016 09:14, Guilherme Rocha
>>> <guilhermerocha000(a)gmail.com> escreveu:
>>> > Amigos bom dia
>>> >
>>> > Não pude seguir com a analise ontem, porém hoje consegui retomar a
>>> > questão.
>>> > Segue o que encontrei nos logs:
>>> >
>>> > Esse trecho entra em looping em conjunto com a solicitação de senha
>>> > -------------------------------
>>> > Dec 20 08:52:57 localhost.localdomain kernel: wlan0: authenticate
with
>>> > <mac_addr>
>>> > Dec 20 08:52:57 localhost.localdomain kernel: wlan0: send auth to
>>> > <mac_addr>
>>> > (try 1/3)
>>> > Dec 20 08:52:57 localhost.localdomain kernel: wlan0: authenticated
>>> > Dec 20 08:52:57 localhost.localdomain kernel: wlan0: associate with
>>> > <mac_addr> (try 1/3)
>>> > Dec 20 08:52:57 localhost.localdomain kernel: wlan0: RX AssocResp
from
>>> > <mac_addr> (capab=0x431 status=0 aid=1)
>>> > Dec 20 08:52:57 localhost.localdomain kernel: wlan0: associated
>>> > Dec 20 08:52:57 localhost.localdomain kernel: wlan0: Limiting TX
power
>>> > to 23
>>> > dBm as advertised by <mac_addr>
>>> > Dec 20 08:53:09 localhost.localdomain kernel: wlan0: deauthenticated
>>> > from
>>> > <mac_addr> (Reason: 23=IEEE8021X_FAILED)
>>> > -------------------------------
>>> >
>>> > Sobre essa questão do 23dBm, encontrei o seguinte detalhe. Porém não
>>> > consegui alterar o valor.
>>> >
>>> > [root@localhost broadcom-wl-4.178.10.4]# iwconfig wlan0
>>> > wlan0 IEEE 802.11bg ESSID:off/any
>>> > Mode:Managed Access Point: Not-Associated Tx-Power=20
dBm
>>> > Retry short limit:7 RTS thr:off Fragment thr:off
>>> > Encryption key:off
>>> > Power Management:off
>>> >
>>> >
>>> >
>>> >
>>> > Atenciosamente,
>>> > Guilherme Maioque Rocha
>>> >
>>> >
>>> > Em 18 de dezembro de 2016 20:25, José Neto
<josenetodino(a)gmail.com>
>>> > escreveu:
>>> >>
>>> >> Tenta observar o que os logs dizem
>>> >>
>>> >> journalctl -bu NetworkManager
>>> >> journalctl -kf
>>> >> journalctl -f
>>> >>
>>> >> enquanto tenta conectar na rede.
>>> >>
>>> >>
>>> >> Em 18 de dezembro de 2016 17:50, Guilherme Rocha
>>> >> <guilhermerocha000(a)gmail.com> escreveu:
>>> >> > Amigos boa tarde.
>>> >> >
>>> >> > Estou com uma grande dificuldade para me conectar na rede
wireless
>>> >> > da
>>> >> > empresa. Já realizei o teste com 3 máquinas diferentes porém
o
>>> >> > comportamento
>>> >> > é o mesmo.
>>> >> >
>>> >> > Em todos os casos eu consigo localizar o SSID da rede; Tento
me
>>> >> > conectar,
>>> >> > configurando todos as opções de segurança com base nas que
são
>>> >> > utilizadas
>>> >> > nos sistema Windows (no qual a mesma máquina funciona sem
problemas)
>>> >> > porém o
>>> >> > fedora entra em looping pedindo repetidamente minha senha e a
>>> >> > conexão
>>> >> > com a
>>> >> > rede nunca é concluída.
>>> >> >
>>> >> > Os requisitos de segurança da rede são os seguintes:
>>> >> >
>>> >> > Security: WPA & WPA2 Enterprise
>>> >> > Authentication: Protected EAP (PEAP)
>>> >> > CA certificate: Já tente com e sem o certificado da CA da
empresa
>>> >> > PEAP version: Automatic
>>> >> > Inner authentication: MSCHAPv2
>>> >> > Username: domain\my_user
>>> >> > Password: my_pass
>>> >> > Firewall Zone: Default
>>> >> >
>>> >> > Tentei realizar as configurações selecionando a rede
encontrada
>>> >> > automaticamente pelo sistema, mas não funcionou;
>>> >> > Tentei criar uma rede manualmente (Connect to a Hidden
Network),
mas
>>> >> > também
>>> >> > não funcionou;
>>> >> > Em redes com outro tipo de segurança, onde é necessário
somente
>>> >> > usuário
>>> >> > e
>>> >> > senha (sem integração com RADIUS), consigo me conectar
normalmente.
>>> >> > O
>>> >> > problema só acontece em WPA2 Enterprise.
>>> >> >
>>> >> > Já encontrei diversas discussões sobre esse assunto em fóruns
com
>>> >> > pessoas
>>> >> > tendo esse tipo de problema para se autenticar na rede de
>>> >> > universidades,
>>> >> > porém todas para o sistema ubuntu e não consegui aplicar tais
>>> >> > sugestões
>>> >> > para
>>> >> > o fedora.
>>> >> >
>>> >> > Estou aberto a sugestões aqui.
>>> >> >
>>> >> > Grande abraço a todos.
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> > Atenciosamente,
>>> >> > Guilherme Maioque Rocha
>>> >> >
>>> >> >
>>> >> > _______________________________________________
>>> >> > br-users mailing list -- br-users(a)lists.fedoraproject.org
>>> >> > To unsubscribe send an email to
>>> >> > br-users-leave(a)lists.fedoraproject.org
>>> >> >
>>> >> _______________________________________________
>>> >> br-users mailing list -- br-users(a)lists.fedoraproject.org
>>> >> To unsubscribe send an email to br-users-leave@lists.
fedoraproject.org
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > br-users mailing list -- br-users(a)lists.fedoraproject.org
>>> > To unsubscribe send an email to br-users-leave@lists.
fedoraproject.org
>>> >
>>> _______________________________________________
>>> br-users mailing list -- br-users(a)lists.fedoraproject.org
>>> To unsubscribe send an email to br-users-leave(a)lists.fedoraproject.org
>>
>>
>
>
> _______________________________________________
> br-users mailing list -- br-users(a)lists.fedoraproject.org
> To unsubscribe send an email to br-users-leave(a)lists.fedoraproject.org
>
_______________________________________________
br-users mailing list -- br-users(a)lists.fedoraproject.org
To unsubscribe send an email to br-users-leave(a)lists.fedoraproject.org