From owner-freebsd-wireless@FreeBSD.ORG  Mon Apr 25 15:43:34 2011
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 256AC1065670
	for <wireless@freebsd.org>; Mon, 25 Apr 2011 15:43:34 +0000 (UTC)
	(envelope-from lists@eitanadler.com)
Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com
	[209.85.220.182])
	by mx1.freebsd.org (Postfix) with ESMTP id D41AC8FC12
	for <wireless@freebsd.org>; Mon, 25 Apr 2011 15:43:33 +0000 (UTC)
Received: by vxc34 with SMTP id 34so2563561vxc.13
	for <wireless@freebsd.org>; Mon, 25 Apr 2011 08:43:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=eitanadler.com; s=0xdeadbeef;
	h=domainkey-signature:mime-version:from:date:message-id:subject:to
	:content-type; bh=FV7Jx2ZODfnAMrbO8s4UoKD/9rcv9CgUS0/qSTHQpwM=;
	b=Nus3C0RHqXka1Oj7rlOZydQoAH6s9duauj/B0GL1OIHqVRgj/PuV6SF+TUh4+q7EmD
	NnbCD5EE6NqgBYdG95tcSmQi8eMdN0GMBOvDD5wp4Sc6M5d8qM86TP6GBodeYmwsWVcb
	0rseusIsi39o692DY4rd3i69PdyxxZn74aAMU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=eitanadler.com; s=0xdeadbeef;
	h=mime-version:from:date:message-id:subject:to:content-type;
	b=R5Bare1GWXTUblHQRrDtEvE/63Vh2DDbOOqMiXE9+Z5PsFURnPXfnR3IPEPyrZVHsp
	TLHCWEfFgVVQ0OZjPIqgjRW7gWVBJ/cLIN4rvmF6byUas3cRXcGAapCD0NwXhKA3Sy4X
	tKBp/vD/kS/tbnzIKwWNDytWlSmzTU9sU4qEo=
Received: by 10.52.0.130 with SMTP id 2mr6561290vde.180.1303744770068; Mon, 25
	Apr 2011 08:19:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.181.202 with HTTP; Mon, 25 Apr 2011 08:19:00 -0700 (PDT)
From: Eitan Adler <lists@eitanadler.com>
Date: Mon, 25 Apr 2011 11:19:00 -0400
Message-ID: <BANLkTimnpsS_ZqiccV9b9tCS6TZyeO+9DA@mail.gmail.com>
To: wireless@freebsd.org
Content-Type: text/plain; charset=UTF-8
Cc: 
Subject: Issues with bwn wireless
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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Apr 2011 15:43:34 -0000

On the same computer I have here:
http://forum.nginx.org/read.php?23,138126,138310,template=head%3F%3F
I've been having similar issues recently and I'm hoping to finally
resolve them. The only change from then is that I am now using
8-STABLE (r219789)

1) For some reason setting the ssid via ifconfig and setting wlan0 to
"up" doesn't do anything. I need to use wpa_supplicant even for an
OPEN network

2) I start wpa_supplicant with
network = {
ssid="fubar"
key_mgmt=NONE
}
and then run dhlient wlan0.
After this it seems that like I am associated and I'm able to ping
"google.com" for some number of packets and then it loses packets.
The routes, /etc/resolv.conf, and ip address all seem in order - even
after it stops responding.
ifconfig wlan0 still says "status: associated" even though I am unable
to ping anything or access the internet. In _some_ cases "dig" still
works.

3) Sometimes I see the channel cycling somewhat randomly during the
"associated but not working" time.

4) ifconfig wlan0 scan never shows anything but ifconfig wlan0 list scan does.

Any pointers or ideas to resolve these issues would be great!


-- 
Eitan Adler