From owner-freebsd-wireless@FreeBSD.ORG Tue Jul 31 03:03:01 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4B55B106566C for ; Tue, 31 Jul 2012 03:03:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id F2FE98FC12 for ; Tue, 31 Jul 2012 03:03:00 +0000 (UTC) Received: by yhfs35 with SMTP id s35so6500500yhf.13 for ; Mon, 30 Jul 2012 20:03:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=xlh2gxOmXN2/EARkgmSjHvZE99DWGrnXpmn773vy7pY=; b=Oy88j+agqsiWsI0OvxjnMfRtreQOmytb5uxZQrBoi5fkAyaTfinHYNh+wYW+Sk+8Ok qpK9GZis6GUwrwJcNKUFB+qc9CkfvVIHsihawMJ9guLxOzdibXrnlB/ZhRQavE6DaxDy PAhL9Ak8QownRzP8pOLbQaEDRKCZ8xqjo3DJXs+TVk66oh2xB/BzvPoALnRbF8h80OsN ON8pfgUqgF+iLkxZPyrwverIT3BmlVZT6RdfHfBc/pOgeRI6JZZawvy8zrPYZiEfCCzY 1ZFef20NaKXmpAplXH+OAhTGouLPJ+8SiQ6XKyuEaWAOLhSHaCWYv6ppXeRD9ejWOY5q mdzg== MIME-Version: 1.0 Received: by 10.66.73.70 with SMTP id j6mr29138759pav.5.1343703780010; Mon, 30 Jul 2012 20:03:00 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.66.136 with HTTP; Mon, 30 Jul 2012 20:02:59 -0700 (PDT) In-Reply-To: <201207311033260047670@gmail.com> References: <201207300139326668335@gmail.com> <201207310032346632212@gmail.com> <201207311033260047670@gmail.com> Date: Mon, 30 Jul 2012 20:02:59 -0700 X-Google-Sender-Auth: hgGJeLRKuiUe64TXagP7_rkfO_U Message-ID: From: Adrian Chadd To: =?UTF-8?B?5LmU5qWaL0hvbmVzdFFpYW8=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless Subject: Re: Re: iwn0/wlan0 scan WPA2-PSK/AES as WEP on freebsd9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 31 Jul 2012 03:03:01 -0000 RIght. It's quite possible that there's something about that beacon frame format that's tripping up the beacon parsing code in net80211. can you please take a snapshot using monitor mode? tcpdump -ni wlan0 -y IEEE802_11_RADIO -s0 -l -v -w pcap.out Run that whilst you're trying to associate, let's see what happens. adrian On 30 July 2012 19:33, =E4=B9=94=E6=A5=9A/HonestQiao = wrote: > 2012-07-31 03:33, Adrian Chadd wrote: >>That SSID looks very odd. And look at the output of wpa_supplicant - >>it isn't finding any WPA enabled APs. >> >>And do an "ifconfig -v wlan0 list scan" at home, to get the entire >>SSID and decoded beacon contents from the scan cache. >> >> >> >>Adrian > > Ok, I 'll test it at home. Now, My local time is 10:32 AM. > > I also think the SSID is very odd. But other devices can get the right SS= ID. > > HonestQiao