I have a point to point link with two WRAP boards with CM9 cards. The distance is about 3.5miles and signal is good -61 noise is -98, the tx rx rate is 54mbps on each side. When I do a bandwidth test I am only getting 13mbps TCP but I get 23 UDP? The CCQ is close to 100 when passing data. The CPU usage is only 30% so its not that. Anything else I can check? I am not using Nstream, it seemed to make it worse. One side is ap bridge other is station.

Hi n4dsl,

I'm not really seeing a lot wrong with your numbers. Can I turn the question around and ask what throughput you are expecting?

-Nelson

Well I was expecting close to 20mbps. The routerboard has two cards in it, one to connect to my internet source which is a 802.11g AP Dlink and the other to distribute to a remote site. When I do a bandwidth test from Mikrotik to Dlink I get about 20megs, but from Mikrotik to another Mikrotik 3.5 miles away I only get 13 megs even though they are both at 54mb rate. Don't you usually figure you should get half the rated speed?

If I connect my laptop to the Dlink AP I get 20megs as well, so should I not expect the same on the 3.5 mile link?

I am doing routing, would bridging yield higher throughput? When I do the bandwidth test it is from one mikrotik to another, so it shouldn't be going through any routing at that point.

You'll get cleaner results if you bandwidth test from devices on either side of the MT's...not using their internal BT service. Or at least get one of them out of the picture by going from a laptop on one side to the remote MT. You can download the MT bandwidth test soft client for your laptop from the website. I'd give that a try and see if your results remain the same or throughput looks a little better. I know you stated 100% ccq, but...how is latency both idle and under load? Low and stable or lots of fluctuation? -98 noise floor is not great...but probably there is little you can do about it.

-Nelson

last time i checked, recieve sensitivity on almost all 802.11 equipment is -97, sans canopy gear

how is -98 db noise floor poor?

so MTK -> MTK you are getting 13 megs UDP, or TCP? what method of testing are you using to verify this?

ROS Versions?

i dont fully understand your setup...

I was wondering the same thing about noise floor, -98 is fine in my book. I am using 4.17, and have tried 5.4 as well, same results. I have tested with PC on one end with same results.

please post your config from both devices.

From Terminal:
so you have

Internet <- Wlan1 > MTK1 Wlan2 -> MTK2 ?

you could be interfering with yourself if all this is on 2ghz.

Here is config from first AP at home
[admin@MikroTik] > interface wireless print advanced
Flags: X - disabled, R - running
0 R name="wlan1" mtu=1500 mac-address=00:0B:6B:34:19:71 arp=enabled disable-running-check=no
interface-type=Atheros AR5213 radio-name="000B6B341971" mode=station ssid="houselink" area=""
frequency-mode=manual-txpower country=no_country_set antenna-gain=0 frequency=2437 band=2.4ghz-b/g
scan-list=default rate-set=default supported-rates-b=1Mbps,2Mbps,5.5Mbps,11Mbps
supported-rates-a/g=6Mbps,9Mbps,12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,54Mbps basic-rates-b=1Mbps
basic-rates-a/g=6Mbps max-station-count=2007 ack-timeout=dynamic tx-power-mode=default
noise-floor-threshold=default periodic-calibration=default periodic-calibration-interval=60
burst-time=disabled 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=yes default-ap-tx-limit=0 default-client-tx-limit=0
proprietary-extensions=post-2.9.25 wmm-support=disabled hide-ssid=no security-profile=atrs
disconnect-timeout=3s on-fail-retry-time=100ms preamble-mode=both compression=no allow-sharedkey=no
station-bridge-clone-mac=00:00:00:00:00:00 hw-retries=7 frame-lifetime=0 adaptive-noise-immunity=none
hw-fragmentation-threshold=disabled hw-protection-mode=none hw-protection-threshold=0 frequency-offset=0

1 R name="wlan2" mtu=1500 mac-address=00:0B:6B:34:B4:85 arp=enabled disable-running-check=no
interface-type=Atheros AR5213 radio-name="000B6B34B485" mode=ap-bridge ssid="mtn" area=""
frequency-mode=superchannel country=no_country_set antenna-gain=0 frequency=2462 band=2.4ghz-b/g
scan-list=default rate-set=default supported-rates-b=1Mbps,2Mbps,5.5Mbps,11Mbps
supported-rates-a/g=6Mbps,9Mbps,12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,54Mbps basic-rates-b=1Mbps
basic-rates-a/g=6Mbps max-station-count=2007 ack-timeout=dynamic tx-power-mode=default
noise-floor-threshold=default periodic-calibration=default periodic-calibration-interval=60
burst-time=disabled 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=yes default-ap-tx-limit=0 default-client-tx-limit=0
proprietary-extensions=post-2.9.25 wmm-support=disabled hide-ssid=no security-profile=atrs
disconnect-timeout=3s on-fail-retry-time=100ms preamble-mode=both compression=no allow-sharedkey=no
station-bridge-clone-mac=00:00:00:00:00:00 hw-retries=7 frame-lifetime=0 adaptive-noise-immunity=none
hw-fragmentation-threshold=disabled hw-protection-mode=none hw-protection-threshold=0 frequency-offset=0
[admin@MikroTik] >

