Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 23 Jul 2007 21:42:43 -0500
From:      Craig Boston <craig@xfoil.gank.org>
To:        Andrew Thompson <thompsa@FreeBSD.org>
Cc:        FreeBSD Current <current@FreeBSD.org>
Subject:   Re: wireless
Message-ID:  <20070724024242.GA69061@nowhere>
In-Reply-To: <20070723114821.GA6575@heff.fud.org.nz>
References:  <20070619011908.GA53748@heff.fud.org.nz> <20070620042023.GA17424@nowhere> <4678B1E4.7080909@errno.com> <467ED084.4000002@petri.cc> <46A484CA.8030805@petri.cc> <20070723114821.GA6575@heff.fud.org.nz>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jul 23, 2007 at 11:48:21PM +1200, Andrew Thompson wrote:
> You can test this WIP.

Hi,

This patch definitely is a big step in the right direction.

The first time I booted with the patch, there were so many debug
messages spamming the console it made the machine completely unusable
(VESA raster console couldn't keep up, heh).

After setting debug.ipw=0 things seem to be working much better.  I can
manually associate with an open AP just fine.  Don't have any in range
with WEP to try at the moment.

The big news however, which I've been holding my breath about since
skimming the patch this morning but didn't want to be too hopeful until
I actually tried it, is WPA (TKIP) works!  That's something that ipw
hasn't supported at all until now, so I'm quite excited about it.

The first time when I ran wpa_supplicant by hand it seemed to work for a
minute, but lost connectivity while dhclient was requesting a lease.  It
worked long enough to get a NAK response for an old address, but never
saw any response to discover requests after that.  Manually setting an
address didn't help either.  ifconfig still showed Associated but no
packets were being received.  There was an "ipw0: scan suck" message on
the console right about this time but nothing else to indicate a
problem.

After rebooting and letting it happen automatically with the rc scripts
it seems to be stable now.  I'm not 100% sure how often TKIP changes the
key, but I'm certain this has been up and running long enough for it to
have rotate a few times at least.

Will have to do some more testing to see if the stuck scan was a fluke
or if I can reproduce it.

Great work!

Craig



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070724024242.GA69061>