NV2 High latency

RouterOS Wireless Networking
1

Hello

RB433 <<=====2km=====>> RB433

Linki info:

status: connected-to-ess
band: 5ghz-n
status: connected-to-ess
band: 5ghz-n
frequency: 5240MHz
wireless-protocol: nv2
tx-rate: 300.0Mbps
rx-rate: 300.0Mbps
ssid: to_radiob

signal-strength: -57dBm
signal-strength-ch0: -67dBm
signal-strength-ch1: -58dBm
tx-signal-strength: -56dBm
tx-signal-strength-ch0: -66dBm
tx-signal-strength-ch1: -57dBm
noise-floor: -116dBm
signal-to-noise: 59dB
tx-ccq: 99%
rx-ccq: 44%
authenticated-clients: 1
current-distance: 3
wds-link: no
bridge: yes
routeros-version: 5.4
last-ip: 10.20.30.1
current-tx-powers: 6Mbps:18(18/21),9Mbps:18(18/21),12Mbps:18(18/21),18Mbps:18(18/21),24Mbps:18(18/21),
36Mbps:17(17/20),48Mbps:16(16/19),54Mbps:14(14/17),HT20-0:18(18/21),HT20-1:18(18/21),
HT20-2:18(18/21),HT20-3:17(17/20),HT20-4:17(17/20),HT20-5:17(17/20),HT20-6:16(16/19),
HT20-7:12(12/15),HT40-0:16(16/19),HT40-1:16(16/19),HT40-2:16(16/19),HT40-3:16(16/19),

Traffic (at the time of the test)

name: vpls
rx-packets-per-second: 357
rx-drops-per-second: 0
rx-errors-per-second: 0
rx-bits-per-second: 2.2Mbps
tx-packets-per-second: 387
tx-drops-per-second: 0
tx-errors-per-second: 0
tx-bits-per-second: 1396.5…

Radio config:

0 R name=“wlan1” mtu=1500 arp=enabled disable-running-check=no interface-type=Atheros 11N
mode=station-bridge ssid=“to_radiob” area=“” frequency-mode=manual-txpower country=poland antenna-gain=0
frequency=5180 band=5ghz-onlyn channel-width=20/40mhz-ht-above scan-list=default wireless-protocol=nv2 rate-set=default
supported-rates-b=1Mbps,2Mbps,5.5Mbps,11Mbps supported-rates-a/g=6Mbps,9Mbps,12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,54Mbps
basic-rates-b=1Mbps basic-rates-a/g=6Mbps max-station-count=2007 distance=dynamic tx-power-mode=default noise-floor-threshold=default
nv2-noise-floor-offset=default periodic-calibration=default periodic-calibration-interval=60 dfs-mode=none wds-mode=disabled
wds-default-bridge=none wds-default-cost=100 wds-cost-range=50-150 wds-ignore-ssid=no update-stats-interval=disabled bridge-mode=enabled
default-authentication=yes default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0 proprietary-extensions=post-2.9.25
wmm-support=disabled hide-ssid=no security-profile=default disconnect-timeout=3s on-fail-retry-time=100ms preamble-mode=both
compression=no allow-sharedkey=no station-bridge-clone-mac=00:00:00:00:00:00 ht-ampdu-priorities=0 ht-guard-interval=any
ht-supported-mcs=mcs-0,mcs-1,mcs-2,mcs-3,mcs-4,mcs-5,mcs-6,mcs-7,mcs-8,mcs-9,mcs-10,mcs-11,mcs-12,mcs-13,mcs-14,mcs-15
ht-basic-mcs=mcs-0,mcs-1,mcs-2,mcs-3,mcs-4,mcs-5,mcs-6,mcs-7 ht-txchains=0,1 ht-rxchains=0,1 ht-amsdu-limit=8192 ht-amsdu-threshold=8192
tdma-period-size=2 nv2-queue-count=2 nv2-qos=default nv2-cell-radius=30 nv2-security=disabled nv2-preshared-key=“” hw-retries=15
frame-lifetime=0 adaptive-noise-immunity=none hw-fragmentation-threshold=disabled hw-protection-mode=none hw-protection-threshold=0
frequency-offset=0 rate-selection=legacy

ping,s

64 bytes from 192.168.1.213: icmp_seq=14 ttl=64 time=27.9 ms
64 bytes from 192.168.1.213: icmp_seq=15 ttl=64 time=6.91 ms
64 bytes from 192.168.1.213: icmp_seq=16 ttl=64 time=10.3 ms
64 bytes from 192.168.1.213: icmp_seq=17 ttl=64 time=40.6 ms
64 bytes from 192.168.1.213: icmp_seq=18 ttl=64 time=35.9 ms
64 bytes from 192.168.1.213: icmp_seq=19 ttl=64 time=59.9 ms
64 bytes from 192.168.1.213: icmp_seq=20 ttl=64 time=33.2 ms
64 bytes from 192.168.1.213: icmp_seq=21 ttl=64 time=15.6 ms
64 bytes from 192.168.1.213: icmp_seq=22 ttl=64 time=55.7 ms
64 bytes from 192.168.1.213: icmp_seq=23 ttl=64 time=28.7 ms
64 bytes from 192.168.1.213: icmp_seq=24 ttl=64 time=5.42 ms
64 bytes from 192.168.1.213: icmp_seq=25 ttl=64 time=47.7 ms
64 bytes from 192.168.1.213: icmp_seq=26 ttl=64 time=53.8 ms
64 bytes from 192.168.1.213: icmp_seq=27 ttl=64 time=23.1 ms
64 bytes from 192.168.1.213: icmp_seq=28 ttl=64 time=27.4 ms
64 bytes from 192.168.1.213: icmp_seq=29 ttl=64 time=31.7 ms
64 bytes from 192.168.1.213: icmp_seq=30 ttl=64 time=12.4 ms
64 bytes from 192.168.1.213: icmp_seq=31 ttl=64 time=3.30 ms
64 bytes from 192.168.1.213: icmp_seq=32 ttl=64 time=36.2 ms
64 bytes from 192.168.1.213: icmp_seq=33 ttl=64 time=31.2 ms

ROS 5.4, traffic through VPLS from wiki

What is wrong ?

2

Well, I see a rx CCQ of less then 50%, meaning a lot of packages don’t make it (complete). So somewhere you have a problem.
Also, switch ani on (Adaptive Noise Immunity) on both ends…
set rates to some fixed ones…
Show settings of both ends.
Any interferences?
Fresnell? Free LOS?

A lot more info is needed to help you giving more usable info…

3

The way NV2 Works is entirely different than Nstreme/802.11

Under the TDMA settings, any client that is not actively participating in traffic, will see longer ping times. I believe it is because the ap has a longer inital poll time for traffic, though this same

phenomenon happens under PTP NV2 links as well.


Do this:

Do a bandwidth test over the link, but limit the TX and RX speed to say… 5 Megabits send and recieve,

and then do your ping tests.

Also try a real world response test over the link to see your real packet transmit times.

http://myspeed.visualware.com/indexvoip.php

There is a excellent voip test. it will test your jitter ping and packet loss with small packets and you can see your actual times out to a destination.

You will notice than when your link is under load, your static ping times will show the actual latency of the link, rather than just some arbitrary number as it is prone to do under no load.

I’ll share an example: First picture is the link under load, the second (bottom) picture is a link under NO load.
5mLoad.jpg
NoLoad.jpg

4

Mikrotik should perhaps work on some options to reduce this latency ptp links, i understand that if only one client connect , tdma should work differently.

5

SOLVED. In my case, this interferences were but in my opinion ping times are higher than on nstreme.