<![CDATA[Linux Forum — wifi, не присваивается IP-адрес]]> https://linuxforum.ru/viewtopic.php?id=6394 Thu, 09 Sep 2010 03:53:55 +0000 PunBB <![CDATA[Re: wifi, не присваивается IP-адрес]]> https://linuxforum.ru/viewtopic.php?pid=89339#p89339 Позвонить по телефону провайдеру можно? За 10минут такие проблемы решаются. Или искать в Интернете  инструкцию на свой роутер.

]]> Thu, 09 Sep 2010 03:53:55 +0000 https://linuxforum.ru/viewtopic.php?pid=89339#p89339 <![CDATA[wifi, не присваивается IP-адрес]]> https://linuxforum.ru/viewtopic.php?pid=88579#p88579 Доброго времени суток.
Столкнулся со следующей проблемой. (Linux Mint 7+ d-link dwa-131) + asus WL-500W. Wifi адаптер успешно увиделся компом (при помощи родных виндузовых дров и ndiswrapper'a), нашел доступные беспроводные сети, но при попытке подключиться дальше аутентификации дело не идет, IP адрес получить не удается.
iwconfig:

wlan1     IEEE 802.11g  ESSID:off/any  
          Mode:Managed  Frequency:2.437 GHz  Access Point: Not-Associated   
          Bit Rate:52 Mb/s   Tx-Power:20 dBm   Sensitivity=0/3  
          RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

syslog:

Sep  5 09:16:47 pullya-desktop dhclient: DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 11
Sep  5 09:16:51 pullya-desktop NetworkManager: <info>  (wlan1): supplicant connection state:  scanning -> associating 
Sep  5 09:16:53 pullya-desktop NetworkManager: <info>  (wlan1): supplicant connection state:  associating -> associated 
Sep  5 09:16:53 pullya-desktop NetworkManager: <info>  (wlan1): supplicant connection state:  associated -> 4-way handshake 
Sep  5 09:16:53 pullya-desktop NetworkManager: <info>  (wlan1): supplicant connection state:  4-way handshake -> group handshake 
Sep  5 09:16:53 pullya-desktop NetworkManager: <info>  (wlan1): supplicant connection state:  group handshake -> completed 
Sep  5 09:16:54 pullya-desktop NetworkManager: <info>  (wlan1): supplicant connection state:  completed -> 4-way handshake 
Sep  5 09:16:54 pullya-desktop NetworkManager: <info>  (wlan1): supplicant connection state:  4-way handshake -> group handshake 
Sep  5 09:16:54 pullya-desktop NetworkManager: <info>  (wlan1): supplicant connection state:  group handshake -> completed 
Sep  5 09:16:55 pullya-desktop NetworkManager: <info>  (wlan1): supplicant connection state:  completed -> 4-way handshake 
Sep  5 09:16:55 pullya-desktop NetworkManager: <info>  (wlan1): supplicant connection state:  4-way handshake -> group handshake 
Sep  5 09:16:55 pullya-desktop NetworkManager: <info>  (wlan1): supplicant connection state:  group handshake -> completed 
Sep  5 09:16:55 pullya-desktop NetworkManager: <info>  Device 'wlan1' DHCP transaction took too long (>45s), stopping it. 
Sep  5 09:16:56 pullya-desktop NetworkManager: <info>  wlan1: canceled DHCP transaction, dhcp client pid 21639 
Sep  5 09:16:56 pullya-desktop NetworkManager: <info>  Activation (wlan1) Stage 4 of 5 (IP Configure Timeout) scheduled... 
Sep  5 09:16:56 pullya-desktop NetworkManager: <info>  Activation (wlan1) Stage 4 of 5 (IP Configure Timeout) started... 
Sep  5 09:16:56 pullya-desktop NetworkManager: <info>  (wlan1): device state change: 7 -> 9 
Sep  5 09:16:56 pullya-desktop NetworkManager: <info>  Activation (wlan1) failed for access point (rikku-w) 
Sep  5 09:16:56 pullya-desktop NetworkManager: <info>  Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) 
Sep  5 09:16:56 pullya-desktop NetworkManager: <info>  Marking connection 'Auto rikku-w' invalid. 
Sep  5 09:16:56 pullya-desktop NetworkManager: <info>  Activation (wlan1) failed. 
Sep  5 09:16:56 pullya-desktop NetworkManager: <info>  Activation (wlan1) Stage 4 of 5 (IP Configure Timeout) complete. 
Sep  5 09:16:56 pullya-desktop NetworkManager: <info>  (wlan1): supplicant connection state:  completed -> 4-way handshake 
Sep  5 09:16:56 pullya-desktop NetworkManager: <info>  (wlan1): supplicant connection state:  4-way handshake -> group handshake 
Sep  5 09:16:56 pullya-desktop NetworkManager: <info>  (wlan1): supplicant connection state:  group handshake -> completed 
Sep  5 09:16:56 pullya-desktop NetworkManager: <info>  (wlan1): device state change: 9 -> 3 
Sep  5 09:16:56 pullya-desktop NetworkManager: <info>  (wlan1): deactivating device (reason: 0). 
Sep  5 09:16:56 pullya-desktop NetworkManager: <info>  Policy set 'Auto eth0' (eth0) as default for routing and DNS.

