From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 23 21:02:29 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 4FF08601 for ; Sat, 23 Aug 2014 21:02:29 +0000 (UTC) Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DF913D96 for ; Sat, 23 Aug 2014 21:02:28 +0000 (UTC) Received: by mail-qa0-f45.google.com with SMTP id cm18so10789118qab.4 for ; Sat, 23 Aug 2014 14:02:28 -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:message-id:subject :from:to:cc:content-type; bh=kypnNu434xMdjfevzt9fWDrGjZ2BTp5bnC96G9RLtYg=; b=Lrl4U3LGbr5+V+K91V2DJIRHpHwcMBz68qsg2JDzy+iLBtSllj7MqOvVaMVOvWTqS6 eL7Vibsk3jRD8LvTb6jf5AhKSTA66IhzM5pGdH/6NmUeqwZLUTEgMidSm/j4mq4lFWLB ar8AKK7HF6ALnF7OoE1KS3cZHTHbFBj5h/T8T4JmVgHKzodX00YKzgoA1dIoNTOCmdDN XjT5/cXwSnjmQo4OFv7EsAI58ZpQ1gpYGohSyI0MAjq6L+Vm6xV2mX9VRks+dy9FUXPh dQamtnQMbGK9ZH0Kk1ST5pxRPnCbotenwpFxb4SPzcAr5GxuH22pi0XG0Rs2Ay87tlfD domw== MIME-Version: 1.0 X-Received: by 10.224.36.4 with SMTP id r4mr11495194qad.69.1408827748178; Sat, 23 Aug 2014 14:02:28 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Sat, 23 Aug 2014 14:02:28 -0700 (PDT) In-Reply-To: <53F9009F.2020603@telenet.be> References: <201408231238.s7NCc8ME057766@fire.js.berklix.net> <53F8F086.1070207@telenet.be> <53F8F605.80006@telenet.be> <53F9009F.2020603@telenet.be> Date: Sat, 23 Aug 2014 14:02:28 -0700 X-Google-Sender-Auth: R5RSDocCkP4Ai1ihygGzZYpdZY8 Message-ID: Subject: Re: WPI (Intel wireless 3945ABG) strange behaviour From: Adrian Chadd To: Chris Van Steenlandt Content-Type: text/plain; charset=UTF-8 Cc: "Julian H. Stacey" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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: Sat, 23 Aug 2014 21:02:29 -0000 Yeah, that's the same problem at iwn - the firmware rejects any frames being transmitted to 5ghz passive channels until a beacon is received. It's likely some buffering in net80211 and/or the driver(s) is required. It's not breaking regulatory - the NIC already scanned the channel and heard a beacon. But then the firmware is reset to associate to the channel (rather than scan) and it "loses" knowledge that the channel is fine to transmit on. So net80211 associating with one frame which is instantly rejected by the firmware. Something needs to buffer that and other frames until the firmware sees a beacon - then if it retries the frame(s), it'll successfully be transmitted. I've known about the problem for a while. I've just been too busy / distracted to sit down and fix it. It's not a conceptually difficult thing to fix - someone just has to do it. :P -a On 23 August 2014 13:59, Chris Van Steenlandt wrote: > Adrian, > > - ifconfig step (creation of pseudo device) completed successfully > - wpa_supplicant gives the following type of output (I can't paste it here, > but I'll describe the structure of the output) : > > 1st message : Initialization successfull > > Then the following blocks of messages (they alternate or repeat) > Block 1 : > > Trying to associate with (SSID='myssid' freq=5180 Mhz) > wlan0 : Authentication with timed out. > wlan0 : CTRL_EVENT_DISCONNECTED bssid = reason=3 > locally_generated=1 > ioctl[SIOCS80211, op=20, val=0, arg_len=7] : Can't assign requested adress > > Block 2 : > Trying to associate with (SSID='myssid' freq=2412 Mhz) > wlan0 : Associated with > wlan0 : WPA: Key negotiation completed with [PTK=CMP > GTK=TKIP] > wlan0 : CTRL_EVENT_CONNECTED - Connection to completed [id=0 > id_str=] > > > Block 2 is sometines followed by : > wlan0 : CTRL_EVENT_DISCONNECTED bssid = reason=0 > and then followed by block 1 > > For as far as I understand, the driver switches between the 2.4 GHz and 5 > Ghz band of my wireless network. Indeed my wifi router is configured to > support both bands but apparently my wifi driver can only handle the 2.4Ghz > one. > > > On 23-08-14 22:19, Adrian Chadd wrote: > > Ok. > > Just try it manually - > > * comment out stuff from /etc/rc.conf and reboot > * ifconfig wlan0 create wlandev wpi0 -bgscan > * wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf & > * ifconfig wlan0 list scan - you haven't pasted that here, so we have > no idea what APs it is seeing > > then see. > > If you compiled in IEEE80211_DEBUG in your kernel config, then > 'wlandebug +scan' and see what is spat out to the kernel config. > >