Hi All
I replaced my RB133c (R52) to a new RB433 routerboard with a R52H mini pci card. All boards are running Mikroitk v3.14.
I would setup a WDS bridge between the Mikrotik AP and Linksys AP, using this guide as reference.
http://sujianto.files.wordpress.com/2008/05/how-do-i-set-up-wds-using-mikrotik.pdf
Here’s the Problem.
When I try to ping any of the linksys AP’s the connections timeout with a response reply of 2s every now and then. Connectivity to local working 100%.
However if I remove the PoE Nic from the Bridge, I can ping all my Linksys AP’s without any problems (6ms), but connectivity to local lan is broken then.
Now the crux of the situation is that I would take the R52H card and put in the RB133c with the exact same results.
then
I would take a R52 and put it in either the RB133c or RB433 and I then can successfully setup the bridge with connectivity to Linksys AP and local lan.
Help will be appreciated.
Thx in advance.
WDS is not a standard function and therefore varies amongst devices, mikrotik can only confirm that their WDS will work with other Mikrotik devices.
WDS may be incompatible between different products (even occasionally from the same vendor) as it is not certified by the Wi-Fi Alliance.
http://en.wikipedia.org/wiki/Wireless_Distribution_System
Thx omega
Why would it work with the R52 Cards and not the R52H, same chipset, just a more powerfull card…?
WDS is support in all atheros chipsets…correct…?
Linksys WRT54G are running the Atheros chipset, loaded with DD-WRT they are working 100% with R52 card but for some reason not the R52H card.
Just does not make sense.
Update:
I think this must be a bug or something.
I took my config from my RB133 and restored on the RB433 with the R52H card, changed the interface for wlan on bridge and corrected wds.
It’s is working, I can ping both the lan and wds lan side 100%, but it works for 5min the the router freeze up.
This config comes from the RB133 that has been upgraded from 2.38 to 2.50 to 3.14.
To me it looks like a config / route or something that prevents the wds working on the R52H card and not the physical hardware.
Any suggestions, to either make the old config work or something that I might be missing, redoing the config from scratch…?
Thx
After restoring the old config from RB133 the bridge works 100% now.
even did a /system/reset and the bridge now function as required.
Weird, but at least it works now for both R52 and R52H cards.
Thx for the excellent help from this forum…?
Just to feedback.
I managed to fix the problem. Connection tracking in the Firewall must be enabled. Other wise WDS throught the bridge do not work.
Thx