Distance is different AP vs CPE

[ganewbie]

Hi Guys,
We have an AP-Bridge with one client only (Station-Bridge).
1- CCQ is jumping between 60 to 90 all the time, never steady.
2- The distance on the AP shows 1Km (correct) but it shows 4 Km in the client.
Any recommendations?!

Attached is all the setups.

# model = 921GS-5HPacD r2
# serial number = 
/interface bridge
add fast-forward=no name=bridge
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
add authentication-types=wpa2-psk eap-methods="" management-protection=allowed mode=dynamic-keys name=profile supplicant-identity="" wpa2-pre-shared-key=xxxxxxx
/interface wireless
set [ find default-name=wlan1 ] adaptive-noise-immunity=ap-and-client-mode \
    antenna-gain=0 band=5ghz-a/n basic-rates-a/g="" channel-width=20/40mhz-Ce \
    disabled=no frequency=5765 ht-basic-mcs=mcs-0 ht-supported-mcs=\
    mcs-0,mcs-1,mcs-2,mcs-3,mcs-8,mcs-10,mcs-11,mcs-12,mcs-13 \
    hw-protection-mode=cts-to-self hw-retries=15 mac-address=\
    W:W:W:W:W:W mode=ap-bridge radio-name=XXXXXXXXX rate-set=\
    configured security-profile=profile ssid=XXXXXXXXX supported-rates-a/g="" \
    tdma-period-size=1 wireless-protocol=802.11 wps-mode=disabled
/ip hotspot profile
set [ find default=yes ] html-directory=flash/hotspot
/system logging action
add name=dude remote=x.x.x.x target=remote
/interface bridge port
add bridge=bridge interface=wlan1
add bridge=bridge hw=no interface=ether1
/ip neighbor discovery-settings
set discover-interface-list=all
/interface wireless access-list
/interface wireless cap
set caps-man-addresses=Yy.y.y.y interfaces=wlan1
/ip address
add address=x.x.x.x/8 interface=bridge network=x.0.0.0
/ip dns
set servers=8.8.8.8
/ip route
add distance=1 gateway=x.x.x.x

[macsrwe]

Known deficiency in ROS that “auto” distance is often wildly overestimated on one side of a PTP link, while correct on the other. Efficiency improvement can be had by entering specific distance into wireless config parameters instead of “auto” default. This alone may improve your CCQ situation. You could also try running with and without WMM to see if there is a difference.

Curious to me that your misestimation is on the station side, as in my experience the error has been uniformly on the bridge side of every link I own, while the station sides have been very accurate.

[ganewbie]

Thanks, macsrwe
I believe I may have fixed the mysterious low CCQ and wrong distance.
We changed the channel width to 20 instead of 20/40.
Choosing a certain data rate helped a lot but we were trying by trial and error until we got a CCQ and the speed we are aiming to offer.
Now the distance magically is correct and the CCQ is very acceptable.