From: "Андрей Зайцев" <andzaytsev@mail.ru> To: hardware@lists.altlinux.org Subject: [Hardware] Проблема с wifi - atheros ar 9285 Date: Sat, 12 Jun 2010 22:03:36 +0400 Message-ID: <E1ONV3Q-0002yU-00.andzaytsev-mail-ru@f275.mail.ru> (raw) На ноутбуке стоит ALT Linux 5.1 Школьный Мастер. На нем установлена карта wifi atheros ar 9285. После установки ничего не менял. Подключился к wifi через KNetworkManager. Через некоторое время невозможно соединиться ни с одним сервером в wifi и в интернете, но показывает, что есть соединение с wifi. Драйвер - ath9k. Шифрование в сети wifi - WPA2-AES. Роутер wifi - ASUS DSL-N13. Как решить проблему? Логи (подключался и отключался от wifi несколько раз, могут быть повторы): dmesg [ 4134.122817] wlan0: direct probe to AP 00:22:15:7b:25:4d try 1 [ 4134.126388] wlan0 direct probe responded [ 4134.126392] wlan0: authenticate with AP 00:22:15:7b:25:4d [ 4134.128351] wlan0: authenticated [ 4134.128357] wlan0: associate with AP 00:22:15:7b:25:4d [ 4134.142678] wlan0: RX ReassocResp from 00:22:15:7b:25:4d (capab=0xc11 status=0 aid=1) [ 4134.142683] wlan0: associated [ 4140.374614] wlan0: disassociated (Reason: 15) [ 4141.369694] wlan0: associate with AP 00:22:15:7b:25:4d [ 4141.569319] wlan0: associate with AP 00:22:15:7b:25:4d [ 4141.768947] wlan0: associate with AP 00:22:15:7b:25:4d [ 4141.968077] wlan0: association with AP 00:22:15:7b:25:4d timed out [ 4143.196645] wlan0: authenticate with AP 00:22:15:7b:25:4d [ 4143.206182] wlan0: authenticate with AP 00:22:15:7b:25:4d [ 4143.208087] wlan0: authenticated [ 4143.208090] wlan0: associate with AP 00:22:15:7b:25:4d [ 4143.222424] wlan0: RX ReassocResp from 00:22:15:7b:25:4d (capab=0xc11 status=0 aid=1) [ 4143.222427] wlan0: associated ifconfig # ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1745 errors:0 dropped:0 overruns:0 frame:0 TX packets:1745 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:169452 (165.4 KiB) TX bytes:169452 (165.4 KiB) vboxnet0 Link encap:Ethernet HWaddr 0A:00:27:00:00:00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) wlan0 Link encap:Ethernet HWaddr C4:17:FE:60:CE:C4 inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8281 errors:0 dropped:0 overruns:0 frame:0 TX packets:4833 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:7917735 (7.5 MiB) TX bytes:581429 (567.8 KiB) wmaster0 Link encap:UNSPEC HWaddr C4-17-FE-60-CE-C4-98-28-00-00-00-00-00-00-00-00 UP RUNNING MTU:0 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) iwconfig (Encryption key сам поменял на ***) # iwconfig lo no wireless extensions. wmaster0 no wireless extensions. wlan0 IEEE 802.11bgn ESSID:"cat@home" Mode:Managed Frequency:2.412 GHz Access Point: 00:22:15:7B:25:4D Bit Rate=0 kb/s Tx-Power=20 dBm Retry min limit:7 RTS thr:off Fragment thr:off Encryption key:*** [2] Security mode:open Power Management:off Link Quality=45/70 Signal level=-65 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 pan0 no wireless extensions. vboxnet0 no wireless extensions. /var/log/messages Jun 12 17:39:49 comp-Core-i5 NetworkManager: <info> (wlan0): device state change: 8 -> 3 (reason 0) Jun 12 17:39:49 comp-Core-i5 NetworkManager: <info> (wlan0): deactivating device (reason: 0). Jun 12 17:39:49 comp-Core-i5 NetworkManager: <info> (wlan0): removing resolv.conf from /sbin/resolvconf Jun 12 17:39:50 comp-Core-i5 named[10452]: loading configuration from '/etc/named.conf' Jun 12 17:39:50 comp-Core-i5 named[10452]: using default UDP/IPv4 port range: [1024, 65535] Jun 12 17:39:50 comp-Core-i5 bind: sending signal 1 to named succeeded Jun 12 17:39:50 comp-Core-i5 named[10452]: using default UDP/IPv6 port range: [1024, 65535] Jun 12 17:39:50 comp-Core-i5 named[10452]: listening on IPv4 interface wlan0, 192.168.1.3#53 Jun 12 17:39:50 comp-Core-i5 named[10452]: could not listen on UDP socket: permission denied Jun 12 17:39:50 comp-Core-i5 named[10452]: creating IPv4 interface wlan0 failed; interface ignored Jun 12 17:39:50 comp-Core-i5 NetworkManager: <WARN> check_one_route(): (wlan0) error -34 returned from rtnl_route_del(): Sucess Jun 12 17:39:50 comp-Core-i5 avahi-daemon[12145]: Withdrawing address record for 192.168.1.3 on wlan0. Jun 12 17:39:50 comp-Core-i5 avahi-daemon[12145]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.3. Jun 12 17:39:50 comp-Core-i5 avahi-daemon[12145]: Interface wlan0.IPv4 no longer relevant for mDNS. Jun 12 17:39:50 comp-Core-i5 avahi-daemon[12145]: querier.c: querier_remove() called but no querier to remove. Jun 12 17:39:50 comp-Core-i5 last message repeated 39 times Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Activation (wlan0) starting connection 'cat@home' Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> (wlan0): device state change: 3 -> 4 (reason 0) Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> (wlan0): supplicant connection state: completed -> disconnected Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0) Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Activation (wlan0/wireless): access point 'cat@home' has security, but secrets are required. Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> (wlan0): device state change: 5 -> 6 (reason 0) Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jun 12 17:39:50 comp-Core-i5 NetworkManager: <WARN> update_one_setting(): Failed to update connection secrets: 1 802-1x Jun 12 17:39:50 comp-Core-i5 NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting 'ipv4'. Jun 12 17:39:50 comp-Core-i5 NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting '802-11-wireless'. Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> (wlan0): device state change: 6 -> 4 (reason 0) Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0) Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Activation (wlan0/wireless): connection 'cat@home' has security, and secrets exist. No new secrets needed. Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Config: added 'ssid' value 'cat@home' Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Config: added 'scan_ssid' value '1' Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK' Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Config: added 'psk' value '<omitted>' Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> Config: set interface ap_scan to 1 Jun 12 17:39:50 comp-Core-i5 NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning Jun 12 17:40:01 comp-Core-i5 NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating Jun 12 17:40:02 comp-Core-i5 NetworkManager: <info> (wlan0): supplicant connection state: associated -> 4-way handshake Jun 12 17:40:02 comp-Core-i5 NetworkManager: <info> (wlan0): supplicant connection state: 4-way handshake -> group handshake Jun 12 17:40:02 comp-Core-i5 NetworkManager: <info> (wlan0): supplicant connection state: group handshake -> completed Jun 12 17:40:02 comp-Core-i5 NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'cat@home'. Jun 12 17:40:02 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. Jun 12 17:40:02 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... Jun 12 17:40:02 comp-Core-i5 NetworkManager: <info> (wlan0): device state change: 5 -> 7 (reason 0) Jun 12 17:40:02 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled... Jun 12 17:40:02 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Jun 12 17:40:02 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started... Jun 12 17:40:02 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled... Jun 12 17:40:02 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete. Jun 12 17:40:02 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started... Jun 12 17:40:02 comp-Core-i5 avahi-daemon[12145]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.3. Jun 12 17:40:02 comp-Core-i5 avahi-daemon[12145]: New relevant interface wlan0.IPv4 for mDNS. Jun 12 17:40:02 comp-Core-i5 avahi-daemon[12145]: Registering new address record for 192.168.1.3 on wlan0.IPv4. Jun 12 17:40:03 comp-Core-i5 NetworkManager: <info> (wlan0): writing resolv.conf to /sbin/resolvconf Jun 12 17:40:04 comp-Core-i5 bind: sending signal 1 to named succeeded Jun 12 17:40:04 comp-Core-i5 named[10452]: loading configuration from '/etc/named.conf' Jun 12 17:40:04 comp-Core-i5 named[10452]: using default UDP/IPv4 port range: [1024, 65535] Jun 12 17:40:04 comp-Core-i5 named[10452]: using default UDP/IPv6 port range: [1024, 65535] Jun 12 17:40:04 comp-Core-i5 named[10452]: listening on IPv4 interface wlan0, 192.168.1.3#53 Jun 12 17:40:04 comp-Core-i5 named[10452]: could not listen on UDP socket: permission denied Jun 12 17:40:04 comp-Core-i5 named[10452]: creating IPv4 interface wlan0 failed; interface ignored Jun 12 17:40:04 comp-Core-i5 NetworkManager: <info> (wlan0): device state change: 7 -> 8 (reason 0) Jun 12 17:40:04 comp-Core-i5 NetworkManager: <info> (wlan0): writing resolv.conf to /sbin/resolvconf Jun 12 17:40:04 comp-Core-i5 NetworkManager: <info> Policy set 'cat@home' (wlan0) as default for routing and DNS. Jun 12 17:40:04 comp-Core-i5 NetworkManager: <info> Activation (wlan0) successful, device activated. Jun 12 17:40:04 comp-Core-i5 NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete. Jun 12 17:40:45 comp-Core-i5 NetworkManager: <info> (wlan0): supplicant connection state: completed -> disconnected Jun 12 17:40:45 comp-Core-i5 NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning Jun 12 17:40:46 comp-Core-i5 NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associated Jun 12 17:40:52 comp-Core-i5 NetworkManager: <info> (wlan0): supplicant connection state: associated -> disconnected Jun 12 17:40:52 comp-Core-i5 NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning Jun 12 17:40:54 comp-Core-i5 NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected Jun 12 17:40:55 comp-Core-i5 NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> associating Jun 12 17:40:55 comp-Core-i5 NetworkManager: <info> (wlan0): supplicant connection state: associating -> associated Jun 12 17:40:55 comp-Core-i5 NetworkManager: <info> (wlan0): supplicant connection state: associated -> 4-way handshake Jun 12 17:40:55 comp-Core-i5 NetworkManager: <info> (wlan0): supplicant connection state: 4-way handshake -> group handshake Jun 12 17:40:55 comp-Core-i5 NetworkManager: <info> (wlan0): supplicant connection state: group handshake -> completed route # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 * 255.255.255.0 U 2 0 0 wlan0 default 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0 В /var/log/messages есть несколько подозрительных предупреждений! В веб-интерфейсе роутера в ARP не видит ноутбук подключенный через wifi. Даже при подключении.
next reply other threads:[~2010-06-12 18:03 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-06-12 18:03 Андрей Зайцев [this message] 2010-06-13 10:30 ` Mikhail Efremov 2010-06-15 7:40 ` Michael Shigorin 2010-06-15 12:30 ` Андрей Зайцев
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=E1ONV3Q-0002yU-00.andzaytsev-mail-ru@f275.mail.ru \ --to=andzaytsev@mail.ru \ --cc=hardware@lists.altlinux.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
ALT Linux hardware support This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/hardware/0 hardware/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 hardware hardware/ http://lore.altlinux.org/hardware \ hardware@altlinux.ru hardware@lists.altlinux.org hardware@lists.altlinux.ru hardware@lists.altlinux.com hardware@altlinux.org public-inbox-index hardware Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.hardware AGPL code for this site: git clone https://public-inbox.org/public-inbox.git