From owner-freebsd-current@FreeBSD.ORG Sat May 30 18:40:43 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 054E41065670 for ; Sat, 30 May 2009 18:40:43 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from mail-ew0-f212.google.com (mail-ew0-f212.google.com [209.85.219.212]) by mx1.freebsd.org (Postfix) with ESMTP id 8902A8FC0C for ; Sat, 30 May 2009 18:40:42 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: by ewy8 with SMTP id 8so3493032ewy.43 for ; Sat, 30 May 2009 11:40:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=t3FnWAhBkXlPjHWTaUMQoP71SbeS9taatnqF075YItQ=; b=UlS77MiEUQVfaGhtKnpGmifHirMMXo/Gw5z645H/mLrlTdPD/aQSHjMGSRDn1U37kX BewHFGZdHt9NQHsV64UKws7fBsw97VPzwErLBUcibF4vO+S9b6+W4jf0pTCKrRJrHxF7 mhOyc9W9bbaLnOIVykYP1Dc5Mnq1WOUzajsZE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=EO2cU4IGyv1bGQ3NhpfHdWzq2bklwidkIzdYHZzORRbVrJY50QlsDaiJL+RZKwq0a7 /6nxMVHLqBs4vbG77NHJH5rZIGMM8IX9g4j/cDYGQ1SmrTbBvgeCJf1/BrMuDMVDYQZ+ q/Vx7uP18pv43MVxjWKRhLQ2TIiP0Ww0vQ+rA= MIME-Version: 1.0 Received: by 10.216.29.80 with SMTP id h58mr1296663wea.159.1243708841585; Sat, 30 May 2009 11:40:41 -0700 (PDT) In-Reply-To: <20090521204752.43aa3adc@fabiankeil.de> References: <4A11A08B.6090309@errno.com> <20090521170637.73619418@fabiankeil.de> <20090521204752.43aa3adc@fabiankeil.de> Date: Sat, 30 May 2009 13:40:41 -0500 Message-ID: <11167f520905301140q41799907ob14ce5edc5571b7b@mail.gmail.com> From: "Sam Fourman Jr." To: Fabian Keil Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: 802.11 monitor mode changes coming X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 May 2009 18:40:43 -0000 On Thu, May 21, 2009 at 1:47 PM, Fabian Keil wrote: > Fabian Keil wrote: > >> With r192468 I can no longer get iwi to associate to the AP. >> "ifconfig wlan0 list scan" shows the AP, but S:N is listed >> as -95:-95 (IIRC). > > Fixed in r192541. > No I don't think it is Fixed, I have a kernel built today 5-30-2009 and I have the same trouble with not being able to associate to AP's that I could before. Except it sounds WEIRD but, certian AP's I can associate to, Eg a OpenBSD 4.5 AP and a ubiquiti NS2 work fine every time, but certain linksys wrt54G's I cant associate with, and I have a Enginius device that I cant associate with. I also noticed that I cant see the Beacons from these AP's with tcpdump -i wlan0 -y IEEE802_11_RADIO I have tried this with ath, uath, urtw a Kernel from May 12th fixes all these issues Just a Observation I am willing to help but I do not know what exactly to do. Sam Fourman Jr.