We have a RB532 running version 2.9.23 configured as an AP Bridge and we have 11 CPE’s (RB112’s) configured as Station WDS. Ping times to client routers are sporadically jumping into the 300-400 ms range with occasional request time outs. The AP processor utilization is around 20%. The frequency utilization in our area is minimal and interference id not a problem. Any ideas why the ping times would be so bad? It has progressively gotten worse as we’ve added more CPE’s to the AP.
I’m encountering the identical issue with our RB532.
I’m using 1 Senao card and 1 CM9 card, both bridge with one ethernet interface.
During the long ping, it could append on CM9 as on Senao the signal is good for clients and ack is 56 us.
The only different that I have notice is the ack of the card, that is about 200us.
I have set dinamic ack with threshould of -80.
after 1 min that the clients ping 400 ms the ping return to 1 ms as normal work. Some time the long ping occours every 10 min sometime every 2 min.
Have you verify or found a solution to the issue long pings?
I had the same problem with on of RB230 with about 8 CPE’s conected and a load of 4-6 Mbps, the Nstream with Polling was a solutoin but it might be a problem with cpu load, depending on how much traffic do you have on your Ap but I sugest you give a try.
Thanks for the reply.
We did in fact enable nstreme/polling and the ping times are still pretty ridiculous. Anywhere from 16ms to 249ms.
I added a firewall filter to see if P2P traffic was causing grief and 0 packets were caught by the filter so I know that can be taken out of the picture. CPU utilization is staying around 35% pretty consistently.
Our ack timeout for wlan1 stays at 25us. Shouldn’t this be dynamically changing based upon the client that is the longest distance? I’m assuming this is now a timing issue…???
Here is a screenshot of the sporadic ping times we’re seeing with the above mentioned config. Just upgraded the rb532 to v2.9.27 to see if software was a potential problem candidate…issue still exists.
Any ideas?
Your basic-rates should not be changed…set it back to 6Mb.
Have you used torch and looked at the firewall connections to see what’s going on on your network? Sounds like you are either overloaded with traffic, or you’ve got signal (interference or hardware) problems. Other things to try are setting periodic-calibration=enabled and disable default-forwarding. Are you throttling your traffic?
Network is clean. Small subnets routed through PC based MT and then on to Cisco 3640 edges. Torch on the wireless AP does not indicate anything out of the ordinary.
We have disabled default-forwarding and enabled periodic-calibration and still no change. I starting to suspect a potential defective CM9 card. Any other ideas appreciated…
Yes…we are throttling in the sense that we are setting AP Tx limit and Client Tx limits in the ACL…
Can you post what signal strengh, do you have with clients. your ap load your wireless configuration also have you tried different frame policy it works different in different scenaraios.
Regard Durim
Here is the reg table:
INTE... RADIO-NAME MAC-ADDRESS AP SIGNAL... TX-RATE
0 wlan1 X0 00:0B:6B:4D:77:A7 no -78dBm... 36Mbps
1 wlan1 X1 00:0B:6B:4D:77:E7 no -75dBm... 36Mbps
2 wlan1 X2 00:15:6D:10:22:68 no -73dBm... 24Mbps
3 wlan1 X3 00:0B:6B:4E:CF:0D no -78dBm... 36Mbps
4 wlan1 X4 00:15:6D:10:21:F3 no -68dBm... 36Mbps
5 wlan1 X5 00:0B:6B:4D:77:97 no -77dBm... 24Mbps
6 wlan1 X6 00:0B:6B:4D:77:3C no -76dBm... 24Mbps
7 wlan1 X7 00:0B:6B:36:0C:D4 no -75dBm... 36Mbps
8 wlan1 X8 00:0B:6B:4D:91:3D no -87dBm... 12Mbps
9 wlan1 X9 00:0B:6B:4D:77:55 no -76dBm... 36Mbps
10 wlan1 X11 00:0B:6B:4E:CF:C2 no -79dBm... 24Mbps
11 wlan1 X12 00:0B:6B:4D:95:B6 no -77dBm... 36Mbps
12 wlan1 X13 00:0B:6B:4E:D4:09 no -77dBm... 6Mbps
Currently Framer Policy is set to none with a Framer Limit being 3200. Whay would be a recommended policy???
I was reading a another post somewhere here on the forum in regards to bridging potentially causing high ping times. Could this also be the issue? I wouldn't think so with only 12 registered clients...
Until you get out a spectrum analyzer and prove otherwise, I would assume your high ping time is due to interference from another system.
Frequency scan show 0 usage. ![]()
Have you tryed to uncheck the supported rates of 54,48,36,24 and 18?
I only say this because I had a similer problem but with some older B clients in the mix and I had to set the mobe to B only on one of the APs also.
PS, The speed rate saw a tip from Sten.
I use the frame policy = best fit with framer limit 3200 (2200) but I would suggest to try all four framer policy, as jober sad try lowering supported data rates to 18MBps or 12MBps
Are you using Nstreme protocol also with standard WIFI client?
No…simply PTMP subscribers connected to our network…
i only heard this from someone else who tried to use wds to each customer;
dont. You add latency for each wds interface added.
I use the frame policy = best fit with framer limit 3200 (2200) but I would suggest to try all four framer policy, as jober sad try lowering supported data rates to 18MBps or 12MBps
Currently Framer Policy is set to none with a Framer Limit being 3200. Whay would be a recommended policy???
No…simply PTMP subscribers connected to our network…
Framer policy is used only with Nstreme protocol.
I use wds for each customers. And I have the same strange problem about long ping.
But I use PPPoE so to bridge my customers the manual says I have to use wds.
May you explain howto use pppoe for my customers (that are all MT based) without using wds?
Regards
Rosario
We changed our data rates and it did improve the ping times a bit. Still sporadic and I think that 30ms is still high for such a small network.
I guess routing is the next step BUT I already have MT PC based routers throughout the network and then Cisco edge routers…sooo adding another “router” into picture in my mind simply adds another unnecessary hop in the network.
The way that it is currently configured…the AP that is giving us grief is connected to the same switch that the MT PC based router is connected to and the clients use the PC based router as the gateway through the bridge that is configured in the AP.
IF I was to use “routing” in the AP, wouldn’t I simply set up a default gateway to the PC based router and then in the CPE set up a default gateway to the AP’s IP address OR would I have to let the AP “route” an entire subnet hence adding another hop?
Thanks for the replys!!!