* [Comm] wifi авторизация
@ 2010-09-28 6:41 Anatoly Rezvushkin
2010-09-28 10:14 ` Mikhail Efremov
0 siblings, 1 reply; 14+ messages in thread
From: Anatoly Rezvushkin @ 2010-09-28 6:41 UTC (permalink / raw)
To: community
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
Установил altlinux-5.0.0-i586-ru на ноут Toshiba Satellite P200-RT7 все
хорошо, только wifi
соединяется с n-го раза, где n произвольное и , как правило, большое.
Настраивал wifi с помощью KNetworkManadger, wifi -карту он определяет, как
Intel Corporationn PRO/Wireless 4965 AG or AGN [Kedron] Network Connection.
Wifi маршрутизатор D-link 824.
После установки системы обновлялся и ядро обновил с 2.6.30 до 2.6.32.
Файлы успешной и неуспешной попыток соединения прилагаю.
(С виндой все работает.)
Прошу прощения не проверил вложения.
отправлял через web mail.ru и майл их попер.
С уважением,
Резвушкин Анатолий
[-- Attachment #2: messages.txt --]
[-- Type: text/plain, Size: 9981 bytes --]
Sep 5 17:32:35 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> associating
Sep 5 17:32:35 VMESTONAME kernel: [ 665.197986] wlan0: authenticate with AP 00:19:5b:be:a3:c1
Sep 5 17:32:35 VMESTONAME kernel: [ 665.198017] wlan0: authenticated
Sep 5 17:32:35 VMESTONAME kernel: [ 665.198021] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep 5 17:32:35 VMESTONAME kernel: [ 665.206203] wlan0: authenticate with AP 00:19:5b:be:a3:c1
Sep 5 17:32:35 VMESTONAME kernel: [ 665.206220] wlan0: authenticated
Sep 5 17:32:35 VMESTONAME kernel: [ 665.206224] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep 5 17:32:35 VMESTONAME kernel: [ 665.206248] wlan0: RX ReassocResp from 00:19:5b:be:a3:c1 (capab=0x431 status=0 aid=1)
Sep 5 17:32:35 VMESTONAME kernel: [ 665.206253] wlan0: associated
Sep 5 17:32:35 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: associating -> 4-way handshake
Sep 5 17:32:35 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: 4-way handshake -> associated
Sep 5 17:32:42 VMESTONAME kernel: [ 672.345236] [drm] Resetting GPU
Sep 5 17:32:45 VMESTONAME kernel: [ 675.226582] wlan0: disassociating by local choice (reason=3)
Sep 5 17:32:45 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: associated -> disconnected
Sep 5 17:32:45 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Sep 5 17:32:45 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected
Sep 5 17:32:50 VMESTONAME NetworkManager: <info> wlan0: link timed out.
Sep 5 17:32:55 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Sep 5 17:32:57 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Sep 5 17:32:57 VMESTONAME kernel: [ 686.973188] wlan0: authenticate with AP 00:19:5b:be:a3:c1
Sep 5 17:32:57 VMESTONAME kernel: [ 686.975055] wlan0: authenticated
Sep 5 17:32:57 VMESTONAME kernel: [ 686.975059] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep 5 17:32:57 VMESTONAME kernel: [ 686.977501] wlan0: RX AssocResp from 00:19:5b:be:a3:c1 (capab=0x431 status=0 aid=1)
Sep 5 17:32:57 VMESTONAME kernel: [ 686.977504] wlan0: associated
Sep 5 17:32:57 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: associating -> 4-way handshake
Sep 5 17:32:57 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: 4-way handshake -> associated
Sep 5 17:33:00 VMESTONAME NetworkManager: <info> Activation (wlan0/wireless): association took too long.
Sep 5 17:33:00 VMESTONAME NetworkManager: <info> (wlan0): device state change: 5 -> 6 (reason 0)
Sep 5 17:33:00 VMESTONAME kernel: [ 689.714098] wlan0: disassociating by local choice (reason=3)
Sep 5 17:33:00 VMESTONAME NetworkManager: <info> Activation (wlan0/wireless): asking for new secrets
Sep 5 17:33:00 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: associated -> disconnected
Sep 5 17:33:14 VMESTONAME NetworkManager: <info> wlan0: link timed out.
Sep 5 17:33:45 VMESTONAME kernel: [ 735.137258] [drm] Loading RV610 CP Microcode
Sep 5 17:33:45 VMESTONAME kernel: [ 735.137651] [drm] Loading RV610 PFP Microcode
Sep 5 17:33:45 VMESTONAME kernel: [ 735.152599] [drm] Resetting GPU
Sep 5 17:35:10 VMESTONAME kernel: [ 820.669244] [drm] Resetting GPU
Sep 5 17:41:02 VMESTONAME kernel: [ 1172.066804] [drm] Loading RV610 CP Microcode
Sep 5 17:41:02 VMESTONAME kernel: [ 1172.067196] [drm] Loading RV610 PFP Microcode
Sep 5 17:41:02 VMESTONAME kernel: [ 1172.082150] [drm] Resetting GPU
Sep 5 17:41:16 VMESTONAME NetworkManager: <WARN> update_one_setting(): Failed to update connection secrets: 1 802-1x
Sep 5 17:41:16 VMESTONAME NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting 'ipv4'.
Sep 5 17:41:16 VMESTONAME NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting '802-11-wireless'.
Sep 5 17:41:16 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 5 17:41:16 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Sep 5 17:41:16 VMESTONAME NetworkManager: <info> (wlan0): device state change: 6 -> 4 (reason 0)
Sep 5 17:41:16 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Sep 5 17:41:16 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Sep 5 17:41:16 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Sep 5 17:41:16 VMESTONAME NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Sep 5 17:41:16 VMESTONAME NetworkManager: <info> Activation (wlan0/wireless): connection 'default' has security, and secrets exist. No new secrets needed.
Sep 5 17:41:16 VMESTONAME NetworkManager: <info> Config: added 'ssid' value 'default'
Sep 5 17:41:16 VMESTONAME NetworkManager: <info> Config: added 'scan_ssid' value '1'
Sep 5 17:41:16 VMESTONAME NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Sep 5 17:41:16 VMESTONAME NetworkManager: <info> Config: added 'psk' value '<omitted>'
Sep 5 17:41:16 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Sep 5 17:41:16 VMESTONAME NetworkManager: <info> Config: set interface ap_scan to 1
Sep 5 17:41:16 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Sep 5 17:41:19 VMESTONAME kernel: [ 1188.896231] [drm] Resetting GPU
Sep 5 17:41:28 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Sep 5 17:41:28 VMESTONAME kernel: [ 1197.830196] wlan0: authenticate with AP 00:19:5b:be:a3:c1
Sep 5 17:41:28 VMESTONAME kernel: [ 1197.831967] wlan0: authenticated
Sep 5 17:41:28 VMESTONAME kernel: [ 1197.831971] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep 5 17:41:28 VMESTONAME kernel: [ 1197.834315] wlan0: RX AssocResp from 00:19:5b:be:a3:c1 (capab=0x431 status=0 aid=1)
Sep 5 17:41:28 VMESTONAME kernel: [ 1197.834319] wlan0: associated
Sep 5 17:41:28 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: associating -> 4-way handshake
Sep 5 17:41:28 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: 4-way handshake -> associated
Sep 5 17:41:31 VMESTONAME kernel: [ 1200.855619] wlan0: disassociated (Reason: 3)
Sep 5 17:41:31 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: associated -> disconnected
Sep 5 17:41:31 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Sep 5 17:41:32 VMESTONAME kernel: [ 1201.852132] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep 5 17:41:32 VMESTONAME kernel: [ 1202.052111] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep 5 17:41:32 VMESTONAME kernel: [ 1202.252134] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep 5 17:41:32 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected
Sep 5 17:41:32 VMESTONAME kernel: [ 1202.452113] wlan0: association with AP 00:19:5b:be:a3:c1 timed out
Sep 5 17:41:37 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Sep 5 17:41:38 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected
Sep 5 17:41:38 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Sep 5 17:41:39 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Sep 5 17:41:39 VMESTONAME kernel: [ 1209.642812] wlan0: authenticate with AP 00:19:5b:be:a3:c1
Sep 5 17:41:39 VMESTONAME kernel: [ 1209.660369] wlan0: authenticate with AP 00:19:5b:be:a3:c1
Sep 5 17:41:39 VMESTONAME kernel: [ 1209.660391] wlan0: authenticated
Sep 5 17:41:39 VMESTONAME kernel: [ 1209.660393] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep 5 17:41:39 VMESTONAME kernel: [ 1209.664729] wlan0: RX ReassocResp from 00:19:5b:be:a3:c1 (capab=0x431 status=0 aid=1)
Sep 5 17:41:39 VMESTONAME kernel: [ 1209.664732] wlan0: associated
Sep 5 17:41:39 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: associating -> 4-way handshake
Sep 5 17:41:39 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: 4-way handshake -> associated
Sep 5 17:41:42 VMESTONAME NetworkManager: <info> Activation (wlan0/wireless): association took too long.
Sep 5 17:41:42 VMESTONAME NetworkManager: <info> (wlan0): device state change: 5 -> 9 (reason 7)
Sep 5 17:41:42 VMESTONAME NetworkManager: <info> Activation (wlan0) failed for access point (default)
Sep 5 17:41:42 VMESTONAME kernel: [ 1211.715066] wlan0: disassociating by local choice (reason=3)
Sep 5 17:41:42 VMESTONAME NetworkManager: <info> Marking connection 'default' invalid.
Sep 5 17:41:42 VMESTONAME NetworkManager: <info> Activation (wlan0) failed.
Sep 5 17:41:42 VMESTONAME NetworkManager: <info> (wlan0): device state change: 9 -> 3 (reason 0)
Sep 5 17:41:42 VMESTONAME NetworkManager: <info> (wlan0): deactivating device (reason: 0).
Sep 5 17:41:42 VMESTONAME NetworkManager: <info> Hostname is not changed because Xorg server is active
Sep 5 17:41:42 VMESTONAME NetworkManager: <info> Hostname is not changed because Xorg server is active
Sep 5 17:43:52 VMESTONAME kernel: [ 1342.528272] [drm] Loading RV610 CP Microcode
Sep 5 17:43:52 VMESTONAME kernel: [ 1342.528664] [drm] Loading RV610 PFP Microcode
Sep 5 17:43:52 VMESTONAME kernel: [ 1342.543611] [drm] Resetting GPU
Sep 5 17:44:05 VMESTONAME kernel: [ 1355.152290] [drm] Resetting GPU
[-- Attachment #3: messagesok.txt --]
[-- Type: text/plain, Size: 10203 bytes --]
Sep 5 17:54:23 VMESTONAME NetworkManager: <WARN> update_one_setting(): Failed to update connection secrets: 1 802-1x
Sep 5 17:54:23 VMESTONAME NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting 'ipv4'.
Sep 5 17:54:23 VMESTONAME NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting '802-11-wireless'.
Sep 5 17:54:23 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 5 17:54:23 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Sep 5 17:54:23 VMESTONAME NetworkManager: <info> (wlan0): device state change: 6 -> 4 (reason 0)
Sep 5 17:54:23 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Sep 5 17:54:23 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Sep 5 17:54:23 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Sep 5 17:54:23 VMESTONAME NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Sep 5 17:54:23 VMESTONAME NetworkManager: <info> Activation (wlan0/wireless): connection 'default' has security, and secrets exist. No new secrets needed.
Sep 5 17:54:23 VMESTONAME NetworkManager: <info> Config: added 'ssid' value 'default'
Sep 5 17:54:23 VMESTONAME NetworkManager: <info> Config: added 'scan_ssid' value '1'
Sep 5 17:54:23 VMESTONAME NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Sep 5 17:54:23 VMESTONAME NetworkManager: <info> Config: added 'psk' value '<omitted>'
Sep 5 17:54:23 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Sep 5 17:54:23 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected
Sep 5 17:54:23 VMESTONAME NetworkManager: <info> Config: set interface ap_scan to 1
Sep 5 17:54:23 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Sep 5 17:54:35 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Sep 5 17:54:35 VMESTONAME kernel: [ 1985.145990] wlan0: authenticate with AP 00:19:5b:be:a3:c1
Sep 5 17:54:35 VMESTONAME kernel: [ 1985.147815] wlan0: authenticated
Sep 5 17:54:35 VMESTONAME kernel: [ 1985.147818] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep 5 17:54:35 VMESTONAME kernel: [ 1985.150299] wlan0: RX AssocResp from 00:19:5b:be:a3:c1 (capab=0x431 status=0 aid=1)
Sep 5 17:54:35 VMESTONAME kernel: [ 1985.150303] wlan0: associated
Sep 5 17:54:35 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: associating -> 4-way handshake
Sep 5 17:54:35 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: 4-way handshake -> associated
Sep 5 17:54:39 VMESTONAME NetworkManager: <info> wlan0: link timed out.
Sep 5 17:54:39 VMESTONAME kernel: [ 1988.885117] wlan0: disassociated (Reason: 3)
Sep 5 17:54:39 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: associated -> disconnected
Sep 5 17:54:39 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Sep 5 17:54:40 VMESTONAME kernel: [ 1989.884127] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep 5 17:54:40 VMESTONAME kernel: [ 1990.084126] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep 5 17:54:40 VMESTONAME kernel: [ 1990.284108] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep 5 17:54:40 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected
Sep 5 17:54:40 VMESTONAME kernel: [ 1990.484128] wlan0: association with AP 00:19:5b:be:a3:c1 timed out
Sep 5 17:54:45 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Sep 5 17:54:47 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Sep 5 17:54:47 VMESTONAME kernel: [ 1997.649459] wlan0: authenticate with AP 00:19:5b:be:a3:c1
Sep 5 17:54:47 VMESTONAME kernel: [ 1997.670493] wlan0: authenticate with AP 00:19:5b:be:a3:c1
Sep 5 17:54:47 VMESTONAME kernel: [ 1997.672319] wlan0: authenticated
Sep 5 17:54:47 VMESTONAME kernel: [ 1997.672323] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep 5 17:54:47 VMESTONAME kernel: [ 1997.674720] wlan0: RX ReassocResp from 00:19:5b:be:a3:c1 (capab=0x431 status=0 aid=1)
Sep 5 17:54:47 VMESTONAME kernel: [ 1997.674723] wlan0: associated
Sep 5 17:54:47 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: associating -> associated
Sep 5 17:54:47 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: associated -> 4-way handshake
Sep 5 17:54:48 VMESTONAME kernel: [ 1997.763177] padlock: VIA PadLock not detected.
Sep 5 17:54:48 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: 4-way handshake -> group handshake
Sep 5 17:54:48 VMESTONAME NetworkManager: <info> (wlan0): supplicant connection state: group handshake -> completed
Sep 5 17:54:48 VMESTONAME NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'default'.
Sep 5 17:54:48 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Sep 5 17:54:48 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Sep 5 17:54:48 VMESTONAME NetworkManager: <info> (wlan0): device state change: 5 -> 7 (reason 0)
Sep 5 17:54:48 VMESTONAME NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction.
Sep 5 17:54:48 VMESTONAME NetworkManager: <info> dhcpcd started with pid 9431
Sep 5 17:54:48 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Sep 5 17:54:48 VMESTONAME dhcpcd[9431]: wlan0: dhcpcd 4.0.15 starting
Sep 5 17:54:48 VMESTONAME NetworkManager: <info> DHCP: device wlan0 state changed (null) -> preinit
Sep 5 17:54:48 VMESTONAME dhcpcd[9431]: wlan0: broadcasting for a lease
Sep 5 17:54:49 VMESTONAME dhcpcd[9431]: wlan0: offered 192.168.0.3 from 192.168.0.1 `My Host'
Sep 5 17:54:49 VMESTONAME dhcpcd[9431]: wlan0: acknowledged 192.168.0.3 from 192.168.0.1 `My Host'
Sep 5 17:54:49 VMESTONAME dhcpcd[9431]: wlan0: leased 192.168.0.3 for 604800 seconds
Sep 5 17:54:49 VMESTONAME avahi-daemon[6912]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.3.
Sep 5 17:54:49 VMESTONAME avahi-daemon[6912]: New relevant interface wlan0.IPv4 for mDNS.
Sep 5 17:54:49 VMESTONAME avahi-daemon[6912]: Registering new address record for 192.168.0.3 on wlan0.IPv4.
Sep 5 17:54:49 VMESTONAME NetworkManager: <info> DHCP: device wlan0 state changed preinit -> bound
Sep 5 17:54:49 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
Sep 5 17:54:49 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
Sep 5 17:54:49 VMESTONAME NetworkManager: <info> address 192.168.0.3
Sep 5 17:54:49 VMESTONAME NetworkManager: <info> prefix 24 (255.255.255.0)
Sep 5 17:54:49 VMESTONAME NetworkManager: <info> gateway 192.168.0.1
Sep 5 17:54:49 VMESTONAME NetworkManager: <info> nameserver '213.234.192.7'
Sep 5 17:54:49 VMESTONAME NetworkManager: <info> nameserver '85.21.192.5'
Sep 5 17:54:49 VMESTONAME NetworkManager: <info> nameserver '192.168.0.1'
Sep 5 17:54:49 VMESTONAME NetworkManager: <info> domain name 'MSHOME'
Sep 5 17:54:49 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Sep 5 17:54:49 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
Sep 5 17:54:49 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Sep 5 17:54:49 VMESTONAME avahi-daemon[6912]: Withdrawing address record for 192.168.0.3 on wlan0.
Sep 5 17:54:49 VMESTONAME avahi-daemon[6912]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.3.
Sep 5 17:54:49 VMESTONAME avahi-daemon[6912]: Interface wlan0.IPv4 no longer relevant for mDNS.
Sep 5 17:54:49 VMESTONAME avahi-daemon[6912]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.3.
Sep 5 17:54:49 VMESTONAME avahi-daemon[6912]: New relevant interface wlan0.IPv4 for mDNS.
Sep 5 17:54:49 VMESTONAME avahi-daemon[6912]: Registering new address record for 192.168.0.3 on wlan0.IPv4.
Sep 5 17:54:50 VMESTONAME NetworkManager: <info> (wlan0): writing resolv.conf to /sbin/resolvconf
Sep 5 17:54:51 VMESTONAME named[6046]: loading configuration from '/etc/named.conf'
Sep 5 17:54:51 VMESTONAME named[6046]: using default UDP/IPv4 port range: [1024, 65535]
Sep 5 17:54:51 VMESTONAME bind: sending signal 1 to named succeeded
Sep 5 17:54:51 VMESTONAME named[6046]: using default UDP/IPv6 port range: [1024, 65535]
Sep 5 17:54:51 VMESTONAME named[6046]: listening on IPv4 interface wlan0, 192.168.0.3#53
Sep 5 17:54:51 VMESTONAME named[6046]: could not listen on UDP socket: permission denied
Sep 5 17:54:51 VMESTONAME named[6046]: creating IPv4 interface wlan0 failed; interface ignored
Sep 5 17:54:51 VMESTONAME NetworkManager: <info> Hostname is not changed because Xorg server is active
Sep 5 17:54:51 VMESTONAME NetworkManager: <info> (wlan0): device state change: 7 -> 8 (reason 0)
Sep 5 17:54:51 VMESTONAME NetworkManager: <info> (wlan0): writing resolv.conf to /sbin/resolvconf
Sep 5 17:54:51 VMESTONAME NetworkManager: <info> Policy set 'default' (wlan0) as default for routing and DNS.
Sep 5 17:54:51 VMESTONAME NetworkManager: <info> Hostname is not changed because Xorg server is active
Sep 5 17:54:51 VMESTONAME NetworkManager: <info> Activation (wlan0) successful, device activated.
Sep 5 17:54:51 VMESTONAME NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Sep 5 17:55:09 VMESTONAME kernel: [ 2018.912239] [drm] Resetting GPU
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Comm] wifi авторизация
2010-09-28 6:41 [Comm] wifi авторизация Anatoly Rezvushkin
@ 2010-09-28 10:14 ` Mikhail Efremov
2010-09-28 18:47 ` rezvushkin
0 siblings, 1 reply; 14+ messages in thread
From: Mikhail Efremov @ 2010-09-28 10:14 UTC (permalink / raw)
To: community
On Tue, 28 Sep 2010 10:41:59 +0400
Anatoly Rezvushkin wrote:
> Файлы успешной и неуспешной попыток соединения прилагаю.
ps ax | grep wpa_supplicant для начала.
--
WBR, Mikhail Efremov
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Comm] wifi авторизация
2010-09-28 10:14 ` Mikhail Efremov
@ 2010-09-28 18:47 ` rezvushkin
2010-09-29 10:47 ` Andriy Dobrovol`s`kii
2010-09-29 11:58 ` Mikhail Efremov
0 siblings, 2 replies; 14+ messages in thread
From: rezvushkin @ 2010-09-28 18:47 UTC (permalink / raw)
To: 'ALT Linux Community general discussions'
> Файлы успешной и неуспешной попыток соединения прилагаю.
ps ax | grep wpa_supplicant для начала.
--
WBR, Mikhail Efremov
[root@VMESTONAME ~]# ps ax | grep wpa_supplicant
6227 ? S 0:00 /usr/sbin/wpa_supplicant -u
10105 pts/1 S+ 0:00 grep wpa_supplicant
В настоящее время соединятся стало часто, но пакеты не бегают, пингуется
только шлюз(D-link 824), остальные Network is unreachable.
Как посмотреть в строке не знаю.
В графическом режиме при наведении курсора на иконку пишет, что IP и DNSы
получены, нехватает только красного сердечка,
Которое есть при нормальном соединении.
В общем крыша отъезжает.
Резвушкин Анатолий
_______________________________________________
community mailing list
community@lists.altlinux.org
https://lists.altlinux.org/mailman/listinfo/community
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Comm] wifi авторизация
2010-09-28 18:47 ` rezvushkin
@ 2010-09-29 10:47 ` Andriy Dobrovol`s`kii
2010-09-29 17:27 ` rezvushkin
2010-09-29 11:58 ` Mikhail Efremov
1 sibling, 1 reply; 14+ messages in thread
From: Andriy Dobrovol`s`kii @ 2010-09-29 10:47 UTC (permalink / raw)
To: ALT Linux Community general discussions
Попробуйте:
ip l l
ip a l
ip r l
cat /etc/resolve.conf
2010/9/28 rezvushkin <rezvushkin@mail.ru>:
>
>
>
>> Файлы успешной и неуспешной попыток соединения прилагаю.
>
> ps ax | grep wpa_supplicant для начала.
>
> --
> WBR, Mikhail Efremov
>
>
> [root@VMESTONAME ~]# ps ax | grep wpa_supplicant
> 6227 ? S 0:00 /usr/sbin/wpa_supplicant -u
> 10105 pts/1 S+ 0:00 grep wpa_supplicant
>
>
> В настоящее время соединятся стало часто, но пакеты не бегают, пингуется
> только шлюз(D-link 824), остальные Network is unreachable.
> Как посмотреть в строке не знаю.
> В графическом режиме при наведении курсора на иконку пишет, что IP и DNSы
> получены, нехватает только красного сердечка,
> Которое есть при нормальном соединении.
> В общем крыша отъезжает.
>
> Резвушкин Анатолий
> _______________________________________________
> community mailing list
> community@lists.altlinux.org
> https://lists.altlinux.org/mailman/listinfo/community
> _______________________________________________
> community mailing list
> community@lists.altlinux.org
> https://lists.altlinux.org/mailman/listinfo/community
--
Regards,
Andrii Dobrovol`s`kyj
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Comm] wifi авторизация
2010-09-28 18:47 ` rezvushkin
2010-09-29 10:47 ` Andriy Dobrovol`s`kii
@ 2010-09-29 11:58 ` Mikhail Efremov
2010-09-29 17:54 ` rezvushkin
1 sibling, 1 reply; 14+ messages in thread
From: Mikhail Efremov @ 2010-09-29 11:58 UTC (permalink / raw)
To: community
On Tue, 28 Sep 2010 22:47:21 +0400 rezvushkin wrote:
> В настоящее время соединятся стало часто, но пакеты не бегают,
Последовательность
supplicant connection state: associating -> 4-way handshake
supplicant connection state: 4-way handshake -> associated
явно неправильная. Можно попробовать использовать
wpa_supplicant напрямую, без NM. Но проблема скорее всего либо в
wpa_supplicant, либо в драйвере. Кстати, какой драйвер используется?
Посмотрите с помощью lspci -k.
> пингуется только шлюз(D-link 824), остальные Network is unreachable.
Возможно dhcp-сервер не присылает шлюз по умолчанию. Или в настройках
соединения стоит его не использовать.
--
WBR, Mikhail Efremov
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Comm] wifi авторизация
2010-09-29 10:47 ` Andriy Dobrovol`s`kii
@ 2010-09-29 17:27 ` rezvushkin
2010-09-30 11:03 ` Andriy Dobrovol`s`kii
0 siblings, 1 reply; 14+ messages in thread
From: rezvushkin @ 2010-09-29 17:27 UTC (permalink / raw)
To: 'ALT Linux Community general discussions'
Попробуйте:
ip l l
ip a l
ip r l
cat /etc/resolve.conf
root@VMESTONAME ~]# ip l l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN qlen 1000
link/ether 00:1b:38:15:8b:fa brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen
1000
link/ether 00:13:e8:31:ef:77 brd ff:ff:ff:ff:ff:ff
4: pan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
link/ether a6:ef:d9:a5:e1:14 brd ff:ff:ff:ff:ff:ff
5: vboxnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 1000
link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
[root@VMESTONAME ~]# ip a l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN qlen 1000
link/ether 00:1b:38:15:8b:fa brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen
1000
link/ether 00:13:e8:31:ef:77 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.3/24 brd 192.168.0.255 scope global wlan0
4: pan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
link/ether a6:ef:d9:a5:e1:14 brd ff:ff:ff:ff:ff:ff
5: vboxnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 1000
link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
[root@VMESTONAME ~]# ip r l
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.3 metric
2
[root@VMESTONAME ~]# cat /etc/resolv.conf # Generated by resolvconf # Do not
edit manually, use # /etc/net/ifaces/<interface>/resolv.conf instead.
search MSHOME
nameserver 127.0.0.1
nameserver 213.234.192.7
nameserver 85.21.192.5
nameserver 192.168.0.1
С уважением,
Резвушкин Анатолий
--
Regards,
Andrii Dobrovol`s`kyj
_______________________________________________
community mailing list
community@lists.altlinux.org
https://lists.altlinux.org/mailman/listinfo/community
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Comm] wifi авторизация
2010-09-29 11:58 ` Mikhail Efremov
@ 2010-09-29 17:54 ` rezvushkin
2010-09-30 17:54 ` Mikhail Efremov
0 siblings, 1 reply; 14+ messages in thread
From: rezvushkin @ 2010-09-29 17:54 UTC (permalink / raw)
To: 'ALT Linux Community general discussions'
>> В настоящее время соединятся стало часто, но пакеты не бегают,
>Последовательность
>supplicant connection state: associating -> 4-way handshake
>supplicant connection state: 4-way handshake -> associated
>явно неправильная.
Это понятно, что 4-way handshake процедура незакончена.
Но Кто виноват? и Что делать? :)
> Можно попробовать использовать
>wpa_supplicant напрямую, без NM.
Это мне сразу не осилить.
>Но проблема скорее всего либо в
>wpa_supplicant, либо в драйвере. Кстати, какой драйвер используется?
>Посмотрите с помощью lspci -k.
Драйвер iwlagn
>> пингуется только шлюз(D-link 824), остальные Network is unreachable.
>Возможно dhcp-сервер не присылает шлюз по умолчанию. Или в настройках
>соединения стоит его не использовать.
Когда задаешь все IP параметры вручную (и шлюз) ничего не меняется.
Какой командой можно проверить установлен ли шлюз не знаю.
С уважением,
Анатолий Резвушкин.
--
WBR, Mikhail Efremov
_______________________________________________
community mailing list
community@lists.altlinux.org
https://lists.altlinux.org/mailman/listinfo/community
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Comm] wifi авторизация
2010-09-29 17:27 ` rezvushkin
@ 2010-09-30 11:03 ` Andriy Dobrovol`s`kii
2010-09-30 18:00 ` Mikhail Efremov
0 siblings, 1 reply; 14+ messages in thread
From: Andriy Dobrovol`s`kii @ 2010-09-30 11:03 UTC (permalink / raw)
To: ALT Linux Community general discussions
2010/9/29 rezvushkin <rezvushkin@mail.ru>:
>
> Попробуйте:
> ip l l
> ip a l
> ip r l
> cat /etc/resolve.conf
>
>
> root@VMESTONAME ~]# ip l l
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
> state DOWN qlen 1000
>
> link/ether 00:1b:38:15:8b:fa brd ff:ff:ff:ff:ff:ff
>
> 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen
> 1000
> link/ether 00:13:e8:31:ef:77 brd ff:ff:ff:ff:ff:ff
>
Интерфейс поднялся
> 4: pan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
>
> link/ether a6:ef:d9:a5:e1:14 brd ff:ff:ff:ff:ff:ff
>
> 5: vboxnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UNKNOWN qlen 1000
>
> link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
>
> [root@VMESTONAME ~]# ip a l
>
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
>
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>
> inet 127.0.0.1/8 scope host lo
>
> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
> state DOWN qlen 1000
>
> link/ether 00:1b:38:15:8b:fa brd ff:ff:ff:ff:ff:ff
>
> 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen
> 1000
> link/ether 00:13:e8:31:ef:77 brd ff:ff:ff:ff:ff:ff
>
> inet 192.168.0.3/24 brd 192.168.0.255 scope global wlan0
>
Адрес получил.
> 4: pan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
>
> link/ether a6:ef:d9:a5:e1:14 brd ff:ff:ff:ff:ff:ff
>
> 5: vboxnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UNKNOWN qlen 1000
>
> link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
>
> [root@VMESTONAME ~]# ip r l
> 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.3 metric
> 2
С маршрутизацией у Вас полный писец. Или Вы чего-то не докопировали.
> [root@VMESTONAME ~]# cat /etc/resolv.conf # Generated by resolvconf # Do not
> edit manually, use # /etc/net/ifaces/<interface>/resolv.conf instead.
> search MSHOME
> nameserver 127.0.0.1
> nameserver 213.234.192.7
> nameserver 85.21.192.5
> nameserver 192.168.0.1
>
Если я ничего не путаю, нужный Вам nameserver последний в списке. Т.е.
к нему никогда обращений не будет. Опрашиваются только 2 первых НСа.
Избавьтесь от лишнего, вылечите маршрутизацию -- и все будет работать.
> С уважением,
> Резвушкин Анатолий
> --
> Regards,
> Andrii Dobrovol`s`kyj
--
Regards,
Andrii Dobrovol`s`kyj
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Comm] wifi авторизация
2010-09-29 17:54 ` rezvushkin
@ 2010-09-30 17:54 ` Mikhail Efremov
2010-10-01 17:48 ` rezvushkin
2010-10-01 18:11 ` rezvushkin
0 siblings, 2 replies; 14+ messages in thread
From: Mikhail Efremov @ 2010-09-30 17:54 UTC (permalink / raw)
To: community
On Wed, 29 Sep 2010 21:54:51 +0400 rezvushkin wrote:
> >Последовательность
> >supplicant connection state: associating -> 4-way handshake
> >supplicant connection state: 4-way handshake -> associated
> >явно неправильная.
> Это понятно, что 4-way handshake процедура незакончена.
> Но Кто виноват? и Что делать? :)
Искать виноватого. Для начала нужно убедиться, что это не NM.
> > Можно попробовать использовать
> >wpa_supplicant напрямую, без NM.
> Это мне сразу не осилить.
Настройте через альтератор. В
Ethernet-интерфейсы->Дополнительно->Сетевая подсистема поставьте etcnet
для этого интерфейса. Появится кнопка настройки WiFi.
На всякий случай можно вообще остановить NM и рестартовать network:
service NetworkManager stop
killall wpa_supplicant
service network restart
Если проблема останется, то влияние NM можно исключить. Надо будет
запускать wpa_supplicant руками и смотреть его вывод.
Примерно так:
killall wpa_supplicant
wpa_supplicant -dd -Dwext -iwlan0 -c/etc/net/ifaces/wlan0/wpa_supplicant.conf
> Какой командой можно проверить установлен ли шлюз не знаю.
ip r покажет маршруты.
--
WBR, Mikhail Efremov
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Comm] wifi авторизация
2010-09-30 11:03 ` Andriy Dobrovol`s`kii
@ 2010-09-30 18:00 ` Mikhail Efremov
0 siblings, 0 replies; 14+ messages in thread
From: Mikhail Efremov @ 2010-09-30 18:00 UTC (permalink / raw)
To: community
On Thu, 30 Sep 2010 14:03:26 +0300 Andriy Dobrovol`s`kii wrote:
> > [root@VMESTONAME ~]# ip r l
> > 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.3
> > metric 2
> С маршрутизацией у Вас полный писец. Или Вы чего-то не докопировали.
Просто маршрута по умолчанию нет. Надо проверять настройки соединения и
dhcp-сервера.
> > nameserver 127.0.0.1
> > nameserver 213.234.192.7
> > nameserver 85.21.192.5
> > nameserver 192.168.0.1
> >
> Если я ничего не путаю, нужный Вам nameserver последний в списке. Т.е.
> к нему никогда обращений не будет. Опрашиваются только 2 первых НСа.
> Избавьтесь от лишнего, вылечите маршрутизацию -- и все будет работать.
resolvconf -l покажет откуда что.
--
WBR, Mikhail Efremov
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Comm] wifi авторизация
2010-09-30 17:54 ` Mikhail Efremov
@ 2010-10-01 17:48 ` rezvushkin
2010-10-03 10:34 ` Mikhail Efremov
2010-10-01 18:11 ` rezvushkin
1 sibling, 1 reply; 14+ messages in thread
From: rezvushkin @ 2010-10-01 17:48 UTC (permalink / raw)
To: 'ALT Linux Community general discussions'
>Настройте через альтератор. В
>Ethernet-интерфейсы->Дополнительно->Сетевая подсистема поставьте etcnet
>для этого интерфейса. Появится кнопка настройки WiFi.
>На всякий случай можно вообще остановить NM и рестартовать network:
>service NetworkManager stop
>killall wpa_supplicant
>service network restart
.Если проблема останется, то влияние NM можно исключить. Надо будет
.запускать wpa_supplicant руками и смотреть его вывод.
>Примерно так:
>killall wpa_supplicant
>wpa_supplicant -dd -Dwext -iwlan0
->c/etc/net/ifaces/wlan0/wpa_supplicant.conf
[root@VMESTONAME ~]# servise NetworkManager stop
-bash: servise: command not found
[root@VMESTONAME ~]# killall wpa_supplicant [root@VMESTONAME ~]#
wpa_supplicant -dd -Dwext -iwlan0 - Initializing interface 'wlan0' conf
'/etc/net/ifaces/wlan0/wpa_supplicant.conf' driver 'wext' ctrl_interface
'N/A' bridge 'N/A'
Configuration file '/etc/net/ifaces/wlan0/wpa_supplicant.conf' ->
'/etc/net/ifaces/wlan0/wpa_supplicant.conf'
Reading configuration file '/etc/net/ifaces/wlan0/wpa_supplicant.conf'
Failed to read or parse configuration
'/etc/net/ifaces/wlan0/wpa_supplicant.conf'.
Failed to add interface wlan0
Cancelling scan request
Cancelling authentication timeout
[root@VMESTONAME ~]#
> Какой командой можно проверить установлен ли шлюз не знаю.
ip r покажет маршруты.
Сравнил с работающим нетбуком не хватает default 192.168.0.1
Как добавить в терминале не знаю.
--
WBR, Mikhail Efremov
_______________________________________________
community mailing list
community@lists.altlinux.org
https://lists.altlinux.org/mailman/listinfo/community
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Comm] wifi авторизация
2010-09-30 17:54 ` Mikhail Efremov
2010-10-01 17:48 ` rezvushkin
@ 2010-10-01 18:11 ` rezvushkin
2010-10-01 19:32 ` Andriy Dobrovol`s`kii
1 sibling, 1 reply; 14+ messages in thread
From: rezvushkin @ 2010-10-01 18:11 UTC (permalink / raw)
To: 'ALT Linux Community general discussions'
>> [root@VMESTONAME ~]# ip r l
>> 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.3
>> metric
>> .2
>С маршрутизацией у Вас полный писец. Или Вы чего-то не докопировали.
Скопировано правильно.
Как удалось выяснить с помощья рабочего нетбука не хватает только default
via 192.168.0.1
>> [root@VMESTONAME ~]# cat /etc/resolv.conf # Generated by resolvconf #
>> Do not edit manually, use # /etc/net/ifaces/<interface>/resolv.conf
instead.
>> search MSHOME
>> nameserver 127.0.0.1
>> nameserver 213.234.192.7
>> nameserver 85.21.192.5
>> nameserver 192.168.0.1
>>
>Если я ничего не путаю, нужный Вам nameserver последний в списке. Т.е.
>к нему никогда обращений не будет. Опрашиваются только 2 первых НСа.
>Избавьтесь от лишнего, вылечите маршрутизацию -- и все будет работать.
Только изменение порядка в списке ничего не дает, А как добавить маршрут по
умолчанию я не знаю.
С уважением,
Резвушкин Анатолий
> --
> Regards,
> Andrii Dobrovol`s`kyj
--
Regards,
Andrii Dobrovol`s`kyj
_______________________________________________
community mailing list
community@lists.altlinux.org
https://lists.altlinux.org/mailman/listinfo/community
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Comm] wifi авторизация
2010-10-01 18:11 ` rezvushkin
@ 2010-10-01 19:32 ` Andriy Dobrovol`s`kii
0 siblings, 0 replies; 14+ messages in thread
From: Andriy Dobrovol`s`kii @ 2010-10-01 19:32 UTC (permalink / raw)
To: ALT Linux Community general discussions
ip r add default via your.gate.way
но это разово. вам нужно разобраться почему оно не добавляется автоматически.
2010/10/1 rezvushkin <rezvushkin@mail.ru>:
>
>>> [root@VMESTONAME ~]# ip r l
>>> 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.3
>>> metric
>>> .2
>>С маршрутизацией у Вас полный писец. Или Вы чего-то не докопировали.
> Скопировано правильно.
> Как удалось выяснить с помощья рабочего нетбука не хватает только default
> via 192.168.0.1
>>> [root@VMESTONAME ~]# cat /etc/resolv.conf # Generated by resolvconf #
>>> Do not edit manually, use # /etc/net/ifaces/<interface>/resolv.conf
> instead.
>>> search MSHOME
>>> nameserver 127.0.0.1
>>> nameserver 213.234.192.7
>>> nameserver 85.21.192.5
>>> nameserver 192.168.0.1
>>>
>>Если я ничего не путаю, нужный Вам nameserver последний в списке. Т.е.
>>к нему никогда обращений не будет. Опрашиваются только 2 первых НСа.
>>Избавьтесь от лишнего, вылечите маршрутизацию -- и все будет работать.
> Только изменение порядка в списке ничего не дает, А как добавить маршрут по
> умолчанию я не знаю.
> С уважением,
> Резвушкин Анатолий
>> --
>> Regards,
>> Andrii Dobrovol`s`kyj
>
> --
> Regards,
> Andrii Dobrovol`s`kyj
> _______________________________________________
> community mailing list
> community@lists.altlinux.org
> https://lists.altlinux.org/mailman/listinfo/community
> _______________________________________________
> community mailing list
> community@lists.altlinux.org
> https://lists.altlinux.org/mailman/listinfo/community
--
Regards,
Andrii Dobrovol`s`kyj
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Comm] wifi авторизация
2010-10-01 17:48 ` rezvushkin
@ 2010-10-03 10:34 ` Mikhail Efremov
0 siblings, 0 replies; 14+ messages in thread
From: Mikhail Efremov @ 2010-10-03 10:34 UTC (permalink / raw)
To: ALT Linux Community general discussions
On Fri, 1 Oct 2010 21:48:17 +0400 rezvushkin wrote:
> .Если проблема останется, то влияние NM можно исключить. Надо будет
> .запускать wpa_supplicant руками и смотреть его вывод.
> >Примерно так:
> >killall wpa_supplicant
> >wpa_supplicant -dd -Dwext -iwlan0
> ->c/etc/net/ifaces/wlan0/wpa_supplicant.conf
> [root@VMESTONAME ~]# servise NetworkManager stop
> -bash: servise: command not found
После этого можно было и не продолжать. Скопируйте из моего письма,
если не можете написать команду правильно. Вообще ругань, что команда
не найдена, должна была насторожить.
> Failed to read or parse configuration
> '/etc/net/ifaces/wlan0/wpa_supplicant.conf'.
Этот конфиг точно есть и сгенерирован с помощью альтератора, как я
описывал?
--
WBR, Mikhail Efremov
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2010-10-03 10:34 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-09-28 6:41 [Comm] wifi авторизация Anatoly Rezvushkin
2010-09-28 10:14 ` Mikhail Efremov
2010-09-28 18:47 ` rezvushkin
2010-09-29 10:47 ` Andriy Dobrovol`s`kii
2010-09-29 17:27 ` rezvushkin
2010-09-30 11:03 ` Andriy Dobrovol`s`kii
2010-09-30 18:00 ` Mikhail Efremov
2010-09-29 11:58 ` Mikhail Efremov
2010-09-29 17:54 ` rezvushkin
2010-09-30 17:54 ` Mikhail Efremov
2010-10-01 17:48 ` rezvushkin
2010-10-03 10:34 ` Mikhail Efremov
2010-10-01 18:11 ` rezvushkin
2010-10-01 19:32 ` Andriy Dobrovol`s`kii
ALT Linux Community general discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/community/0 community/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 community community/ http://lore.altlinux.org/community \
mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
public-inbox-index community
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.community
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git