AP:
MK112 with prism 2,5 card. 12 connectred clients. And latency si around 2-6 ms. It is very cool but not for long time. A rest of time the latency is around 150 - 400 ms.
If latency is 2-6 ms the throughput could be higher with no roblem. 1200 / 500 kbps
If latency is high the throughput coldn`t be higher than 300-400 kbps.
Defauld forward is disabled, broadcast is filtered with netbios, too.The connections are limited for 150 / user!
And the are a lot of droped packets!I tryed to change the frequency too. It is the same.
I tryed change ROS version. I tryed beta v. too. It is the same!
This problem is not only on thi one AP. I thought:the problem is witch cm9 wlan card.I changed it for Prism 2.5. It is the same.
Please help!!!!!
Where are you seeing packet drops ?Where are you seeing packet drops? How do you measure it?
What's you configuration?
cpu load is around 20 %What's the load at the time? What's the response time? Exactly what kind of client are you pinging? What is the AP wireless configuration?
name=" XXXXXXXX " mtu=1500 mac-address=00:02:6F:xx:xx:xx arp=enabled
disable-running-check=no interface-type=Prism prism-cardtype=100mW
radio-name="XXXXXXXX" mode=ap-bridge ssid="XXXXXXXX" area=""
frequency-mode=manual-txpower country=rusia antenna-gain=0
frequency=2427 band=2.4ghz-b scan-list=default rate-set=default
supported-rates-b=1Mbps,2Mbps basic-rates-b=1Mbps,2Mbps
max-station-count=2007 tx-power-mode=default
periodic-calibration=enabled periodic-calibration-interval=60
dfs-mode=none antenna-mode=ant-a wds-mode=disabled
wds-default-bridge=none wds-default-cost=100 wds-cost-range=50-150
wds-ignore-ssid=no update-stats-interval=disabled
default-authentication=yes default-forwarding=no default-ap-tx-limit=0
default-client-tx-limit=0 hide-ssid=no security-profile=default
disconnect-timeout=3s on-fail-retry-time=300ms compression=no
allow-sharedkey=no
You can get some helpful information by doubleclcking on an entry in the wireless/registration table and looking at the Statistics tab regarding what is happening below layer 3.AP:
And the are a lot of droped packets!I tryed to change the frequency too. It is the same.
If you cycle between times of good latency and poor latency, look for the cause of the cycle.MK112 with prism 2,5 card. 12 connectred clients. And latency si around 2-6 ms. It is very cool but not for long time. A rest of time the latency is around 150 - 400 ms.
The cycle between times of good latency and poor latency is not equal.Usualy the problems with poor latency are at night.If you cycle between times of good latency and poor latency, look for the cause of the cycle.MK112 with prism 2,5 card. 12 connectred clients. And latency si around 2-6 ms. It is very cool but not for long time. A rest of time the latency is around 150 - 400 ms.
A single cycle (a single occurrence) can be more difficult to diagnose than a repetitive cycle, but you wind up looking at the data to find out what changed (changes) at the inflection point(s) or executing a series of SWAGs.
Turn on wireless logging and look at the log file as well as the Statistics tab for particular connections under wireless/registration-table.
best regards/ldv
Were the ping times good or poor when you took that lab note?the severance betwen Tx/Rx Frames vx. TX/Rx HW Frames are monimal. RX frames are equal. TX is little different ...Very little
Were the ping times good or poor when you took that lab note?the severance betwen Tx/Rx Frames vx. TX/Rx HW Frames are monimal. RX frames are equal. TX is little different ...Very little
Whether good or bad, did you make a second lab note regarding the opposite condition?
If so, what was that result?
regards/ldv
the severance betwen Tx/Rx Frames vx. TX/Rx HW Frames are monimal. RX frames are equal. TX is little different ...Very little
Were the ping times good or poor when you took that lab note?
Whether good or bad, did you make a second lab note regarding the opposite condition?
If so, what was that result?
1. Please reply with lab notes regarding:Sorry, I don`t understand what you said
That is an old myth since before Atheros cards were plentiful.I heard so the best effort for AP whit MK is mini PCI card with prism 2,5 chipset.
I'll bet you $100 that John meant for you to key inSystem reboot helps no more than 5 minutes... Reboot is not solving !As usual, your rate settings are all messed up. A /system reset is probably easiest.
I'd like to suggest that you:The sameWhat is the configuration now then?
I'm not very confident this will be helpful to you, but some folks running Tranzeos wind up trying to solve certain problems by adjusting RTS and fragmentation thresholds to lower values. Lonnie N. has written quite a bit on his forum regarding the evils of low numbers which are thought to solve, e.g., the hidden node problem, but cause others. This situation can normally be detected by using 1500 byte pings.These are Tranzeo clients radios. In desperation I switched back to the Tranzeo AP and all if fine. It appears to me we still have an issue with compatability with some radio chipsets. Any thoughts?
How can I reduce upload on ap. What is the best effort?Post the version of the RouterOs used and the firmware of the RB112.
I have the same issue in the past, I have reduced the problem as follow:
1) update the firmware from 1.3 to the last 2.6
2) update the ROUTEROS to last
3) I have reduced the upload from the clients to internet. (for 50 customers from 2 Mbit to 600 kbits)
with this modification the download increase to 8 Mbit for sector.
In some sector I have switched from b-g to only b since I have GSM operator in the same roof.
Hi maxfava,3) I have reduced the upload from the clients to internet. (for 50 customers from 2 Mbit to 600 kbits)
with this modification the download increase to 8 Mbit for sector.