wpa-supplicant.log:

Trying to associate with 00:22:15:24:25:3b (SSID='rikku-w' freq=2437 MHz)
Associated with 00:22:15:24:25:3b
WPA: Key negotiation completed with 00:22:15:24:25:3b &#91;PTK=CCMP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:22:15:24:25:3b completed (reauth) &#91;id=0 id_str=]
WPA: Key negotiation completed with 00:22:15:24:25:3b &#91;PTK=CCMP GTK=TKIP]
WPA: Key negotiation completed with 00:22:15:24:25:3b &#91;PTK=CCMP GTK=TKIP]
WPA: Key negotiation completed with 00:22:15:24:25:3b &#91;PTK=CCMP GTK=TKIP]
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-SCAN-RESULTS

system log на асусе:

Sep  5 09:16:26 kernel: eth2: received packet with  own address as source address
Sep  5 09:16:40 kernel: eth2: received packet with  own address as source address
Sep  5 09:16:54 kernel: eth2: received packet with  own address as source address

Пользовался как network manager'ом, так и wicd - результат один.
wicd.log

2010/09/05 23:22:21 :: Connecting to wireless network rikku-w
2010/09/05 23:22:21 :: Putting interface down
2010/09/05 23:22:21 :: Releasing DHCP leases...
2010/09/05 23:22:21 :: Setting false IP...
2010/09/05 23:22:21 :: Stopping wpa_supplicant and any DHCP clients
2010/09/05 23:22:21 :: Flushing the routing table...
2010/09/05 23:22:22 :: Generating psk...
2010/09/05 23:22:22 :: Attempting to authenticate...
2010/09/05 23:22:22 :: Putting interface up...
2010/09/05 23:22:24 :: Running DHCP
2010/09/05 23:22:24 :: Internet Systems Consortium DHCP Client V3.1.1
2010/09/05 23:22:24 :: Copyright 2004-2008 Internet Systems Consortium.
2010/09/05 23:22:24 :: All rights reserved.
2010/09/05 23:22:24 :: For info, please visit http://www.isc.org/sw/dhcp/
2010/09/05 23:22:24 ::
2010/09/05 23:22:25 :: Listening on LPF/wlan1/00:26:5a:bc:1c:fb
2010/09/05 23:22:25 :: Sending on   LPF/wlan1/00:26:5a:bc:1c:fb
2010/09/05 23:22:25 :: Sending on   Socket/fallback
2010/09/05 23:22:27 :: DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 7
2010/09/05 23:22:34 :: DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 16
2010/09/05 23:22:36 :: canceling connection attempt
2010/09/05 23:22:36 :: DHCP connection failed
2010/09/05 23:22:36 :: exiting connection thread

Интуитивно понимаю, что копать нужно в сторону "received packet with own address as source address", но что делать конкретно?

Если проблема возникает на этапе получения IP от DHCP, то может имеет смысл в настройках wicd прописать статический IP компа и адрес DNS сервера? Теоретически возможна такая схема работы (т.е. на роутере поднят DHCP, который раздает IP автоматически всем кроме одной машины, IP которой прописан статически)?

]]> Tue, 07 Sep 2010 06:36:31 +0000 https://linuxforum.ru/viewtopic.php?pid=88579#p88579