So far every device I have WDS on (not many mind you) has issues with v5...

I am having the same issue on 5.11. It gets large amounts of traffic over the WDS interfaces as soon as they register and doesnt allow me to access them any more, i have to access via Mac address and disable to WDS to get back in. Have tried upgrading to 5.16 and am still having the same issue.
This seems to work fine with two APS connected via WDS, though when i have one AP with more than one WDS interface this is when the issue arises.
When i downgrade to version 4.16 the issue is gone.
Any ideas what is causing this?

we are unable to reproduce that large traffic problem when you start using WDS.
We need the simplest setup to reproduce this problem - that will help us to find the problem and fix.

I've been able to reproduce this consistently with 2 RB751U-2HnD's one as apbridge and the other as either apbridge or WDS slave, nothing else in the network. Usually only takes a few minutes for the storms to start.

I have the same exact problem on my pair of RB751U-2HnD running AP Bridge mode with WDS-Bridge. Tried all the firmware including V6Beta2 but storm still observed. Only firmware 4.17 is OK.

After trying several permutation of configurations, I managed to find a way to fix this. Under Bridge Port configuration, just enable Horizon settings on WDS and WLAN interface by defining a same number for both interfaces.

Do note that this Horizon settings can only be enabled on one of the two WDS nodes else traffic will somehow not pass through.

• If so, should the wlan interface itself not be a port on the bridge, just the WDS interface (via the wds-default-bridge setting)?
• If both are required, does this mean we have to just assign the same "horizon" values to each pair of wlan/WDS interfaces?
• Must WDS be static in order to assign it a permanent horizon value?

looks like we were able to find the loop when you connect two APs together with WDS. The fix will be added in v5.18.

looks like we were able to find the loop when you connect two APs together with WDS. The fix will be added in v5.18.

looks like we were able to find the loop when you connect two APs together with WDS. The fix will be added in v5.18.

Any idea on release date, as we have a very large installation due that will rely upon this.

Try out now the new test release that was made today.

Try out now the new test release that was made today.

36 hours without incident, and counting.

Disabling a radio occasionally takes the RB offline (no response via ether1, one of the bridge ports) for ~30 seconds, and enabling a radio often results in several seconds of multi-Megabit traffic over the newly-created WDS interface. But in both cases, everything settles back to normal in less than a minute.

Try out now the new test release that was made today.

36 hours without incident, and counting.

Disabling a radio occasionally takes the RB offline (no response via ether1, one of the bridge ports) for ~30 seconds, and enabling a radio often results in several seconds of multi-Megabit traffic over the newly-created WDS interface. But in both cases, everything settles back to normal in less than a minute.

Try out now the new test release that was made today.

36 hours without incident, and counting.

Disabling a radio occasionally takes the RB offline (no response via ether1, one of the bridge ports) for ~30 seconds, and enabling a radio often results in several seconds of multi-Megabit traffic over the newly-created WDS interface. But in both cases, everything settles back to normal in less than a minute.

try to use the wds-mode=dynamic-mesh on both boards and check again the logs.

try to use the wds-mode=dynamic-mesh on both boards and check again the logs.

name="wlan1" mtu=1500 mac-address=XX:XX:XX:13:2C:0F arp=enabled 
      interface-type=Atheros 11N mode=ap-bridge ssid="COP-Backhaul" 
      frequency=5320 band=5ghz-onlyn channel-width=20/40mhz-ht-below 
      scan-list=default wireless-protocol=unspecified wds-mode=dynamic 
      wds-default-bridge=br-backhaul wds-ignore-ssid=no bridge-mode=enabled 
      default-authentication=yes default-forwarding=yes default-ap-tx-limit=0 
      default-client-tx-limit=0 hide-ssid=no security-profile=Backhaul2 
      compression=no

name="Backhaul2" mode=dynamic-keys authentication-types=wpa2-eap 
     unicast-ciphers=aes-ccm group-ciphers=aes-ccm wpa-pre-shared-key="" 
     wpa2-pre-shared-key="" supplicant-identity="" eap-methods=eap-tls 
     tls-mode=no-certificates tls-certificate=none static-algo-0=none 
     static-key-0="" static-algo-1=none static-key-1="" static-algo-2=none 
     static-key-2="" static-algo-3=none static-key-3="" 
     static-transmit-key=key-0 static-sta-private-algo=none 
     static-sta-private-key="" radius-mac-authentication=no 
     radius-mac-accounting=no radius-eap-accounting=no interim-update=0s 
     radius-mac-format=XX:XX:XX:XX:XX:XX radius-mac-mode=as-username 
     radius-mac-caching=disabled group-key-update=5m 
     management-protection=allowed management-protection-key="1x2x3x4x"