WDS Functions 3.1 release

[sldnkarm]

I have a MikroTik AP running 3.10 firmware. I had a PS2 running 3.0 that would work just fine in StationWDS mode. As soon as I upgraded the PS2 to 3.1 I was unable to successfully establish the StationWDS connection.

I did see that you "fixed" some issue in regards to a PS2 set to AP running a WDS connection to a MikroTik station. In doing so, you may have disrupted the operation of the PS2 in StationWDS mode. I cannot say for sure, but 3.1 seems to be the culprit.

Can you confirm or deny this and let me know if any resources can be made available to fix the issue? There are a list of tools in 3.1 that we do not want to give up but may have to in order to support the WDS connection type.

[UBNT-Mike.Ford]

Hello,

Please contact me for Version 3.2 RC of the firmware to help with your WDS problems.

Thank you,

Mike

Mike@ubnt.com

[sldnkarm]

I am now running the XS2.ar2316.v3.2.2.3891.081021.2153 and still no fix for running the PS2 in stations-wds mode and associating it to a MikroTik AP. What are the chances that the 'fixes' introduced in 3.1 can be reversed so I can get the functionality I need?

[UBNT-Mike.Ford]

Hello Sldnkarm,

I am still trying to replicate this WDS issue here in the lab. All version of MikroTik RouterOS V2.9.45, 3.0, 3.10, 3.14 all have no issues talking with our units in Station WDS.

Thanks,

Mike

[sldnkarm]

Just to make sure we are discussing the same issue. I am running my PS2 in Station-WDS mode and my MikroTik (3.10) in AP-Bridge mode with dynamic wds enabled.

Let me know if this is how you are running your lab setup.

[UBNT-Mike.Ford]

Hello Sldnkarm,

All of my MikroTik's are running in AP/Bridge with Dynamic WDS - On, WDS Bridge set to bridge 1.

Are you running WPA?

Thanks,

[sldnkarm]

I am not running WPA on the MikroTik AP's or PS2's.

[UBNT-Mike.Ford]

Are you leaving the WDS peers list empty on the PowerStation?

[sldnkarm]

Ok, now you are confusing me. I am using my PS2, in Station-WDS mode to associate to the MikroTik AP in ap-bridge mode.

WDS peers is only available in Access Point WDS mode, correct?

[UBNT-Mike.Ford]

Yes I apologize I misread. Other then settings the unit to Station WDS mode, there is nothing else needed to talk with a MikroTik.

Thanks,

Mike

[sldnkarm]

Do you have more that one ip/mac pair behind the PS2(Station-WDS)? Or are you just using one 'client' mac/ip pair?

[UBNT-Mike.Ford]

Hello Sldnkarm,

I have set it up with 7 MAC pairs behind the STA/WDS unit, using an 8 port switch.

Thanks,

Mike

[sldnkarm]

care to share the wireless configurations of each unit? I am not getting the same results as you and would like to know where I am setting something incorrectly.

maybe just a "/int wire pri adva" for the m-tik.

[UBNT-Mike.Ford]

Hey Sldnkarm,

The MikroTik's I use are near factory config.

The only things I change, are adding the bridge, adding the WLAN and ETH0 interface to the bridge, then setting up the wireless card.

Pretty straightforward.

Thanks,

Mike

[sldnkarm]

How about the wds settings provided under "/int wireless"? I use the following:
wds-mode = dynamic
wds-default-bridge = br0(the bridge I create)

That's the only other thing I am doing outside of what you described you did above.

I realize that setting up the M-Tik is straightforward, but as I said at the top of this thread, something changed in 3.1 of AirOS. That's when I lost the ability to support the same PS2(station-WDS) connection I had been utilizing in previous versions of AirOS.

I understand that this is not a "MikroTik" forum, but I need the power provided from the RH433ah series boards. That is until the RouterStation is available and comes with AirOS, then I won't need to worry about these things.

Thanks for your time.

[UBNT-Mike.Ford]

Hello Sldnkarm,

I am using the same settings under WDS. I set WDS to Dynamic, and teh Default Bridge to BR0.

What country code are you using for the wireless settings? Also have you tried the firmware that I released today? Are you using channel shifting or compliance test mode on teh PS2?

Thanks,

Mike

[sldnkarm]

I have not tried the new version of AirOS, but I will Thurs.

No Channel Shifting or Compliance Test are being used.

Thanks. I will get back with you on the new firmware version and this particular situation.

[sldnkarm]

Got the new version loaded today. Didn't fix my issues.

PS2 (station-wds) <<--->> MikroTik(ap-bridge w/ dynamic wds)

Still cannot get the wds connection to work...not sure how you are getting this to work, but would you mind sending me your configuration file for the PS2? I am not sure what else to try and this point. What 'Network Mode' are you running? I am running 'bridge'.

[UBNT-Zy]

Hello Sldnkarm,

