Hi everybody,
is it possible to bring down the Ping-Time under 4 ms?
We are using two RB100s with AR5213 in PTP-Mode with WDS.
4-5 ms is not much but now we must use one or two additional WLANs Lines to connect another base. And that means twice ore thre times 4-5ms…
so what? it’s just a number …
you want to lower the number, or fix some issue that you are having?
@fux
My first guess you are using nstreme feature?
You cannot get 1ms with that as far as I know in the world 
Hello Fux…
I am very very interesting about your pinging result action not more than …4-5ms
This’s one of my ap [xxxxx@apo] with omni 15 dbi, one sample connect to station [xxxxx@vpadi] around 4,5km NLOS [mount and forest condition], here many interferences.
I think, that result at the bottom is ‘good’ quality, before i tried with wds but poor in pinging and speed, and i am so sorry, that ‘sensitive value’, i edited with ‘xx’.
My question: can you give me litle methode, how to make much better than it screen result…?
This’s monitor ap status.
[xxxxx@apo] interface wireless> mo 0
status: running-ap
band: 2.4ghz-b
frequency: 2437MHz
noise-floor: -105dBm
overall-tx-ccq: 71%
registered-clients: 2
authenticated-clients: 2
current-ack-timeout: 30
current-distance: 30
nstreme: no
current-tx-powers: 1Mbps:20,2Mbps:20,5.5Mbps:20,11Mbps:20
notify-external-fdb: no
This’s pinging to station from ap
[xxxxx@apo] interface wireless> /ping xx.xx.xx.5
xx.xx.xx.5 64 byte ping: ttl=64 time=7 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=4 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=10 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=4 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=6 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=5 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=4 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=5 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=4 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=4 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=11 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=5 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=5 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=4 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=4 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=4 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=8 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=5 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=4 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=4 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=4 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=8 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=4 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=10 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=4 ms
xx.xx.xx.5 64 byte ping: ttl=64 time=9 ms
48 packets transmitted, 48 packets received, 0% packet loss
round-trip min/avg/max = 4/7.9/25 ms
This is monitor station from ap
[xxxxx@vpadi] interface wireless>mo 0
status: connected-to-ess
band: 2.4ghz-b
frequency: 2437MHz
tx-rate: 11Mbps
rx-rate: 11Mbps
ssid: "xx-xx-xx"
bssid: xx:xx:xx:xx:xx:xx
radio-name: ""
signal-strength: -79dBm
tx-signal-strength: -77dBm
noise-floor: -98dBm
signal-to-noise: 19dB
tx-ccq: 74%
rx-ccq: 80%
p-throughput: 4097
current-ack-timeout: 30
current-distance: 30
wds-link: no
nstreme: no
framing-mode: none
routeros-version: "2.9.30"
last-ip: xx.xx.xx.4
802.1x-port-enabled: yes
-- [Q quit|D dump|C-z pause|down]
[xxxxx@vpadi] interface wireless>