I’m having some troubles with WDS dynamic-mesh performance and I have some questions about best practices.
Here is my setup:
2 x (RB 433 UAH, ROS 4.10, R52Hn)
The wireless interface is in WDS, which is added to a mesh, and it is working as “ap-bridge”.
Now, when I have no WDS enabled, just 1 MT is station and 1 is ap-bridge, performance looks like this:
tcp, both = 46.5Mbps/46.5Mbps, 216Mbps-HT/270Mbps-HT
But the same link with WDS enabled looks like this:
tcp both = 14.8/12.6Mbps, 54Mbps/216Mbps-HT, which is just bad.
I’ve tried to search for some help on the forum, but the only info I’ve found is that MT in ap-bridge mode with WDS works 50% of time as AP and 50% as Station. Is that true? If so, how can i make my WDS backbone mesh more effective? I’d like to use 2 independent wireless cards, 1 for backbone WDS and 1 for client access. Than, which moeds should the cards run? Just “bridge” and WDS for backbone and “ap-bridge” for client access?
Are there any good practices for setting up a WDS mesh backbone and client access?
@ayufan: Is it broken only with n cards, or the cost of using it is always that high, no matter what type of cards you use? And, why is the cost so gigh, how does it work, that it is that ineffective?
Yep - Don’t do it.
If you want Max thruput, you need to spend more money and have AP<->Client all over.
If you want Cheapest, use Mesh and/or WDS, but there is a big performance cost.
OK, the problem is… I really have a dynamic mesh situation, where some of the APs are mobile. Of course some are not and I can try using EoIP/VPLS there, but they are all static solutions. I need some way to get a mobile layer 2 (or 3) network, so WDS dynamic mesh with HWMP+ seemed to be ideal.
So, there is no way to make WDS more effective, even when using multiple radios?
Could you please give me some clues how to do that, how are your MTs configured and how does the performance look like? I’ve tried to run WDS on Nstreme links, but with no success.