PS2 STA-WDS mode (v3.2.2 FW) was successfully tested with RouterOS v2.9.51 and v3.14 Dynamic WDS feature. Please check for the log entries in routeros as we'll need more clues for the futher investigation. I'm attaching working PS2 configuration file just in case.


bridge.1.devname=br0
bridge.1.fd=1
bridge.1.port.1.devname=eth0
bridge.1.port.2.devname=ath0
bridge.status=enabled
ebtables.status=enabled
gui.language=en_US
httpd.port=80
httpd.status=enabled
netconf.1.alias.1.status=disabled
netconf.1.devname=eth0
netconf.1.ip=0.0.0.0
netconf.1.netmask=255.255.255.0
netconf.1.promisc=enabled
netconf.1.status=enabled
netconf.1.up=enabled
netconf.2.alias.1.status=disabled
netconf.2.allmulti=disabled
netconf.2.devname=ath0
netconf.2.ip=0.0.0.0
netconf.2.netmask=255.255.255.0
netconf.2.status=enabled
netconf.2.up=enabled
netconf.3.autoip.status=enabled
netconf.3.devname=br0
netconf.3.ip=192.168.1.114
netconf.3.netmask=255.255.255.0
netconf.3.status=enabled
netconf.3.up=enabled
netconf.status=enabled
netmode=bridge
radio.1.ack.auto=enabled
radio.1.acktimeout=48
radio.1.channel=11
radio.1.chanshift=0
radio.1.clksel=0
radio.1.countrycode=840
radio.1.devname=ath0
radio.1.ext_antenna=disabled
radio.1.frag=off
radio.1.ieee_mode=g
radio.1.mcastrate=1M
radio.1.mode=managed
radio.1.rate.auto=enabled
radio.1.rate.max=54M
radio.1.rts=off
radio.1.rx_antenna=2
radio.1.rx_antenna_diversity=disabled
radio.1.status=enabled
radio.1.thresh62a=28
radio.1.thresh62b=28
radio.1.thresh62g=28
radio.1.tx_antenna=2
radio.1.tx_antenna_diversity=disabled
radio.1.txpower=16
radio.countrycode=840
radio.ratemodule=ath_rate_minstrel
radio.status=enabled
resolv.nameserver.1.ip=192.168.1.3
resolv.nameserver.1.status=enabled
resolv.status=enabled
route.1.devname=br0
route.1.gateway=192.168.1.1
route.1.ip=0.0.0.0
route.1.netmask=0
route.1.status=enabled
route.status=enabled
sshd.port=22
sshd.status=enabled
telnet.port=23
telnetd.status=enabled
users.1.name=ubnt
users.1.password=VvpvCwhccFv6Q
users.1.status=enabled
users.status=enabled
wireless.status=enabled
wireless.1.addmtikie=enabled
wireless.1.authmode=1
wireless.1.devname=ath0
wireless.1.l2_isolation=enabled
wireless.1.security=none
wireless.1.signal_led1=94
wireless.1.signal_led2=80
wireless.1.signal_led3=73
wireless.1.signal_led4=65
wireless.1.ssid=MikroTik-XR2-Br-2442
wireless.1.status=enabled
wireless.1.wds=enabled

[sldnkarm]

I upgraded M-Tik router to 3.14 with PS2 @ 3.2.2, still no luck.

I downgraded PS2 to 3.0 to verify proper operation of setup. Station-WDS mode works fine as long as PS2 version is 3.0. While changing back to this version, I noticed in the log the following line that I was not seeing before while the PS2 was running 3.2.2...

MikroTik Log:
10:14:17 wireless,info 00:15:6D:A6:3A:3D@wlan1: connected, wants WDS

Thanks.

[sldnkarm]

Does silence mean that you are no longer interested in looking into this issue? I know there is only so much you can do to try and help me get this working, but I am at a loss as to why my setup is not working just like yours?

What extra information do you need me to provide? The biggest thing I was seeing in the logs of the Access Point (M-Tik) was that with the PS2 running version 3.0, it said the PS2 was requesting a 'wds connection'. When running the PS2 with versions after 3.0 this was not seen in the M-Tik AP and I was unable to get a successful wds connection between the two.

[sar]

When I first tried WDS I could not get it to work. I had; "Client Isolation" enabled. Once I disabled "Client Isolation" it worked perfect.

in your config it says wireless.1.l2_isolation=enabled

[sldnkarm]

thanks sar. I tried your setting and it seemed to fix the issue. However, I cannot get it to 'fail' now. I have been trying to not allow the wds connection by changing settings on the CPE, including firmware, but cannot. Will keep updating as to what I find on this issue.

[sldnkarm]

1-Reset PS2 back to default config.
2-Associated PS2 to MikroTik AP in Station mode and verified connectivity.
3-Tried to associate PS2 to MikroTik AP in Station-WDS mode, but was unsucessful.
4-Set default-forwarding=no on MikroTik AP, which allowed the PS2 to associate in Station-WDS mode.
5-Set default-forwarding back to yes on MikroTik AP and was still able to connect PS2 with Station-WDS mode.

Nothing is consistent yet...