O ponto de acesso sem fio móvel continua caindo

0

Eu tenho um ponto de acesso sem fio no meu telefone que acabei de configurar. O telefone é um Samsung Galaxy S2 fornecido pela ATT Wireless. Quando o configurei pela primeira vez, o Network Manager reconheceu o ponto de acesso e consegui me conectar.

Então, um ou dois dias depois, a conexão só permanecerá por cerca de um minuto. Consultei os links a seguir e nenhuma das sugestões teve impacto na minha situação:

link (não há informação relevante nesta resposta.)

Não é possível conectar VPN pptp em 13.10 (Isso é uma VPN)

Problema de conexão Wi-Fi (configurar o sudo iw wlan0 set power_save off não teve efeito)

Eu posso manter uma conexão com outros roteadores wifi, trabalho em casa etc. Apenas não o telefone.

Estou executando o seguinte sistema:


Linux 3.11.0-19-generic #33-Ubuntu SMP 
Description:    Ubuntu 13.10
Release:    13.10
Codename:   saucy

O driver (conforme fornecido pelo lspci) é:

Network controller: Intel Corporation Wireless 3160 (rev 83)

Quando perco a conexão, o dispositivo não é mais visto pela verificação do SSID. Eu tenho que reiniciar wpa_supplicant para vê-lo novamente e se conectar a ele.

Tailing / var / log / syslog oferece alguns trechos do que está acontecendo:

A conexão inicial bem-sucedida:

