High ping times with 11 CPE's on RB532...

RouterOS Wireless Networking
21

I don’t think bridging has anything to do with your problem. We use WDS for a lot of networks, and they typically work well if interference is low, we have good signal, we use good pigtails and antennas, and do bandwidth control to reduce flooding the APs. Here’s a ping from a gateway to an AP 3 WDS hops away [GW] – [AP1] ↔ [AP2] ↔ [AP3] ↔ [AP4] where Gatway=GW and the AP it pings is AP4 - each connected to the other via WDS bridging:

25 packets transmitted, 25 packets received, 0% packet loss
round-trip min/avg/max = 5/6.7/15 ms

This is on 5GHz to Routeboards with 2 radios (the other is 2.4GHz).

Yes…we are throttling in the sense that we are setting AP Tx limit and Client Tx limits in the ACL

I wonder if this might be causing some of your problems? Have you tried removing these settings and setting up queues on your gateway instead. Seems like this would add some overhead to the AP, especially if it were to become busy. I’ve never set tx/rx limits on the AP itself, so I’m not sure how well this works. Might be something to try at least temporarily.

22

Removed the AP Tx and Client Tx limits from all associated CPE’s and still horrible ping times. :frowning:

23

Do you have all of your ack-times set to dynamic (they should be if your clients are at different distances)? I can’t easily find the frequency you are running…is it 5GHz or 2.4GHz (a or g mode?)? Also, what antennas are you using?

24

Ack Timeout on the AP is set to dynamic. We are running in 5GHz with a single 120 degree 16 dbi sector.

25

Hmmm. Can you post the output from “/interface wireless reg print stat”? Maybe just include 2 or 3 of the problematic clients from this output as all of them will be too much. Also, I’m not sure if you’ve mentioned this, but have you tried other channels? Your ping output you posted shows packet sizes of 50. What does it look like with a size of 1500? Better, worse, or the same?

26

Jober: What i tried to say was:

supported-rates-a/g=24Mbps basic-rates-a/g=24Mbps

27

Here’s output for the first 2 CPE’s:

0 interface=wlan1 radio-name=“X0” mac-address=00:0B:6B:36:0C:D4
ap=no wds=yes rx-rate=12Mbps tx-rate=12Mbps packets=46323,28394
bytes=28836890,3724565 frames=34669,22744 frame-bytes=28852884,3692360
hw-frames=52920,250228 hw-frame-bytes=32111051,14755386 uptime=1h29m46s
last-activity=30ms signal-strength=-75dBm@6Mbps signal-to-noise=31dB
strength-at-rates=-75dBm@6Mbps 30ms,-75dBm@9Mbps 15m45s740ms,-75dBm@12Mbps
50ms
tx-signal-strength=-78dBm tx-ccq=36% rx-ccq=55% p-throughput=11315
nstreme=yes framing-mode=exact-size framing-limit=2200
routeros-version=“2.9.24” last-ip=10.10.0.149 802.1x-port-enabled=yes
authentication-type=none encryption=none compression=no

1 interface=wlan1 radio-name=“X1” mac-address=00:0B:6B:4D:77:3C
ap=no wds=yes rx-rate=12Mbps tx-rate=12Mbps packets=86208,38129
bytes=22797932,2155944 frames=75494,38561 frame-bytes=22490196,1971946
hw-frames=109330,287525 hw-frame-bytes=27715509,14327438 uptime=1h29m38s
last-activity=30ms signal-strength=-76dBm@6Mbps signal-to-noise=30dB
strength-at-rates=-76dBm@6Mbps 30ms,-75dBm@9Mbps 15s520ms,-76dBm@12Mbps
30ms
tx-signal-strength=-77dBm tx-ccq=35% rx-ccq=54% p-throughput=10410
nstreme=yes framing-mode=exact-size framing-limit=2200
routeros-version=“2.9.24” last-ip=10.10.0.34 802.1x-port-enabled=yes
authentication-type=none encryption=none compression=no

Ping times are sproadic even with a packet size of 1500…between 5ms and 80ms. Limiting the data rates at least brought them below 200 and 300ms. If I change channels, the clients SHOULD reassociate based on the scan list correct?

Thx for your input!

28

How much traffic is on the link while you test?

Yes to question about searching according to scan-list.

29

Bridge interface is passing no more than 768 Kbps as I type this. Most customers are residential and most likely currently at work. Even now with the traffic minimal, here’s ping output to one of the CPE’s:

00:0B:6B:4D:77:E7 64 byte ping time=35 ms
00:0B:6B:4D:77:E7 64 byte ping time=32 ms
00:0B:6B:4D:77:E7 64 byte ping time=34 ms
00:0B:6B:4D:77:E7 64 byte ping time=21 ms
00:0B:6B:4D:77:E7 64 byte ping time=44 ms
00:0B:6B:4D:77:E7 64 byte ping time=26 ms
00:0B:6B:4D:77:E7 64 byte ping time=16 ms
00:0B:6B:4D:77:E7 64 byte ping time=11 ms
00:0B:6B:4D:77:E7 64 byte ping time=30 ms
00:0B:6B:4D:77:E7 64 byte ping time=42 ms
00:0B:6B:4D:77:E7 64 byte ping time=50 ms
00:0B:6B:4D:77:E7 64 byte ping time=18 ms
00:0B:6B:4D:77:E7 64 byte ping time=21 ms
00:0B:6B:4D:77:E7 64 byte ping time=63 ms
00:0B:6B:4D:77:E7 64 byte ping time=68 ms
00:0B:6B:4D:77:E7 64 byte ping time=61 ms
00:0B:6B:4D:77:E7 64 byte ping time=30 ms
00:0B:6B:4D:77:E7 64 byte ping time=49 ms
00:0B:6B:4D:77:E7 64 byte ping time=48 ms
00:0B:6B:4D:77:E7 64 byte ping time=48 ms
00:0B:6B:4D:77:E7 64 byte ping time=48 ms
00:0B:6B:4D:77:E7 64 byte ping time=15 ms
00:0B:6B:4D:77:E7 64 byte ping time=32 ms

