Date: Tue, 26 Sep 2006 00:46:14 +0200 From: =?ISO-8859-1?Q?Sten_Daniel_S=F8rsdal?= <lists@wm-access.no> To: Sam Leffler <sam@errno.com> Cc: freebsd-stable@freebsd.org Subject: Re: ath0 weak connectivity Message-ID: <45185C36.5080101@wm-access.no> In-Reply-To: <4515DA06.1070402@errno.com> References: <20060918083139.GA59966@tetsuo.karasik.eu.org> <450ED7AA.6090801@errno.com> <84wt7ubjwy.fsf@tetsuo.karasik.eu.org> <4515DA06.1070402@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sam Leffler wrote: > I've lost context about your problem but it appears you're having > trouble associating with "trejago" sometimes. The failed scan shows > that your rssi was only 6 when you were having problems which is a very= > marginal signal so I'm not at all surprised you're having trouble. > You've got strong signal ap's on overlapping channels (5 and 7) which > are likely drowning the signal on your ap. I don't see anything the > driver could do differently; this seems more an issue of your > environment being very busy. I vaguely recall you were comparing the > operation of the freebsd to windows. If so then perhaps the windows > driver was doing better because it switched to XR mode and operating in= > XR mode you were able to punch through the noise to get to the ap. > freebsd does not support XR mode. >=20 > Sam >=20 Are there any plans to support this? What about fastframes/bursting? 10Mhz, 5Mhz channels? WDS? Virtual AP? Is there any place where i can read about this? Apologies if any of these are already in the works. --=20 Sten Daniel S=F8rsdal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45185C36.5080101>