Apr 21 22:57:59 eggsmachine NetworkManager[930]:  (wlan0): bringing up device.
Apr 21 22:57:59 eggsmachine kernel: [18251.911641] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Apr 21 22:57:59 eggsmachine kernel: [18251.911885] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Apr 21 22:57:59 eggsmachine kernel: [18251.924021] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 21 22:57:59 eggsmachine NetworkManager[930]:  (wlan0) supports 5 scan SSIDs
Apr 21 22:57:59 eggsmachine NetworkManager[930]:  Trying to remove a non-existant call id.
Apr 21 22:57:59 eggsmachine NetworkManager[930]:  (wlan0): supplicant interface state: starting -> ready
Apr 21 22:57:59 eggsmachine NetworkManager[930]:  (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Apr 21 22:57:59 eggsmachine NetworkManager[930]:  (wlan0): supplicant interface state: ready -> inactive
Apr 21 22:57:59 eggsmachine NetworkManager[930]:  (wlan0) supports 5 scan SSIDs
Apr 21 22:58:14 eggsmachine NetworkManager[930]:  Activation (wlan0) starting connection 'eggmatters'
Apr 21 22:58:14 eggsmachine NetworkManager[930]:  (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 21 22:58:14 eggsmachine NetworkManager[930]:  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 21 22:58:14 eggsmachine NetworkManager[930]:  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 21 22:58:14 eggsmachine whoopsie[1321]: offline
Apr 21 22:58:14 eggsmachine NetworkManager[930]:  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 21 22:58:14 eggsmachine NetworkManager[930]:  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 21 22:58:14 eggsmachine NetworkManager[930]:  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 21 22:58:14 eggsmachine NetworkManager[930]:  (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 21 22:58:14 eggsmachine NetworkManager[930]:  Activation (wlan0/wireless): connection 'eggmatters' has security, and secrets exist.  No new secrets needed.
Apr 21 22:58:14 eggsmachine NetworkManager[930]:  Config: added 'ssid' value 'eggmatters'
Apr 21 22:58:14 eggsmachine NetworkManager[930]:  Config: added 'scan_ssid' value '1'
Apr 21 22:58:14 eggsmachine NetworkManager[930]:  Config: added 'key_mgmt' value 'WPA-PSK'
Apr 21 22:58:14 eggsmachine NetworkManager[930]:  Config: added 'psk' value ''
Apr 21 22:58:14 eggsmachine NetworkManager[930]:  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 21 22:58:14 eggsmachine NetworkManager[930]:  Config: set interface ap_scan to 1
Apr 21 22:58:14 eggsmachine NetworkManager[930]:  (wlan0): supplicant interface state: inactive -> scanning
Apr 21 22:58:18 eggsmachine wpa_supplicant[5029]: wlan0: SME: Trying to authenticate with 20:64:32:3a:91:85 (SSID='eggmatters' freq=2462 MHz)
Apr 21 22:58:18 eggsmachine wpa_supplicant[5029]: wlan0: Trying to associate with 20:64:32:3a:91:85 (SSID='eggmatters' freq=2462 MHz)
Apr 21 22:58:18 eggsmachine kernel: [18271.392061] wlan0: authenticate with 20:64:32:3a:91:85
Apr 21 22:58:18 eggsmachine kernel: [18271.392784] wlan0: send auth to 20:64:32:3a:91:85 (try 1/3)
Apr 21 22:58:18 eggsmachine kernel: [18271.394588] wlan0: authenticated
Apr 21 22:58:18 eggsmachine kernel: [18271.395117] wlan0: associate with 20:64:32:3a:91:85 (try 1/3)
Apr 21 22:58:18 eggsmachine NetworkManager[930]:  (wlan0): supplicant interface state: scanning -> associating
Apr 21 22:58:18 eggsmachine kernel: [18271.398930] wlan0: RX AssocResp from 20:64:32:3a:91:85 (capab=0x411 status=0 aid=1)
Apr 21 22:58:18 eggsmachine wpa_supplicant[5029]: wlan0: Associated with 20:64:32:3a:91:85
Apr 21 22:58:18 eggsmachine kernel: [18271.399687] wlan0: associated
Apr 21 22:58:18 eggsmachine kernel: [18271.399824] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Apr 21 22:58:18 eggsmachine NetworkManager[930]:  (wlan0): supplicant interface state: associating -> associated
Apr 21 22:58:18 eggsmachine NetworkManager[930]:  (wlan0): supplicant interface state: associated -> 4-way handshake
Apr 21 22:58:18 eggsmachine wpa_supplicant[5029]: wlan0: WPA: Key negotiation completed with 20:64:32:3a:91:85 [PTK=CCMP GTK=CCMP]
Apr 21 22:58:18 eggsmachine wpa_supplicant[5029]: wlan0: CTRL-EVENT-CONNECTED - Connection to 20:64:32:3a:91:85 completed (auth) [id=0 id_str=]
Apr 21 22:58:18 eggsmachine NetworkManager[930]:  (wlan0): supplicant interface state: 4-way handshake -> completed
Apr 21 22:58:18 eggsmachine NetworkManager[930]:  Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'eggmatters'.
Apr 21 22:58:18 eggsmachine NetworkManager[930]:  Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 21 22:58:18 eggsmachine NetworkManager[930]:  Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Apr 21 22:58:18 eggsmachine NetworkManager[930]:  (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Apr 21 22:58:18 eggsmachine NetworkManager[930]:  Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Apr 21 22:58:18 eggsmachine NetworkManager[930]:  dhclient started with pid 5282
Apr 21 22:58:18 eggsmachine NetworkManager[930]:  Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Apr 21 22:58:18 eggsmachine dhclient: Internet Systems Consortium DHCP Client 4.2.4
Apr 21 22:58:18 eggsmachine dhclient: Copyright 2004-2012 Internet Systems Consortium.
Apr 21 22:58:18 eggsmachine dhclient: All rights reserved.
Apr 21 22:58:18 eggsmachine dhclient: For info, please visit https://www.isc.org/software/dhcp/
Apr 21 22:58:18 eggsmachine dhclient: 
Apr 21 22:58:18 eggsmachine NetworkManager[930]:  (wlan0): DHCPv4 state changed nbi -> preinit
Apr 21 22:58:18 eggsmachine dhclient: Listening on LPF/wlan0/a0:88:69:32:fd:d9
Apr 21 22:58:18 eggsmachine dhclient: Sending on   LPF/wlan0/a0:88:69:32:fd:d9
Apr 21 22:58:18 eggsmachine dhclient: Sending on   Socket/fallback
Apr 21 22:58:18 eggsmachine dhclient: DHCPREQUEST of 192.168.43.84 on wlan0 to 255.255.255.255 port 67 (xid=0x78346b10)
Apr 21 22:58:18 eggsmachine dhclient: DHCPACK of 192.168.43.84 from 192.168.43.1
Apr 21 22:58:18 eggsmachine dhclient: bound to 192.168.43.84 -- renewal in 1469 seconds.
Apr 21 22:58:18 eggsmachine NetworkManager[930]:  (wlan0): DHCPv4 state changed preinit -> reboot
Apr 21 22:58:18 eggsmachine NetworkManager[930]:    address 192.168.43.84
Apr 21 22:58:18 eggsmachine NetworkManager[930]:    prefix 24 (255.255.255.0)
Apr 21 22:58:18 eggsmachine NetworkManager[930]:    gateway 192.168.43.1
Apr 21 22:58:18 eggsmachine NetworkManager[930]:    hostname 'eggsmachine'
Apr 21 22:58:18 eggsmachine NetworkManager[930]:    nameserver '192.168.43.1'
Apr 21 22:58:18 eggsmachine NetworkManager[930]:  Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Apr 21 22:58:18 eggsmachine NetworkManager[930]:  Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Apr 21 22:58:18 eggsmachine avahi-daemon[909]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.43.84.
Apr 21 22:58:18 eggsmachine avahi-daemon[909]: New relevant interface wlan0.IPv4 for mDNS.
Apr 21 22:58:18 eggsmachine avahi-daemon[909]: Registering new address record for 192.168.43.84 on wlan0.IPv4.
Apr 21 22:58:19 eggsmachine NetworkManager[930]:  (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Apr 21 22:58:19 eggsmachine NetworkManager[930]:  Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Apr 21 22:58:19 eggsmachine NetworkManager[930]:  (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 21 22:58:20 eggsmachine NetworkManager[930]:  Policy set 'eggmatters' (wlan0) as default for IPv4 routing and DNS.
Apr 21 22:58:20 eggsmachine NetworkManager[930]:  Writing DNS information to /sbin/resolvconf
Apr 21 22:58:20 eggsmachine dnsmasq[2018]: setting upstream servers from DBus
Apr 21 22:58:20 eggsmachine dnsmasq[2018]: using nameserver 192.168.43.1#53
Apr 21 22:58:20 eggsmachine avahi-daemon[909]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::a288:69ff:fe32:fdd9.
Apr 21 22:58:20 eggsmachine avahi-daemon[909]: New relevant interface wlan0.IPv6 for mDNS.
Apr 21 22:58:20 eggsmachine avahi-daemon[909]: Registering new address record for fe80::a288:69ff:fe32:fdd9 on wlan0.*.
Apr 21 22:58:20 eggsmachine NetworkManager[930]:  Activation (wlan0) successful, device activated.
Apr 21 22:58:20 eggsmachine dbus[823]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Apr 21 22:58:20 eggsmachine whoopsie[1321]: offline
Apr 21 22:58:20 eggsmachine dbus[823]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 21 22:58:20 eggsmachine whoopsie[1321]: online
Apr 21 22:58:21 eggsmachine whoopsie[1321]: online
Apr 21 22:58:27 eggsmachine ntpdate[5361]: adjust time server 91.189.94.4 offset -0.033826 sec

Então, neste caso, perdemos a conexão:


Apr 21 22:58:59 eggsmachine wpa_supplicant[5029]: wlan0: CTRL-EVENT-DISCONNECTED bssid=20:64:32:3a:91:85 reason=4
Apr 21 22:58:59 eggsmachine kernel: [18311.899261] cfg80211: Calling CRDA to update world regulatory domain
Apr 21 22:58:59 eggsmachine kernel: [18311.901056] cfg80211: World regulatory domain updated:
Apr 21 22:58:59 eggsmachine kernel: [18311.901058] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Apr 21 22:58:59 eggsmachine kernel: [18311.901059] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 21 22:58:59 eggsmachine kernel: [18311.901060] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 21 22:58:59 eggsmachine kernel: [18311.901061] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Apr 21 22:58:59 eggsmachine kernel: [18311.901062] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 21 22:58:59 eggsmachine kernel: [18311.901063] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 21 22:58:59 eggsmachine NetworkManager[930]:  (wlan0): supplicant interface state: completed -> disconnected
Apr 21 22:58:59 eggsmachine NetworkManager[930]:  (wlan0): supplicant interface state: disconnected -> scanning
Apr 21 22:59:11 eggsmachine wpa_supplicant[5029]: wlan0: SME: Trying to authenticate with 20:64:32:3a:91:85 (SSID='eggmatters' freq=2462 MHz)
Apr 21 22:59:11 eggsmachine wpa_supplicant[5029]: wlan0: Trying to associate with 20:64:32:3a:91:85 (SSID='eggmatters' freq=2462 MHz)
Apr 21 22:59:11 eggsmachine kernel: [18324.400907] wlan0: authenticate with 20:64:32:3a:91:85
Apr 21 22:59:11 eggsmachine kernel: [18324.401919] wlan0: send auth to 20:64:32:3a:91:85 (try 1/3)
Apr 21 22:59:11 eggsmachine kernel: [18324.403932] wlan0: authenticated
Apr 21 22:59:11 eggsmachine NetworkManager[930]:  (wlan0): supplicant interface state: scanning -> associating
Apr 21 22:59:11 eggsmachine kernel: [18324.408370] wlan0: associate with 20:64:32:3a:91:85 (try 1/3)
Apr 21 22:59:11 eggsmachine kernel: [18324.411832] wlan0: RX AssocResp from 20:64:32:3a:91:85 (capab=0x411 status=0 aid=1)
Apr 21 22:59:11 eggsmachine wpa_supplicant[5029]: wlan0: Associated with 20:64:32:3a:91:85
Apr 21 22:59:11 eggsmachine kernel: [18324.412786] wlan0: associated
Apr 21 22:59:11 eggsmachine NetworkManager[930]:  (wlan0): supplicant interface state: associating -> associated
Apr 21 22:59:14 eggsmachine NetworkManager[930]:  (wlan0): link timed out.
Apr 21 22:59:14 eggsmachine NetworkManager[930]:  (wlan0): device state change: activated -> failed (reason 'supplicant-timeout') [100 120 11]
Apr 21 22:59:14 eggsmachine NetworkManager[930]:  Activation (wlan0) failed for connection 'eggmatters'
Apr 21 22:59:14 eggsmachine whoopsie[1321]: offline
Apr 21 22:59:14 eggsmachine dbus[823]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Apr 21 22:59:14 eggsmachine NetworkManager[930]:  (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Apr 21 22:59:14 eggsmachine NetworkManager[930]:  (wlan0): deactivating device (reason 'none') [0]
Apr 21 22:59:14 eggsmachine dbus[823]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 21 22:59:14 eggsmachine NetworkManager[930]:  (wlan0): canceled DHCP transaction, DHCP client pid 5282
Apr 21 22:59:14 eggsmachine avahi-daemon[909]: Withdrawing address record for fe80::a288:69ff:fe32:fdd9 on wlan0.
Apr 21 22:59:14 eggsmachine avahi-daemon[909]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::a288:69ff:fe32:fdd9.
Apr 21 22:59:14 eggsmachine avahi-daemon[909]: Interface wlan0.IPv6 no longer relevant for mDNS.
Apr 21 22:59:14 eggsmachine avahi-daemon[909]: Withdrawing address record for 192.168.43.84 on wlan0.
Apr 21 22:59:14 eggsmachine avahi-daemon[909]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.43.84.
Apr 21 22:59:14 eggsmachine avahi-daemon[909]: Interface wlan0.IPv4 no longer relevant for mDNS.
Apr 21 22:59:14 eggsmachine kernel: [18327.457293] wlan0: deauthenticating from 20:64:32:3a:91:85 by local choice (reason=3)
Apr 21 22:59:14 eggsmachine NetworkManager[930]:  DNS: plugin dnsmasq update failed
Apr 21 22:59:14 eggsmachine NetworkManager[930]:  Removing DNS information from /sbin/resolvconf
Apr 21 22:59:14 eggsmachine dnsmasq[2018]: setting upstream servers from DBus
Apr 21 22:59:14 eggsmachine wpa_supplicant[5029]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
Apr 21 22:59:14 eggsmachine kernel: [18327.459960] cfg80211: Calling CRDA to update world regulatory domain
Apr 21 22:59:14 eggsmachine kernel: [18327.464927] cfg80211: World regulatory domain updated:
Apr 21 22:59:14 eggsmachine kernel: [18327.464934] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Apr 21 22:59:14 eggsmachine kernel: [18327.464939] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 21 22:59:14 eggsmachine kernel: [18327.464944] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 21 22:59:14 eggsmachine kernel: [18327.464947] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Apr 21 22:59:14 eggsmachine kernel: [18327.464950] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 21 22:59:14 eggsmachine kernel: [18327.464953] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 21 22:59:14 eggsmachine NetworkManager[930]:  (wlan0): supplicant interface state: associated -> disconnected

Para "bssid CTRL-EVENTS-DISCONNECTED = 20: 64: 32: 3a: 91: 85 reason = 4", não consigo encontrar um recurso que explique que razão = 4 significa.

Vimos que na tentativa subsequente, o link expira com um bssid = 00: 00: 00: 00: 00: 00 reason = 3

com o valor CTRL-EVENT-DISCONNECTED

O que faz sentido, pois o wpa_supplicant não consegue mais encontrar o dispositivo.

Posso repetir este processo executando:


ps -ef | grep wpa
kill -9 (the pid of wpa_supplicant)

Adicionar log detalhado ao wpa_supplicant mostra o seguinte:


Apr 23 09:07:31 eggsmachine wpa_supplicant[4790]: WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
Apr 23 09:07:40 eggsmachine wpa_supplicant[4790]: EAPOL: External notification - portEnabled=0
Apr 23 09:07:40 eggsmachine wpa_supplicant[4790]: EAPOL: SUPP_PAE entering state DISCONNECTED
Apr 23 09:07:40 eggsmachine wpa_supplicant[4790]: EAPOL: Supplicant port status: Unauthorized
Apr 23 09:07:40 eggsmachine wpa_supplicant[4790]: EAPOL: SUPP_BE entering state INITIALIZE
Apr 23 09:07:40 eggsmachine wpa_supplicant[4790]: EAPOL: Supplicant port status: Unauthorized
Apr 23 09:07:40 eggsmachine wpa_supplicant[4790]: EAPOL: External notification - portValid=0
Apr 23 09:07:40 eggsmachine wpa_supplicant[4790]: EAPOL: Supplicant port status: Unauthorized
Apr 23 09:07:40 eggsmachine wpa_supplicant[4790]: EAPOL: External notification - EAP success=0
Apr 23 09:07:40 eggsmachine wpa_supplicant[4790]: EAPOL: Supplicant port status: Unauthorized
Apr 23 09:07:40 eggsmachine wpa_supplicant[4790]: EAPOL: External notification - portEnabled=0
Apr 23 09:07:40 eggsmachine wpa_supplicant[4790]: EAPOL: Supplicant port status: Unauthorized
Apr 23 09:07:40 eggsmachine wpa_supplicant[4790]: EAPOL: External notification - portValid=0
Apr 23 09:07:40 eggsmachine wpa_supplicant[4790]: EAPOL: Supplicant port status: Unauthorized
Apr 23 09:07:40 eggsmachine wpa_supplicant[4790]: EAPOL: External notification - EAP success=0
Apr 23 09:07:40 eggsmachine wpa_supplicant[4790]: EAPOL: Supplicant port status: Unauthorized
Apr 23 09:07:40 eggsmachine wpa_supplicant[4790]: EAPOL: Supplicant port status: Unauthorized

Qualquer que seja o EAPOL, ele não está mais sendo autenticado.

Então, como uma rápida recapitulação:

  • Não é possível conectar-se à mobilidade sem fio (Samsung Galaxy S2 via ATT) por mais de 1 a 5 minutos
  • Pode se conectar a outros pontos de acesso sem fio sem problemas.
  • Os registros indicam que o dispositivo não pode ser autenticado e atinge o tempo limite.

Outras postagens do fórum indicam um problema no kernel ou em um driver de dispositivo. Minha situação é confusa, pois posso me conectar a pontos de acesso Wi-Fi.

Ah, e não tenho certeza se é o telefone ou não. Ainda não testei em outros dispositivos. Meus instintos estão me dizendo que não é o telefone.

Obrigado por dedicar um tempo para me ajudar com isso. Apenas migrei do Debian Wheezy para o Ubuntu, então. . . isso é inútil, mas esse é o meu primeiro post no Ask Ask.

ATUALIZAÇÃO: Eu removi o MAC ADDRESS desta máquina do telefone e simplesmente simplesmente autentico com o WPA2. Isso, obviamente, não fez nada.

Os registros parecem indicar que o dispositivo não honra mais a autenticidade da conexão. Na tentativa de isolar o wpa_supplicant, eu chamei o wpa_supplicant do terminal, passando o driver, e o ssid, mas isso muck com o NetworkManager que está rodando sua própria versão do wpa_supplicant e, aparentemente, eles não tocam bem.

O outro culpado pode ser dnsmasq, já que parece que está consultando meu telefone para uma entrada dns e talvez esses dois não estejam interagindo muito bem "Eu gostaria de uma entrada dns. Claro. Eu gostaria de uma entrada dns novamente. Espere um segundo, eu acabei de te dar dois minutos atrás. "

Colisão diária: você não adora quando problemas bem formados fornecem histórico e registros, bem como históricos e log, passam despercebidos? Portanto, a conexão é estável e contínua quando conectada. Algo está com o sinal então. Talvez seja um mau motorista? Não tenho certeza, já que essa questão é bastante inadequada.

    
por eggmatters 23.04.2014 / 19:59

1 resposta

0

Aparentemente, há um bug no Kernel para os drivers de dispositivos sem fio da realtek. Eu estou tendo o mesmo problema no Ubuntu 14.04 com a minha conexão caindo. Estou me preparando para reverter para uma versão mais antiga do kernel para ver se isso resolve meus problemas. Espero que você encontre ajuda com seu problema. Wildman e eu estamos solucionando meu problema no tópico Wifi Drops e se reconecta com o UBUNTU 14.04 (Realtek RTL8188) , nós documentamos nossos passos ao longo do caminho, talvez você possa experimentar um pouco do que nós tentamos e encontrar uma solução se você emitir é similar o suficiente para o meu.

    
por Jeff Smith 22.07.2014 / 15:27