How to force client to associate another AP
williamt at arescom.com
Wed Aug 13 13:54:24 EDT 2003
----- Original Message -----
From: "Jun Sun" <jsun at junsun.net>
To: "Timo Vanhatupa" <timo.vanhatupa at tut.fi>
Cc: "william" <williamt at arescom.com>; <hostap at shmoo.com>
Sent: Wednesday, August 13, 2003 7:02 AM
Subject: Re: How to force client to associate another AP
> On Wed, Aug 13, 2003 at 09:55:47AM +0300, Timo Vanhatupa wrote:
> > Hi
> > I have done it using access control list and it seems to work.
> > First I set deny policy for access control list and then deny client's
> > access and kick it out.
> > iwpriv wlan0 maccmd 2
> > iwpriv wlan0 addmac <mac addr>
> > iwpriv wlan0 kickmac <mac addr>
> Very interesting approach.
> > At least my clients seem to find their way to other APs. I would like to
> > know if this does not work
> > with all clients.
I did this, but the client still tried to associated with my AP.
I guess the client will try to associate with the AP with highest singal
quality. Am I right?
The client still try to associate with my AP even though I already kick it
> > Still I haven't figured out how to know which access points can be heard
> > by the client.
> > Does anyone have ideas how an AP could scan/listen clients that are not
> > associated with it and are on the different channel?
> > If this information would be available it would be easy to force clients
> > to selected APs.
> My understanding is that people are working on this as part of
> inter-AP protocol.
More information about the HostAP