Date: Sun, 03 Nov 2002 18:06:27 -0800 From: "Greg Smith" <freebsd_mail@myrealbox.com> To: freebsd-mobile@FreeBSD.ORG Subject: Re: Disconnect and Reconnects using Hostap Message-ID: <200211031806270669.9CCCC342@smtp.myrealbox.com> In-Reply-To: <20021103.160046.34602778.imp@bsdimp.com> References: <001a01c2831f$2ae87f20$c20aa8c0@lfarr> <20021103.160046.34602778.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Warner, I have a Cisco 340 AP set up for my neighborhood to use. It seems to let clients stay associated as long as they are within range, even if idle. It has never blown up due to too many associations, since it seems to drop clients after they go out of range. And surely it has less RAM than most of the machines running hostap. I'm no wireless rocket scientist, but I thought that was the intention of 802.11b - that chit-chat between AP and client would confirm that the client was still nearby. Why doesn't hostap do that? It would seem that forcing clients to reconnect might also defeat some of the power saving benefits of infrastructure (non-adhoc) networks. Greg -----Original Message----- >In message: <001a01c2831f$2ae87f20$c20aa8c0@lfarr> > "Lawrence Farr" <freebsd-net@epcdirect.co.uk> writes: >: That works flawlessly, until a connected machine is idle network >: wise for a few minutes. The client machine disconnects and then >: immediately reconnects to the hostap box. Same machines don't do >: this on a "real" access point. Any ideas anyone? > >That's how hostap is implemented now. After you've been idle for a >while, you are kicked off to avoid tables in the kernel growning w/o >bound. > >Warner > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-mobile" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211031806270669.9CCCC342>