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.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.
Until you get out a spectrum analyzer and prove otherwise, I would assume your high ping time is due to interference from another system.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...????
Have you tryed to uncheck the supported rates of 54,48,36,24 and 18?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...
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 12MBpsHere 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...
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???
Framer policy is used only with Nstreme protocol.No...simply PTMP subscribers connected to our network...
I use wds for each customers. And I have the same strange problem about long ping.i only heard this from someone else who tried to use wds to each customer;
dont. You add latency for each wds interface added.
25 packets transmitted, 25 packets received, 0% packet loss
round-trip min/avg/max = 5/6.7/15 ms
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.Yes...we are throttling in the sense that we are setting AP Tx limit and Client Tx limits in the ACL
Removed the AP Tx and Client Tx limits from all associated CPE's and still horrible ping times.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:This is on 5GHz to Routeboards with 2 radios (the other is 2.4GHz).Code: Select all25 packets transmitted, 25 packets received, 0% packet loss round-trip min/avg/max = 5/6.7/15 ms
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.Yes...we are throttling in the sense that we are setting AP Tx limit and Client Tx limits in the ACL
Ack Timeout on the AP is set to dynamic. We are running in 5GHz with a single 120 degree 16 dbi sector.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?
Jober: What i tried to say was:Have you tryed to uncheck the supported rates of 54,48,36,24 and 18?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...
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.
Here's output for the first 2 CPE's: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?
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:How much traffic is on the link while you test?
Yes to question about searching according to scan-list.
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.From the 2 clients:
tx-ccq=36% rx-ccq=55%
tx-ccq=35% rx-ccq=54%
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?1 interface=wlan1 radio-name="X1"
uptime=1h29m38s
strength-at-rates=-76dBm@6Mbps 30ms,-75dBm@9Mbps 15s520ms,-76dBm@12Mbps 30ms
perhaps you should let the cpe do the pppoe ?I use wds for each customers. And I have the same strange problem about long ping.i only heard this from someone else who tried to use wds to each customer;
dont. You add latency for each wds interface added.
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
tx rate times are times since last use of that tx rate i guess.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?
We're using Rootenna cases with 19dbi integrated for the CPE's. Here's output: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.From the 2 clients:
tx-ccq=36% rx-ccq=55%
tx-ccq=35% rx-ccq=54%
As a side note and slightly off-topic, consider the values of output posted: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?1 interface=wlan1 radio-name="X1"
uptime=1h29m38s
strength-at-rates=-76dBm@6Mbps 30ms,-75dBm@9Mbps 15s520ms,-76dBm@12Mbps 30ms
We're operating in 5GHz...I don't think Frequency Scan will show non-802.11 systems using the frequencies. Can someone from Mikrotik comment please?Frequency scan show 0 usage.
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
Per the diagram, we use the network 10.10.0.0/22 for all of our clients....for management purposes. Is there any way to make use of that network on the client side to add "routing" to the picture instead of WDS? Like I said...for some reason I'm NOT seeing how to make it work....I suggest the follow
RB532 Ether. 10.0.0.1/24 - default getway (your modem or server) --
RB532 Wireless 10.0.1.254/24
Client must in the network 10.0.1.X/24 with default gataway 10.0.1.254
Max
MT reports that the noise floor and thus SNR measurements are accurate and take into account ALL transmissions at that particular time... Alvarion, Canopy, Orthogon, etc.I don't think Frequency Scan will show non-802.11 systems using the frequencies. Can someone from Mikrotik comment please?Frequency scan show 0 usage. :roll:
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
No I have not. Good idea. I added a filter for P2P but it filtered 0 packets in an 12 hour period.jd6strings,
have you tried to insert a firewall rule that drop invalid connection, accept related and valid? instead of accept all?
I tried this yesterday and at first time it works, but response will be tonight after 24 hours.
Actually we changed channels and I could NOT get the clients to re-associate. I was under the impression that the clients would use the default scan-list to find the AP with the associated SSID if NO country was selected. That did NOT happen. Maybe I've misconfigured something??? How long does the re-association process normally take after changing channels? I waited approx 3 minutes and 0 registration....Did you ever try testing out other channels? What do ping tests and bandiwdth tests look like at 2AM? What does the registration table and the reg stat look like early in the morning?
I still think your problem is RF related. Based on your registration table, some of the link's signal strengths, and the ccq readings reported, I'm not sure if switching to routing is going to change anything. I've been wrong many times tho so you never know
Also, I don't think the wireless sniffer accounts for RF that isn't 802.11 or some variation (like proprietary wireless, cordless phones, Sat, etc)...can anyone confirm this?
/ip firewall filter
add chain=forward protocol=tcp connection-state=invalid \
action=drop comment="drop invalid connections"
add chain=forward connection-state=established action=accept \ comment="allow already established connections"
add chain=forward connection-state=related action=accept \
comment="allow related connections"
Thanks for the repy. I actually found it in the manual right after I posted...thanks again. We are NOT using point-to-point tunneling. Why do you ask?from the manual
jd6stringsCode: Select all/ip firewall filter add chain=forward protocol=tcp connection-state=invalid \ action=drop comment="drop invalid connections" add chain=forward connection-state=established action=accept \ comment="allow already established connections" add chain=forward connection-state=related action=accept \ comment="allow related connections"
Also are you using pptp connection between you customers and server?
I'll give that a try. Thanks! By the way do you use WDS in your PTMP configuration?jd6strings
Try turning off the nstreme on the AP and the clients, We have found this to overload the RB532 too much and cause high pings and all sorts of other troubles in a point to multipoint configuration.
Hope it helps you.
Regards
Albie
I wrote about high ping issue.What do you mean by this? Do you mean re-association issues?
No, we don't use wds, increases load and decreases throughput.jd6strings
I'll give that a try. Thanks! By the way do you use WDS in your PTMP configuration?
Let your cpe do the pppoe connections.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?i only heard this from someone else who tried to use wds to each customer;
dont. You add latency for each wds interface added.
Yep..and create a default gateway in the CPE to your AP. Then create a default gateway on your AP to the next hop in your network (i.e. intermediary router, edge router, etc.).So you would just set the CPE to "station" and the AP to "AP Bridge" and route the traffic between the two WLAN interfaces?