Then here is config from mountain top ap

[admin@MikroTik] > interface wireless print advanced
Flags: X - disabled, R - running
0 R name="wlan2" mtu=1500 mac-address=00:0B:6B:33:0E:CB arp=enabled disable-running-check=no
interface-type=Atheros AR5213 radio-name="000B6B330ECB" mode=station ssid="mtn" area=""
frequency-mode=manual-txpower country=no_country_set antenna-gain=0 frequency=2462 band=2.4ghz-b/g
scan-list=default rate-set=default supported-rates-b=1Mbps,2Mbps,5.5Mbps,11Mbps
supported-rates-a/g=6Mbps,9Mbps,12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,54Mbps basic-rates-b=1Mbps
basic-rates-a/g=6Mbps max-station-count=2007 ack-timeout=dynamic tx-power-mode=default
noise-floor-threshold=default periodic-calibration=default periodic-calibration-interval=60
burst-time=disabled 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=yes default-ap-tx-limit=0 default-client-tx-limit=0
proprietary-extensions=post-2.9.25 wmm-support=disabled hide-ssid=no security-profile=atrsmtn
disconnect-timeout=3s on-fail-retry-time=100ms preamble-mode=both compression=no
allow-sharedkey=no station-bridge-clone-mac=00:00:00:00:00:00 hw-retries=7 frame-lifetime=0
adaptive-noise-immunity=none hw-fragmentation-threshold=disabled hw-protection-mode=none
hw-protection-threshold=0 frequency-offset=0

1 name="wlan1" mtu=1500 mac-address=00:15:6D:69:57:AC arp=enabled disable-running-check=no
interface-type=Atheros AR5413 radio-name="00156D6957AC" mode=ap-bridge ssid="apmtn" area=""
frequency-mode=superchannel country=no_country_set antenna-gain=0 frequency=2412 band=2ghz-10mhz
scan-list=default rate-set=default supported-rates-b=1Mbps,2Mbps,5.5Mbps,11Mbps
supported-rates-a/g=6Mbps,9Mbps,12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,54Mbps basic-rates-b=1Mbps
basic-rates-a/g=6Mbps max-station-count=2007 ack-timeout=dynamic tx-power-mode=default
noise-floor-threshold=default periodic-calibration=default periodic-calibration-interval=60
burst-time=disabled 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=yes default-ap-tx-limit=0 default-client-tx-limit=0
proprietary-extensions=post-2.9.25 wmm-support=disabled hide-ssid=no security-profile=443150
disconnect-timeout=3s on-fail-retry-time=100ms preamble-mode=both compression=no
allow-sharedkey=no station-bridge-clone-mac=00:00:00:00:00:00 hw-retries=7 frame-lifetime=0
adaptive-noise-immunity=none hw-fragmentation-threshold=disabled hw-protection-mode=none
hw-protection-threshold=0 frequency-offset=0

[admin@MikroTik] >

I shouldn't be interfering as I am using channel 11 and 1 alternating.
Here is a diagram of network, this should help you.

I agree that -98 noise is fine. I would just prefer better than fine when it can be had. If you're reading a -98 that means there is a modest amount of background 2.4 traffic and you'll inevitably have intermittant "shouts" that are louder than -98 from those rogue devices. I admit we're pretty spoiled in my area. We're very rural and noise floors are usualy above 100 or in the 11-teens.

That said, is running this link in 5.8 a possibility? There are a lot more channels to work with and it's almost always a more forgiving noise environment. To some degree you also get away from being one step removed from a bad situation when your neighbor puts up a new 2.4 radio (or microwave oven, garage door opener, baby monitor...etc). That's really the trouble with the 2.4 band. Even if you squeeze another 5mbit out of this link with fine tuning, it could all go away next week because of elements you have no control over. Not that you fully control 5.8...but you have a lot more "flex".

-Nelson

Well, your configurations look fine. And the map is great!

To answer some previous questions:

Yes, Bridging will be faster. can be quite a bit faster.

Generally speaking, you tend to get half of the air rate, yes.


I am now on to wondering about your CPU usage under a TCP test.

If it were me, i would try MPLS tunneling between the two wrap boards. Have you ever set

one up?

http://wiki.mikrotik.com/wiki/Transpare ... using_MPLS

This can improve speeds over backhaul links, and lower cpu usage.

