[Madwifi-devel] Fwd: Re: Association Table ???

[Nazeer K. <Naz...@ni...>]

Hi,

Let me explain what i want to to. Below is a rought location of Access
points and station.

 ___                                         ___
(AP1)                                       (AP2)
                         ___
                        (STA)

Station is in the range of both APs. I want that both APs forward the
frames for station, no matter to which AP the station is associated. The
downlink traffic will come through one of the Access points depending on
the signal strenght measured by APs. APs are just dump and the decisions
are taken at a central point to which both APs are connected.

"The main idea is that there will be a pool of APs and all the APs will
forward traffic for all stations, no matter to which AP the station is
associated. The central point will discard the extra copy. And finally
downlink traffic will go throught the best LINK."

I thought of the idea to make everything similar (MAC, BSSID, Channel) for
both APs, but station just associates with one at a time.


Again the starting point is the assymption "if MAC address of station is
in the association table of an AP, it will not discard the frames from
that station and will forward it."


Can anyone tell please, if my assymption is true or not?

Thank you.

Nazeer Khan

---------------------------- Original Message ----------------------------
Subject: Re: [Madwifi-devel] Fwd: Re: Association Table ???
From:    "Dan Searle" <da...@ad...>
Date:    Thu, October 26, 2006 7:09 pm
---------------------------------------------------------------

Hi,

It might just be me missing something, but two devices (two L2
interfaces) having the same MAC address sounds like a really bad idea.
Surely the whole point of a MAC address, that it's unique. Switches are
going to have a fit if you have both AP's on the same L2 network.

Dan...

Thursday, October 26, 2006, 10:02:52 AM, you wrote:

Hi,

I need some clarification on the basis of which i can proceed with my work.

I have two Access Points and one station. Station is in the range of both
AP. Both access points have same BSSID, same MAC address and same channel,
but station can be associated with one AP at a time and only that AP will
forward frames for the station. When station transmit the frame the
receiver address is the MAC address of the AP. Altough the second AP has
the same MAC address, it simply discards the packet because it could not
find the station in its association table.

If somehow I add the MAC address in the association table of second AP,
will it forward the frames for the station or not. (Don't worry that there
will be two copies, offcourse there will be a central point of decision
which will in the end discard the extra copy).

Is my assymption true that if MAC address of station is in the association
table of an AP, it will not discard the frames from that station and will
forward it??

> Please need a sincere reply because on this basis i will start my work.

> Thank you so much.

> Nazeer Khan


-------------------

From:    "Praveen Mehrotra" <pra...@gm...>

The mechanisms for doing what you want would be similar to handling
associated client data. Assuming all AP's have exchange information about
a new client (using some xyz mechanism), each AP may insert that client in
a node-queue (which probably should be different from queue used to track
associated clients). You can keep track of clients in 2nd queue using
sysctl. When client actually roams to a new AP, you would probably need to
manipulate node queues again so that now client shows up in associated
node-q.

Praveen





--------------------------------------------------------------------------
This email and any attachments may be confidential. They may contain legally
privileged information or copyright material. You should not read, copy,
use or disclose them without authorisation. If you are not an intended
recipient, please contact us at once by return email and then delete both
messages. We do not accept liability in connection with computer virus,
data corruption, delay, interruption, unauthorised access or unauthorised
amendment. This notice should not be removed.