strange behaviour with wds

RouterOS General
1

We’ve got 2 outdoor-routerboards running in wds-bridged mode.
If the tx-power of one of the wireless interfaces used for wds. Here is a ping output set tx-power to 9:
ping 192.168.125.5
PING 192.168.125.5 (192.168.125.5): 56 data bytes
64 bytes from 192.168.125.5: icmp_seq=0 ttl=64 time=8.5 ms
64 bytes from 192.168.125.5: icmp_seq=1 ttl=64 time=4.2 ms
64 bytes from 192.168.125.5: icmp_seq=2 ttl=64 time=4.3 ms
64 bytes from 192.168.125.5: icmp_seq=3 ttl=64 time=19.7 ms
64 bytes from 192.168.125.5: icmp_seq=4 ttl=64 time=5.4 ms
64 bytes from 192.168.125.5: icmp_seq=5 ttl=64 time=4.4 ms

— 192.168.125.5 ping statistics —
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 4.2/7.7/19.7 ms

when setting the tx-power to default, ping gets dups and has a higher time as before:

ping 192.168.125.5
PING 192.168.125.5 (192.168.125.5): 56 data bytes
64 bytes from 192.168.125.5: icmp_seq=0 ttl=64 time=180.9 ms
64 bytes from 192.168.125.5: icmp_seq=0 ttl=64 time=283.3 ms (DUP!)
64 bytes from 192.168.125.5: icmp_seq=0 ttl=64 time=392.1 ms (DUP!)
64 bytes from 192.168.125.5: icmp_seq=0 ttl=64 time=486.5 ms (DUP!)
64 bytes from 192.168.125.5: icmp_seq=0 ttl=64 time=591.6 ms (DUP!)
64 bytes from 192.168.125.5: icmp_seq=0 ttl=64 time=674.7 ms (DUP!)
64 bytes from 192.168.125.5: icmp_seq=0 ttl=64 time=769.1 ms (DUP!)
64 bytes from 192.168.125.5: icmp_seq=0 ttl=64 time=869.6 ms (DUP!)
64 bytes from 192.168.125.5: icmp_seq=0 ttl=64 time=960.6 ms (DUP!)
64 bytes from 192.168.125.5: icmp_seq=0 ttl=64 time=1051.6 ms (DUP!)
64 bytes from 192.168.125.5: icmp_seq=1 ttl=64 time=91.4 ms
64 bytes from 192.168.125.5: icmp_seq=0 ttl=64 time=1170.4 ms (DUP!)
64 bytes from 192.168.125.5: icmp_seq=1 ttl=64 time=211.2 ms (DUP!)
64 bytes from 192.168.125.5: icmp_seq=0 ttl=64 time=1331.9 ms (DUP!)
64 bytes from 192.168.125.5: icmp_seq=1 ttl=64 time=399.1 ms (DUP!)
64 bytes from 192.168.125.5: icmp_seq=0 ttl=64 time=1511.2 ms (DUP!)
64 bytes from 192.168.125.5: icmp_seq=1 ttl=64 time=586.3 ms (DUP!)
64 bytes from 192.168.125.5: icmp_seq=0 ttl=64 time=1690.4 ms (DUP!)
64 bytes from 192.168.125.5: icmp_seq=1 ttl=64 time=733.5 ms (DUP!)
64 bytes from 192.168.125.5: icmp_seq=0 ttl=64 time=1825.6 ms (DUP!)

— 192.168.125.5 ping statistics —
2 packets transmitted, 2 packets received, +18 duplicates, 0% packet loss
round-trip min/avg/max = 91.4/790.5/1825.6 ms

Can someone explain this?

2

What is your distance between the AP’s? What kind of radiocard do you use? Cables? Antennas?

3

Dist: ca. 400 m

Oudoor MT1
Cable: 1m lowloss
Antenna: 8dBi Omni

Outdoor MT2
Cable: 10m lowloss
Antenna: 8dBi Omni

Cards: 200 mW Mikrotik Prism PCMCIA (both sides)

4

probably too strong signal :slight_smile: we had same problem on 200m PtP link using Atheros on 5GHz. The signal level was between -40 and -45, tx-power=default. The link was going up and down every few seconds. I had to put tx-power=1 to have it running. It was either to remove antennas or to lower the tx-power. :slight_smile:

5

EIRP should be about 30dBm. If it’s a 2.4GHz link the RF should be about -60 and with a 5.6GHz link the RF should be about -66.

Unless I’ve made some bad calculations, this should not be a too strong signal.

But you could try sifferent TX-values. What is your ACK-setting?

6

hmm
you cannot set tx-power more than 20 , that meens your default is more than 20 (maybe 23 ) , i had same problem with senao 200mW , and i set it to tx-power=20 and now works fine for me links are 5 km ptp and ap mode