Re: Disconnect and Reconnects using Hostap

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" <[email protected]> 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 [email protected]
>with "unsubscribe freebsd-mobile" in the body of the message




To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-mobile" in the body of the message