can not connect access point

Waleed Hamra kubuntu-users at whamra.com
Sat Aug 27 09:42:58 UTC 2011


On 08/25/2011 08:05 PM, Michael Renner wrote:
> Moin,
> 
> I use kubuntu 10.04, under normal circumstances with the eth-Interface. Now I 
> want to connect this notebook to a wpa2 encrypted wireless lan. But the 
> connect fail). The USB Stick (Sitecom WL113) is identified, and the interface 
> eth1 is  brought up.
> 
> 20719.312118] usb 4-2: new high speed USB device using ehci_hcd and address 3
> [20719.457047] usb 4-2: configuration #1 chosen from 1 choice
> [20719.572120] usb 4-2: reset high speed USB device using ehci_hcd and address 
> 3
> [20719.706011] cfg80211: Disabling channel 2484 MHz on phy2 due to Country IE
> [20719.725318] phy2: Selected rate control algorithm 'minstrel'
> [20719.736104] zd1211rw 4-2:1.0: phy2
> [20719.847166] udev: renamed network interface wlan0 to wlan1
> [20719.854873] usb 4-2: firmware: requesting zd1211/zd1211_ub
> [20719.963901] usb 4-2: firmware: requesting zd1211/zd1211_uphr
> [20720.102389] zd1211rw 4-2:1.0: firmware version 4605
> [20720.144438] zd1211rw 4-2:1.0: zd1211 chip 0df6:9071 v4330 high 00-0c-f6 
> AL2230_RF pa0 -----
> [20720.147533] cfg80211: Calling CRDA for country: DE
> [20720.167153] ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [20720.238162] cfg80211: Current regulatory domain intersected:
> [20720.238177]  (start_freq - end_freq @ bandwidth), (max_antenna_gain, 
> max_eirp)
> [20720.238184]  (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
> 
> ifconfig zeigt das Device an, und iwlist findet meinen AP:
> root at lyra:~# ifconfig wlan1
> wlan1     Link encap:Ethernet  HWaddr 00:0c:f6:13:f5:73
>           UP BROADCAST 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)
> 
> 
> Also the AP seems to be in range:
> root at lyra:~# iwlist wlan1 scan
> wlan1     Scan completed :
>           Cell 01 - Address: 00:19:70:68:55:11
>                     Channel:6
>                     Frequency:2.437 GHz (Channel 6)
>                     Quality=9/100  Signal level=9/100
>                     Encryption key:on
>                     ESSID:"Livebox-e706"
>                     Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
>                               9 Mb/s; 12 Mb/s; 18 Mb/s
>                     Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
>                     Mode:Master
>                     Extra:tsf=0000003ca58f4b17
>                     Extra: Last beacon: 556ms ago
>                     IE: Unknown: 000C4C697665626F782D65373036
>                     IE: Unknown: 010882848B960C121824
>                     IE: Unknown: 030106
>                     IE: IEEE 802.11i/WPA2 Version 1
>                         Group Cipher : TKIP
>                         Pairwise Ciphers (2) : CCMP TKIP
>                         Authentication Suites (1) : PSK
>                     IE: WPA Version 1
>                         Group Cipher : TKIP
>                         Pairwise Ciphers (2) : CCMP TKIP
>                         Authentication Suites (1) : PSK
>                     IE: Unknown: 2A0100
>                     IE: Unknown: 32043048606C
>                     IE: Unknown: 
> DD180050F2020101820003A4000027A4000042435E0062322F00
>                     IE: Unknown: 
> 2D1A4C101BFFFF000000000000000000000000000000000000000000
>                     IE: Unknown: 
> 3D1606001B00000000000000000000000000000000000000
>                     IE: Unknown: DD0900037F01010000FF7F
>                     IE: Unknown: DD0A00037F04010020000000
>                     IE: Unknown: 0706465220010D14
>                     IE: Unknown: 
> DD880050F204104A000110104400010210570001001041000100103B00010310470010C8CD724AE706C8CD724AE706724AE70610210005536167656D102300084C697665626F7832102400084C697665626F78321042000A4C4B31313038364450331054000800060050F20400011011000D4C697665626F78322D45373036100800020086103C000101
> 
> 
> But the connect itself fails. The key is OK, in fact is is the same key that I 
> use at the computer where I write this email. In find in the kernel log:
> 
> [20983.537071] wlan1: deauthenticating from 00:19:70:68:55:11 by local choice 
> (reason=3)
> [20983.738422] wlan1: direct probe to AP 00:19:70:68:55:11 (try 1)
> [20983.748230] wlan1: direct probe responded
> [20983.748253] wlan1: authenticate with AP 00:19:70:68:55:11 (try 1)
> [20983.750710] wlan1: authenticated
> [20983.750786] wlan1: associate with AP 00:19:70:68:55:11 (try 1)
> [20983.754175] wlan1: RX AssocResp from 00:19:70:68:55:11 (capab=0x431 
> status=0 aid=3)
> [20983.754189] wlan1: associated
> [20983.770735] wlan1: deauthenticating from 00:19:70:68:55:11 by local choice 
> (reason=3)
> [20983.973066] wlan1: deauthenticating from 00:19:70:68:55:11 by local choice 
> (reason=3)
> [20984.185337] wlan1: direct probe to AP 00:19:70:68:55:11 (try 1)
> [20984.190155] wlan1: direct probe responded
> [20984.190176] wlan1: authenticate with AP 00:19:70:68:55:11 (try 1)
> [20984.192681] wlan1: authenticated
> [20984.192752] wlan1: associate with AP 00:19:70:68:55:11 (try 1)
> [20984.197998] wlan1: RX AssocResp from 00:19:70:68:55:11 (capab=0x431 
> status=0 aid=3)
> [20984.198014] wlan1: associated
> [20984.211927] wlan1: deauthenticating from 00:19:70:68:55:11 by local choice 
> (reason=3)
> [20984.421052] wlan1: deauthenticating from 00:19:70:68:55:11 by local choice 
> (reason=3)
> .
> .
> .
> 21017.567154] wlan1: authenticated
> [21017.567221] wlan1: associate with AP 00:19:70:68:55:11 (try 1)
> [21017.570269] wlan1: RX AssocResp from 00:19:70:68:55:11 (capab=0x431 
> status=0 aid=3)
> [21017.570279] wlan1: associated
> [21017.571200] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
> [21017.588867] wlan1: deauthenticating from 00:19:70:68:55:11 by local choice 
> (reason=3)
> [21028.076103] eth1: no IPv6 routers present
> 
> 
> and in the wicd log
> 2011/08/25 16:33:48 :: Connecting to wireless network Livebox-e706
> 2011/08/25 16:33:48 :: attempting to set hostname with dhclient
> 2011/08/25 16:33:48 :: using dhcpcd or another supported client may work 
> better
> 2011/08/25 16:33:49 :: attempting to set hostname with dhclient
> 2011/08/25 16:33:49 :: using dhcpcd or another supported client may work 
> better
> 2011/08/25 16:33:49 :: Putting interface down
> 2011/08/25 16:33:49 :: Sending connection attempt result Failed
> 2011/08/25 16:33:49 :: Releasing DHCP leases...
> 2011/08/25 16:33:49 :: attempting to set hostname with dhclient
> 2011/08/25 16:33:49 :: using dhcpcd or another supported client may work 
> better
> 2011/08/25 16:33:49 :: Setting false IP...
> 2011/08/25 16:33:49 :: Stopping wpa_supplicant
> 2011/08/25 16:33:49 :: Flushing the routing table...
> 2011/08/25 16:33:49 :: Putting interface up...
> 2011/08/25 16:33:51 :: Generating psk...
> 2011/08/25 16:33:51 :: Attempting to authenticate...
> 2011/08/25 16:34:27 :: wpa_supplicant authentication may have failed.
> 2011/08/25 16:34:27 :: connect result is
> 2011/08/25 16:34:27 :: exiting connection thread
> 2011/08/25 16:34:28 :: Sending connection attempt result bad_pass
> 2011/08/25 16:34:28 :: attempting to set hostname with dhclient
> 2011/08/25 16:34:28 :: using dhcpcd or another supported client may work 
> better
> 2011/08/25 16:34:28 :: attempting to set hostname with dhclient
> 2011/08/25 16:34:28 :: using dhcpcd or another supported client may work 
> better
> 
> 
> Any hint? I do not belief the the dhclient is the problem, becaus the some 
> combination (kubuntu 10.04, wicd, dhclient) work at my other notebook without 
> problem.
> 
> ii  dhcp3-client    3.1.3-2ubuntu3.2                       DHCP client
> ii  dhcp3-common   3.1.3-2ubuntu3.2        common files used by all the dhcp3* 
> packages
> ii  wpasupplicant     0.6.9-3ubuntu3         client support for WPA and WPA2 
> (IEEE 802.11
> 
> Any hint? Thanks!
> 

this problem is one of those elusive nasty ones. there's no one reason
why it would happen.
as you suggested, yes, DHCP can very well be the problem sometimes, if
the network fails to receive an IP address from the access point, NM
disconnects it. you can try setting up manual IPs, and connect. if it
stays connected, then try out the network. many times, DHCP wouldnt be
working not due to a configuration error, but rather because the
interface isnt receiving packets due to a driver problem.

some people report that wpa_supplicant is the culprit, i suggest you try
this command in a terminal:

ps -Af | grep wpa_supplicant

and see if more than one instance of this program are running. if just
one, keep it, if more, kill them all, then start the program again by:

sudo /sbin/wpa_supplicant -u -s

let's just test these 2 theories for now, and we'll see what happens :)

-- 
Waleed K. Hamra
Manager of Hamra Information Systems

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/kubuntu-users/attachments/20110827/907146d5/attachment.sig>


More information about the kubuntu-users mailing list