Date: Wed, 3 Oct 2007 08:26:12 -0500 From: Craig Boston <cb@severious.net> To: Andrew Thompson <thompsa@FreeBSD.org> Cc: FreeBSD Current <current@FreeBSD.org> Subject: Re: ipw status (was: wireless) Message-ID: <20071003132612.GA39864@nowhere> In-Reply-To: <20071001203030.GB16919@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> <46A84F36.8080309@petri.cc> <20071001203030.GB16919@heff.fud.org.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 02, 2007 at 09:30:30AM +1300, Andrew Thompson wrote: > Thanks for the report, attached is an updated patch for ipw(4) that > seems to work very well. Please give it a spin. Managed to get this compiled yesterday and had a chance to do some testing last night. It does seem to be a bit better then the previous patch -- the interface comes up and associates automatically on boot now. Previously it would be up and scanning but never find anything until I restarted wpa_supplicant. It does still randomly stop working after a couple hours though. It will still show "up" and associated with the AP, but no packets get through until I down/up the interface. Sometimes have to cycle it twice. It may last a little longer than the previous patch before it dies, but I'm not 100% sure. Is that a known issue or should I start enabling debug flags? Thanks for all your work on this driver. Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071003132612.GA39864>