??? Weird huh?

30

From the 2 clients:
tx-ccq=36% rx-ccq=55%
tx-ccq=35% rx-ccq=54%

While not horrible, these should be a little higher for a solid connection. What type and gain are the antennas you are using on the CPE side? There seems to be a weakness on the CPE side as there is quite a difference between the client and the AP. If you look at the registration table on the CPE, is it similar to what you see on the AP? I’d try out a few different channels and see if your signals and the ccq values change at all.

As a side note and slightly off-topic, consider the values of output posted:

1 interface=wlan1 radio-name=“X1”

uptime=> 1h29m38s

strength-at-rates=-76dBm@6Mbps > 30ms> ,-75dBm@9Mbps > 15s520ms> ,-76dBm@12Mbps > 30ms

Could someone explain why the link uptime is 1h29m while all of the combined transmit rate times are around 15 minutes? I’ve noticed this before, and don’t really understand these as it seems they should be almost the same. Perhaps they mean something different?

31

perhaps you should let the cpe do the pppoe ?

32

Could someone explain why the link uptime is 1h29m while all of the combined transmit rate times are around 15 minutes? I’ve noticed this before, and don’t really understand these as it seems they should be almost the same. Perhaps they mean something different?

tx rate times are times since last use of that tx rate i guess.

33

We’re using Rootenna cases with 19dbi integrated for the CPE’s. Here’s output:

0 interface=wlan1 radio-name=“Oakbrush AP” mac-address=00:0B:6B:37:B5:20
ap=yes wds=yes rx-rate=12Mbps tx-rate=6Mbps packets=229521,227521
bytes=66677985,95310269 frames=103946,119077 frame-bytes=67389829,96136425
hw-frames=124344,2279907 hw-frame-bytes=71899169,199457306 uptime=1h17m16s
last-activity=10ms signal-strength=-74dBm@6Mbps signal-to-noise=35dB
strength-at-rates=-74dBm@6Mbps 0s,-75dBm@9Mbps 1h17m11s340ms,-75dBm@12Mbps
10ms
tx-ccq=33% p-throughput=11315 nstreme=yes framing-mode=exact-size
framing-limit=2200 routeros-version=“2.9.27” last-ip=69.39.23.58
802.1x-port-enabled=yes authentication-type=none encryption=none
compression=no

This began happening after we added approximately the 6th CPE to the AP.

34

tx rate times are times since last use of that tx rate i guess.

I think this is it…makes sense after looking at a few APs. Thanks :slight_smile:

How close are these CPEs to each other? As in, are all these in the same neighborhood?

35

We are seeing the same problem. The AP is an RB532 with 16 connected CPE running Station WDS and NStreme with polling. Testing with an AP with only two connected clients looks fine. Based on the results shown below, signal quality isn’t a problem. The AP is running at 333MHz w/SR5 and the client is an RB112 w/CM9.

25 packets transmitted, 25 packets received, 0% packet loss
round-trip min/avg/max = 3/9.5/30 ms


signal-strength: -66dBm
tx-signal-strength: -68dBm
noise-floor: -104dBm
signal-to-noise: 38dB
tx-ccq: 91%
rx-ccq: 100%
p-throughput: 36822
wds-link: yes
nstreme: yes
polling: yes
framing-mode: exact-size
framing-limit: 3200
framing-current-size: 2560

36

CPE’s are spread out by at least 3 miles each direction…

37

Go to the Ip ,firewall ,connections,and check connections there you can see
which SU make you trouble .Also Change TCP Established Timeout from 1d to 1 hour .Works for me after I make this changes .Ping come down From 400 ms to 1 to 3ms and speed from 300k to 6MB .

Best regards

38

I don’t think Frequency Scan will show non-802.11 systems using the frequencies. Can someone from Mikrotik comment please?

You could be sharing the area with one or more of the following:

  1. 2.4GHz AV sender
  2. 2.4GHz DSSS Trango
  3. 2.4GHz Motorola Canopy

JB

39

We’re operating in 5GHz…

40

So I’m determined to make this situation right and I think routing vs. bridging is ultimately the way to go. I’ve posted a diagram of my basic network config here:

http://www.skywerx.com/netdiagram.jpg

I guess I’m just not seeing how to add “routing” to the picture WITHOUT adding an entire hop in the network. What config changes in both the AP and the CPE would allow for me to get traffic inbound/outbound to the WWW? I assume that adding a default gateway to the AP of 10.10.0.1 AND then giving the AP an address of say 10.10.0.4 and THEN adding a default gateway to the CPE of 10.10.0.4 would do it??? Am I on the right track?

How do some of you others do it if you already have routers in the network that handle the traffic and you DON’T want to break out another subnet and put it DIRECTLY on the AP? How are you “routing” your traffic WITHOUT making the AP a dedicated “router” but rather pushing 0.0.0.0/0.0.0.0 to the correct gateway?

Please note that a MAJORITY of our network is Trango gear and the routing capabilities are NOT built into the AP/SU hence the reason for the network configuration. We’ve recently fell in love with the low cost MikroTik CPE BUT because of the numerous Trango radios (450+) we have deployed, re-subnetting to support “routing” in the MikroTik RB532 AP CAN’t realistically happen… :unamused:

Thank you!!!