It seems to me like your bandwidth is actually pretty good. now some questions about your testing methods:

have you have monitored CPU usage while testing from

PC -> Mountain site? With that first wrap relaying data, could it be maxing out on a tcp test?

Are you using the windows bandwidth test utility? (Btest.exe) ?

Another question now:

If you are concerned with bandwidth to your mountain site, why are you using a 10 mhz

channel to your end point? that is going to be your bottleneck 100% of the time

Also, have you ever tried manually setting your ack timeouts? have you tried NV2 ?

and lastly, I would definitely give bridging a try in this scenario!

-Brad

I just did a test with two wrap boards in the lab. With routing I got 13.5megs TCP from PC to PC. CPU usage was 100%. I then used the MPLS bridging method and still got same speed but CPU usage was around 50 to 70%. So is this is realistic number? Seems weird that I can get 17 from a DD-wrt wap to Mikrotik WRAP board, but then from Mikrotik to Mikrotik I can only get 13.5 megs.

I could not get WDS to work? If I put ap in bridge mode and client in Wds station it never connects, am I missing something?

The reason I have a 10mhz channel at Mountain is due to interference. I realize that is a bottleneck, but I have plans to maybe add a 5.8 sector at some point and want to know why my backhaul link to mountain is slower than it seems it should be. Don't really need the bandwidth at this point, but more of principal at this point.

At this point I am wondering if WRAP speed is limiting. What is the most throughput someone has gotten through these? I thought they were spec for 25mb at least?

I do not know if your test is LAN to LAN, 802.11g in all tests I did not give you more than 22Mbps half duplex with Protcol udp and tcp protocol will get less because this is three ways before establishing a communication, making it slower.
when evaluating a wireless link must take into account that the troughput never be equal to the physical velocity in the air, in this case 54mbps, because the data that goes in the air are added parameters to control the transmitting data reducing so its ability to transfer information from one point to another. that's why you'll never achieve more traffic you're getting.
if you want to achieve more traffic you must change to 802.11n.
Greetings from Nicaragua

if you want to achieve more traffic you must change to 802.11n.
Greetings from Nicaragua

What traffic speed can I get from 802.11n?

Thanks in advance from Dominican Republic.

Yo he hecho pruebas en el campo y he llegado a obtener hasta 30mbps full duplex aproximadamente 65mbps en half duplex, esto es pruebas de lan a lan y utilizando doble polaridad a unos 20km aprox, si quieres obtener mas puedes utilizar nv2 y a 40mhz. Por cierto con la version 5.7 se ha mejorado el protocolo nv2 aunque tiene el problema del reinicio del puerto ethernet, te recomiendo que lo actualizes a 5.7, pero el firmware no lo actualices dejalo en uno diferente a la version 2.29 que es en la que he visto ese problema, y prueba nv2, obtendras mayor ancho de banda en ese protocolo.

I have been tested in the field and I have to get up to about 30mbps full duplex and 60Mbps half duplex, this LAN to LAN tests using dual polarity and about 20km approx, if you want more you can use NV2 and 40MHz. Of course with the version 5.7 has improved although NV2 protocol has the port flaping the ethernet port, I recommend that you upgrade to 5.7, but the firmware update did not leave in a version different from the 2.29 that is where I seen that problem, and NV2 test, you will get more bandwidth to that protocol.
saludos.

You are probably maxing out the CPU of the wrap boards by using the internal MT server.

Use the MT server on a PC and do a speed test to another BT server connected to far end PC.

Yo he hecho pruebas en el campo y he llegado a obtener hasta 30mbps full duplex aproximadamente 65mbps en half duplex, esto es pruebas de lan a lan y utilizando doble polaridad a unos 20km aprox, si quieres obtener mas puedes utilizar nv2 y a 40mhz. Por cierto con la version 5.7 se ha mejorado el protocolo nv2 aunque tiene el problema del reinicio del puerto ethernet, te recomiendo que lo actualizes a 5.7, pero el firmware no lo actualices dejalo en uno diferente a la version 2.29 que es en la que he visto ese problema, y prueba nv2, obtendras mayor ancho de banda en ese protocolo.

I have been tested in the field and I have to get up to about 30mbps full duplex and 60Mbps half duplex, this LAN to LAN tests using dual polarity and about 20km approx, if you want more you can use NV2 and 40MHz. Of course with the version 5.7 has improved although NV2 protocol has the port flaping the ethernet port, I recommend that you upgrade to 5.7, but the firmware update did not leave in a version different from the 2.29 that is where I seen that problem, and NV2 test, you will get more bandwidth to that protocol.
saludos.

Thanks a lot for the information
Muchisimas gracias por la informacion

(y)

i used wan killer of solarwins and ftp trafic for my test.