From owner-freebsd-wireless@FreeBSD.ORG Mon Jan 6 16:00:56 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8347F21F for ; Mon, 6 Jan 2014 16:00:56 +0000 (UTC) Received: from mail-qe0-x230.google.com (mail-qe0-x230.google.com [IPv6:2607:f8b0:400d:c02::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 38B641F5E for ; Mon, 6 Jan 2014 16:00:56 +0000 (UTC) Received: by mail-qe0-f48.google.com with SMTP id gc15so18602096qeb.7 for ; Mon, 06 Jan 2014 08:00:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=blbg2MkNJLs3wmIiV04Kj46d4mqXi2ByWgx8r4O35/0=; b=ty2LCVUAjZh4SvBuXIu66vhmrOIVQwqL/hdMBmmfp0bvc9EairGynvwjP/vlX+2YqX ceYBSFHzPPU6rhz5hJXL9xnUVWWzyOafLhP+cY6SyiBRy+2qZ4yDT09mmbipPWYEAP6W W8WqxtNeEiw+0PtAYabZ9aqTeUPbfSsek8jrNu+33Gb/RxKgcifewCEWGt1VWEM8IBdO 5dN5KV68WpRm6EufX/9ibtpJpy2qvfHkr44Xt1jvgZz/6Z5f+sL4vaPD2vygm1ymhct5 7DAP1GhAH7Or3fXcVgqjxpOO8+GdmruqBMtA6zboz2dq+cDphuI/ZlRZDc3Ep1DDWAam Z2pw== MIME-Version: 1.0 X-Received: by 10.224.13.203 with SMTP id d11mr5035691qaa.26.1389024055448; Mon, 06 Jan 2014 08:00:55 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.52.8 with HTTP; Mon, 6 Jan 2014 08:00:55 -0800 (PST) In-Reply-To: <52CAC907.8020507@shurik.kiev.ua> References: <52CAB6F2.3010707@shurik.kiev.ua> <52CABD82.2070106@shurik.kiev.ua> <52CAC368.3000105@shurik.kiev.ua> <52CAC6B6.8090007@shurik.kiev.ua> <52CAC907.8020507@shurik.kiev.ua> Date: Mon, 6 Jan 2014 08:00:55 -0800 X-Google-Sender-Auth: LELtVQuxqzUu5sU7IH_v0Vt17PM Message-ID: Subject: Re: Problem connecting to AP From: Adrian Chadd To: Alexandr Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jan 2014 16:00:56 -0000 tcpdump -ni wlan0 -y IEEE802_11_RADIO -l -v -w pcap.out -a On 6 January 2014 07:17, Alexandr wrote: > It's TP-Link TL-MR3420 rev.1. > > How can I capture a dump? AP has no such tools and it logs is clean. Can > I do it from my bsd? > > 06.01.2014 17:08, Adrian Chadd =D0=C9=DB=C5=D4: >> Which AP is it? >> >> I kinda want to see a packet dump of the negotiation exchange. I'm >> worried that your AP is deciding to kick you off because you don't >> meet some minimum rate selection or something. >> >> -a >> >> On 6 January 2014 07:07, Alexandr wrote: >>> Yes, just now it works in 11n-only. But I tried switch it to bgn-mixed, >>> g-only, n-only - no luck. >>> >>> /var/log/dmesg.today: >>> >>> wlan0: [54:e6:fc:e4:48:c4] recv auth frame with algorithm 0 seq 2 >>> wlan0: link state changed to UP >>> wlan0: [54:e6:fc:e4:48:c4] recv deauthenticate (reason 2) >>> wlan0: link state changed to DOWN >>> >>> /var/log/messages: >>> >>> Jan 6 17:05:03 thinkpad wpa_supplicant[27113]: wlan0: Trying to >>> associate with 54:e6:fc:e4:48:c4 (SSID=3D'door' freq=3D2412 MHz) >>> Jan 6 17:05:03 thinkpad wpa_supplicant[27113]: wlan0: Associated with >>> 54:e6:fc:e4:48:c4 >>> Jan 6 17:05:06 thinkpad wpa_supplicant[27113]: wlan0: >>> CTRL-EVENT-DISCONNECTED bssid=3D54:e6:fc:e4:48:c4 reason=3D0 >>> Jan 6 17:05:17 thinkpad wpa_supplicant[27113]: wlan0: Trying to >>> associate with 54:e6:fc:e4:48:c4 (SSID=3D'door' freq=3D2412 MHz) >>> Jan 6 17:05:17 thinkpad wpa_supplicant[27113]: wlan0: Associated with >>> 54:e6:fc:e4:48:c4 >>> Jan 6 17:05:20 thinkpad wpa_supplicant[27113]: wlan0: >>> CTRL-EVENT-DISCONNECTED bssid=3D54:e6:fc:e4:48:c4 reason=3D0 >>> >>> 06.01.2014 16:56, Adrian Chadd =D0=C9=DB=C5=D4: >>>> .. and is the AP locked down to 11n only or something? >>>> >>>> >>>> -a >>>> >>>> On 6 January 2014 06:55, Adrian Chadd wrote: >>>>> Whta's logged in dmesg? >>>>> >>>>> >>>>> -a >>>>> >>>>> On 6 January 2014 06:53, Alexandr wrote: >>>>>> =EF=CB, I changed key to "secretsecretsecret", the same error - WPA:= 4-Way >>>>>> Handshake failed - pre-shared key may be incorrect. >>>>>> >>>>>> <3>Trying to associate with 54:e6:fc:e4:48:c4 (SSID=3D'door' freq=3D= 2412 MHz) >>>>>> <3>Associated with 54:e6:fc:e4:48:c4 >>>>>> <3>CTRL-EVENT-DISCONNECTED bssid=3D54:e6:fc:e4:48:c4 reason=3D0 >>>>>> <3>WPA: 4-Way Handshake failed - pre-shared key may be incorrect >>>>>> <3>CTRL-EVENT-SSID-TEMP-DISABLED id=3D0 ssid=3D"door" auth_failures= =3D8 >>>>>> duration=3D30 >>>>>> >>>>>> But it successfully connects to my android phone: >>>>>> >>>>>> wlan0: flags=3D8843 metric 0= mtu 1500 >>>>>> ether 68:5d:43:92:3a:88 >>>>>> inet 192.168.1.227 netmask 0xffffff00 broadcast 192.168.1.25= 5 >>>>>> nd6 options=3D29 >>>>>> media: IEEE 802.11 Wireless Ethernet MCS mode 11ng >>>>>> status: associated >>>>>> ssid htc channel 6 (2437 MHz 11g ht/20) bssid 84:7a:88:c9:25= :ce >>>>>> country US authmode WPA2/802.11i privacy ON deftxkey UNDEF >>>>>> AES-CCM 2:128-bit txpower 15 bmiss 10 scanvalid 60 bgscan >>>>>> bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 64 prot= mode CTS >>>>>> ampdulimit 16k -amsdutx amsdurx shortgi wme roaming MANUAL >>>>>> >>>>>> >>>>>> May be it AP-related problem? But why other devices works (laptop wi= th >>>>>> opensuse and different android devices) >>>>>> >>>>>> 06.01.2014 16:43, Adrian Chadd =D0=C9=DB=C5=D4: >>>>>>> You still need a longer password, psk isn't WPA long. Try secretsec= retsecret. >>>>>>> >>>>>>> >>>>>>> -a >>>>>>> >>>>>>> On 6 January 2014 06:28, Alexandr wrote: >>>>>>>> I simply changed key in this listing to "secret". Yes, I tried a v= ery >>>>>>>> simple configuration, no luck: >>>>>>>> >>>>>>>> network=3D{ >>>>>>>> ssid=3D"door" >>>>>>>> psk=3D"secret" >>>>>>>> } >>>>>>>> >>>>>>>> >>>>>>>> 06.01.2014 16:24, Adrian Chadd =D0=C9=DB=C5=D4: >>>>>>>>> The passphrase 'secret' is too short for WPA. >>>>>>>>> >>>>>>>>> I gather it's not _that_, but is it long enough to meet WPA reuir= ements? >>>>>>>>> >>>>>>>>> Have you tried removing the proto=3D and bssid lines? You don't s= trictly >>>>>>>>> need them. >>>>>>>>> >>>>>>>>> Thanks! >>>>>>>>> >>>>>>>>> -a >>>>>>>>> >>>>>>>>> >>>>>>>>> On 6 January 2014 06:00, Alexandr wrote: >>>>>>>>>> Hello, >>>>>>>>>> >>>>>>>>>> I recently upgraded system on my laptop to current with a hope t= o get my >>>>>>>>>> wireless card working. Now it successfully recognized by kernel: >>>>>>>>>> >>>>>>>>>> iwn0: mem 0xf2d00000-0xf2d01fff= irq 17 >>>>>>>>>> at device 0.0 on pci3 >>>>>>>>>> >>>>>>>>>> Unfortunately, I can't connect to my home access point: >>>>>>>>>> >>>>>>>>>> wpa_supplicant[519]: wlan0: CTRL-EVENT-DISCONNECTED >>>>>>>>>> bssid=3D54:e6:fc:e4:48:c4 reason=3D0 >>>>>>>>>> wpa_supplicant[519]: wlan0: WPA: 4-Way Handshake failed - pre-sh= ared key >>>>>>>>>> may be incorrect >>>>>>>>>> wpa_supplicant[519]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=3D0 >>>>>>>>>> ssid=3D"door" auth_failures=3D10 duration=3D30 >>>>>>>>>> >>>>>>>>>> I tried different security settings (WPA-WPA2 + AES-TKIP), wirel= ess >>>>>>>>>> modes, radio channels on my access point, the same error. >>>>>>>>>> >>>>>>>>>> # ifconfig wlan0 >>>>>>>>>> wlan0: flags=3D8843 metr= ic 0 mtu 1500 >>>>>>>>>> ether 68:5d:43:92:3a:88 >>>>>>>>>> nd6 options=3D29 >>>>>>>>>> media: IEEE 802.11 Wireless Ethernet autoselect (autosel= ect) >>>>>>>>>> status: no carrier >>>>>>>>>> ssid door channel 1 (2412 MHz 11g ht/40+) >>>>>>>>>> country US authmode WPA2/802.11i privacy ON deftxkey UND= EF >>>>>>>>>> txpower 13 >>>>>>>>>> bmiss 10 scanvalid 60 bgscan bgscanintvl 300 bgscanidle = 250 >>>>>>>>>> roam:rssi 7 roam:rate 64 protmode CTS ampdulimit 8k -ams= dutx amsdurx >>>>>>>>>> shortgi wme roaming MANUAL >>>>>>>>>> >>>>>>>>>> /etc/wpa_supplicant.conf: >>>>>>>>>> >>>>>>>>>> ctrl_interface=3D/var/run/wpa_supplicant >>>>>>>>>> ctrl_interface_group=3Dwheel >>>>>>>>>> eapol_version=3D2 >>>>>>>>>> >>>>>>>>>> network=3D{ >>>>>>>>>> ssid=3D"door" >>>>>>>>>> bssid=3D54:e6:fc:e4:48:c4 >>>>>>>>>> key_mgmt=3DWPA-PSK >>>>>>>>>> proto=3DWPA RSN >>>>>>>>>> psk=3D"secret" >>>>>>>>>> } >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Other home devices connets to AP without problems. Can you point= me how >>>>>>>>>> I can debug it? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> freebsd-wireless@freebsd.org mailing list >>>>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>>>>>>>>> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@f= reebsd.org" >