Perdition,
As far as I can tell, there is no limit on this. You will have to bear in mind that it does entail a slight performance hit, supposedly, it breaks the maximum possible throughput down to 5.5MBps, I've never really noticed slowdowns on my network though.
Setting it up should be fairly straight forward. The best way to do it would be to work the same way as 802.1d spanning tree ethernet bridges, but manually.
WDS allows for setting up repeaters to repeat for specific APs only, so, AP 2 can repeat for AP 1 and 3 but AP 1 and 3 only repeat for AP 2. Since AP 2 is repeating for 1 and 3, a frame from an ethernet netework connected to AP 1 can be broadcast, repeated for AP 1 by AP 2, received by AP 3 and bridged back to an ethernet behind AP 3.
Perhaps I should explain in diagram form:
|ETHERNET|
||
| AP 1 |
||
|TO-AP-2|
||
\/
RADIO SIGNAL
/\
||
|TO-AP-1|
||
| AP 2 |
||
|TO-AP-3|
||
\/
RADIO SIGNAL
/\
||
|TO-AP-2|
||
| AP 3 |
||
|ETHERNET|
In other words, AP 2 would receive the radio signal from AP 1 and bridge any frames to its ethernet port (if it is connected to a network), and also retransmit the signal to its coverage footprint.
AP 3 would receive the retransmitted signal and in turn bridge the frames to its ethernet block, and yet again retransmit the frame to its coverage area.
You could keep going ad infinitum with a chain like this, since each AP only has to repeat signals for one or two other APs, which are in turn repeating signals for other APs. In this way, your signal should propagate to every AP and your ethernet frames should propagate to every ethernet network or wireless device connected to each AP.
WDS has built in safeties to prevent feedback loops, so you need not worry that AP 2 will repeat a signal it got from AP 3 which AP 3 just got from AP 2, etc.
Be sure not to set up repeater links between APs if they aren't needed. Each AP should only repeat for other APs that are just on the threshold of its coverage footprint.
Bouncing the signal in this way, you should be able to build a discreet network that can span several kilometers, without needing high gain antennas that attract a lot of attention, or worse, amplifiers, which are totally illegal.
The general coverage footprint you can expect from the A16B is about 300 meters when repeating for other APs, regardless of line of sight, and about 50 - 300 meters when talking to wireless client devices, depending on line of sight and the strength of the device.
So, for a network that can effectively bounce your signals over long distances, with minimal impact on performance, you will want one repeater AP at least every 300 meters.
If you place your repeaters in a straight line, you should be able to get a coverage area in one street of 1 kilometer or more with 4 of these little APs.
If you build in a star topology, you could feasibly create a mesh with limitless coverage around your area. Just make sure to be as economical as you can be in terms of the amount of other APs each AP must repeat for.
To jump over longer distances between users, just buy another AP and configure it as a repeater, but do not connect its ethernet. Then just find a neighbour who might not be interested in sharing the connection, but is willing to host an AP, to place the AP with.
When chosing locations for these APs, which in effect are true repeaters, the highest locations are the best. If you can find somebody with a two or three story house on elevated ground, you might be able to bounce signals for APs up to 600 meters away, I don't guarantee it though. Experiment.
A really nice side benifit of building your wide area guerilla network in this way is that you maintain denyability:
WDS repeater mode does not require that APs which repeat for each other share the same SSID, instead, WDS repeaters recognize their peers by MAC address.
This means, each AP can still have its own SSID. Roaming between the APs is provided by IAPP, so you need not worry about your wireless device not wanting to hop between SSIDs, it is instructed to do so automatically.
The denyability part comes in here. What you want to do is break the conventional rule that dictates that one should chose an SSID that is as vague and non-descript as possible, especially, one should never give away one's location or identity.
In this case, we break this convention by chosing SSIDs that are as descriptive as we possibly can. Then, if anybody should ever come knocking on your door, you can just tell them: "Well, look, the SSID says MYNAME, this AP is for my house, so I can use my PDA and my sister can use her laptop and so on...".
Your neighbour can just say: "Well, look, my SSID is set to HISNAME, it's just for me and my girlfriend to use my laptop around the house... "
Since WDS only retransmits frames and not SSID broadcasts, there is no way for any regulatory authority goon to prove that your APs are really "AP-repeaters" running in WDS mode. They will only see each AP's SSID broadcasts in that AP's actual coverage footprint.
To their feeble Wi-Fi finder devices, it will look as if there are a myriad of small, independant wireless networks, not one large repeater tree.
The frames propagating throughout the entire area can be explained as "stray signals, probably reflected by Mr. X's tin roof, or the water tower, or what ever... ", not that I think your standard ICASA goon will notice, since their Wi-Fi finder listens for broadcast SSID, not network frames. [

]
Willie Viljoen
Web Developer
Adaptive Web Development