I’ve recently noticed two new settings for a wireless interface relating to WDS (not sure when these were added to 2.9):
WDS Default Cost (wds-default-cost)
WDS Cost Range (wds-cost-range)
What exactly do these do? Is this for bridging and STP/RSTP or something else? Would be curious to test these if there were some info about them. Thanks.
Yes, it is used for RSTP.
Can someone explain to how I would adjust these settings?
We have never been able to keep WDS running with out disconnections over a 12hr period.
WDS is allways disconnecting which takes the PPPoE client offline for 30sec to 1 min at a time untill the WDS sorts itself out.
We are now running a PPPoE server on the RB on there roof as a temp solution running in station mode for those customers that complain of a poor service. In other words, convert back before we use WDS.
This means that we are not able to account for the data on our raduis 
Matt
what’s your configuration? i can’t say i have that problem anymore. maybe you are using different hardware or configuration?
Hi sten
Here is the AP side:
Flags: X - disabled, R - running
0 R name=“maLinwood1” mtu=1500 mac-address=00:01:B4:02:0B:23 arp=enabled disable-running-check=no
interface-type=Atheros AR5213 radio-name=“den-maLinwood1 (Linwood)” mode=ap-bridge
ssid=“maLinwood1” area=“” frequency-mode=manual-txpower country=no_country_set antenna-gain=0
frequency=5220 band=5ghz scan-list=default rate-set=default
supported-rates-a/g=6Mbps,9Mbps,12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,54Mbps
basic-rates-a/g=6Mbps max-station-count=2007 ack-timeout=dynamic tx-power-mode=default
noise-floor-threshold=default periodic-calibration=default periodic-calibration-interval=60
burst-time=disabled dfs-mode=none antenna-mode=ant-a wds-mode=dynamic
wds-default-bridge=corebridge wds-default-cost=100 wds-cost-range=50-150 wds-ignore-ssid=no
update-stats-interval=disabled default-authentication=yes default-forwarding=yes
default-ap-tx-limit=0 default-client-tx-limit=0 hide-ssid=no security-profile=default
disconnect-timeout=3s on-fail-retry-time=100ms preamble-mode=both compression=no
allow-sharedkey=no
And the Client end:
2 R name=“bbToScoutden” mtu=1500 mac-address=00:02:6F:20:F4:90 arp=enabled disable-running-check=no
interface-type=Atheros AR5212 radio-name=“BNZ” mode=wds-slave ssid=“maLinwood1” area=“”
frequency-mode=manual-txpower country=no_country_set antenna-gain=0 frequency=5300 band=5ghz scan-list=default
rate-set=default supported-rates-b=1Mbps,2Mbps,5.5Mbps,11Mbps supported-rates-a/g=6Mbps basic-rates-b=1Mbps
basic-rates-a/g=6Mbps max-station-count=2007 ack-timeout=dynamic tx-power-mode=default
noise-floor-threshold=default periodic-calibration=disabled periodic-calibration-interval=60 burst-time=disabled
dfs-mode=none antenna-mode=ant-a wds-mode=dynamic wds-default-bridge=corebridge wds-default-cost=100
wds-cost-range=50-150 wds-ignore-ssid=no update-stats-interval=disabled default-authentication=yes
default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0 hide-ssid=no security-profile=default
disconnect-timeout=3s on-fail-retry-time=100ms preamble-mode=both compression=no allow-sharedkey=no
Wouldn’t you want to be in station-wds mode anyway? Or are you also using your clients as repeaters? I’ve not had any problems with WDS when using dynamic mode and station-wds on the client side. Also, no problems with using static WDS entries and stations in ap-bridge mode.
Thank you for your comments jarosoup,
We have tried lots of different configurations. It seams to loose connection at the AP end. The WDS will drop its connections etc, but not the client end.
Customers connecting in station mode not running WDS stay up for days on end with no problems.
How many clients do you have on the AP?
As for the original question, the RSTP shows up as /test-bridge where you can add a bridge similar to adding a regular bridge. However, when adding a new one, it does not show up under interfaces, and I’m not sure where to go from there. Mirkotik, any input or crash course on how to use RSTP and the new WDS settings?
Shortly after creating this RSTP bridge, I got a kernel panic. Currently, this is a WDS station with a CM9 card running at a 10-MHz channel (all power and most settings still at default) on a wrap.2c. I have no idea if this is related to the RSTP package I just installed, and can’t reproduce it yet. This is the output I got:
[admin@MikroTik] test-bridge links> general protection fault: 0003
CPU: 0
EIP: 0010:[] Tainted: P
EFLAGS: 00010246
eax: 00000000 ebx: c0234000 ecx: c10c4270 edx: c10c4270
esi: c0106e00 edi: ffffe000 ebp: 0008e000 esp: c0235fe0
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, stackpage=c0235000)
Stack: c0106e87 00000000 00099e00 c0105000 c0105027 c023669a c02489c0 c0100191
Call Trace: [] [] []
Code: c3 fb c3 89 f6 fb ba 00 e0 ff ff 21 e2 b8 ff ff ff ff 87 42
Kernel panic: Attempted to kill the idle task!
In idle task - not syncing
<0>Rebooting in 1 seconds..a5212: disable, tx_count 128, tx_bufs 0, flags 0xe
a5212: minPower 22, maxPower 34
a5212: minPower 4294967289, maxPower 43 after power table
a5212: disable, tx_count 128, tx_bufs 0, flags 0xe
a5212: minPower 22, maxPower 34
a5212: minPower 4294967288, maxPower 43 after power table
a5212: disable, tx_count 128, tx_bufs 0, flags 0xe
a5212: minPower 22, maxPower 34
a5212: minPower 4294967287, maxPower 42 after power table
a5212: disable, tx_count 128, tx_bufs 0, flags 0xe
a5212: minPower 22, maxPower 34
a5212: minPower 4294967286, maxPower 42 after power table
a5212: disable, tx_count 128, tx_bufs 0, flags 0xe
a5212: minPower 22, maxPower 34
a5212: minPower 4294967286, maxPower 42 after power table
BUFS: b_a 3, b_f 0, f_a 3, f_f 0
a5212: disable, tx_count 128, tx_bufs 0, flags 0xe
a5212: minPower 22, maxPower 34
a5212: minPower 4294967285, maxPower 42 after power table
a5212: disable, tx_count 128, tx_bufs 0, flags 0xe
a5212: minPower 22, maxPower 34
a5212: minPower 4294967284, maxPower 41 after power table
a5212: disable, tx_count 128, tx_bufs 0, flags 0xe
a5212: minPower 22, maxPower 34
a5212: minPower 4294967283, maxPower 41 after power table
a5212: disable, tx_count 128, tx_bufs 0, flags 0xe
idle_enter (from 1)
/test-bridge menu in console is not the correct way to configure RSTP bridge, use as usually /interface bridge
test bridge we will remove
But still it shouldn’t cause the kernel panic.
Please make the support output file after the reboot of the router and send it to support@mikrotik.com
Despite the new settings WDS still doesnt seem to work on Prism. When will this be fixed.
Prism on WDS ir working. Set both cards to AP/Bridge mode, same freq,ssid and enable wds-mode. After that you should be able to make wds.
hi. i’m making the support file but i can’t finde it??? do u have any idea where to find it?
/file print
Access router FTP (ftp://router_IP_address), support output file should be at root directory.
thx