Date: Wed, 26 Jul 2006 11:07:36 -0700 From: Sam Leffler <sam@errno.com> To: freebsd-stable@freebsd.org Subject: Re: "scan stuck" with if_iwi(4) Message-ID: <44C7AF68.3090109@errno.com> In-Reply-To: <20060726163017.GB5856@osgiliath.opasia.dk> References: <20060720224632.GB31459@osgiliath.brixandersen.dk> <44C00B40.2010901@errno.com> <20060726144058.GD3077@osgiliath.opasia.dk> <44C793DB.5090900@errno.com> <20060726163017.GB5856@osgiliath.opasia.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Henrik Brix Andersen wrote: > On Wed, Jul 26, 2006 at 09:10:03AM -0700, Sam Leffler wrote: >> Thanks for your help but understand this is not necessarily a solution; >> just the addition of a knob. > > I know. Sure, it was for others. > >> The linux driver already used 7 consecutive beacon misses to trigger >> roaming so I'm not sure why 10 is an improvement but given that >> adding 300ms (typical) lag makes you happy I wasn't going to argue >> :) > > Actually, it seems the linux driver uses a threshold of 8 missed > beacons for roaming and a threshold of 24 for disassociation. Which version are you looking at? The numbers in iwi are from the code in linux-2.6.17; maybe it's been changed again in the code on sourceforge? The one thing the linux driver does differently is scan for a new ap _before_ roaming which the current net80211 code cannot do. Unfortunately the code to do that has been sitting outside the tree for a long time and it's unclear if it'll ever come in... > > But you're correct - this only solves the issue of being disassociated > every 3 minutes; it doesn't solve the problem behind "scan stuck", but > this problem is not present here anymore since the station is not > disassociated all the time. > > I'll try to address the scan stuck problem when I find some more time. Thank you. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44C7AF68.3090109>