5213 distance issues w/ .17 software

jonbrewer · Wed Oct 13, 2004 12:00 pm

Hi Folks,

Installed a new two-hop system this week and am having serious throughput and latency issues. What's funny is I tested the system in the lab before deploy and had no such issues - in fact had throughput over two hops to 15mbps full-duplex.

System uses 5213 radios (DLink AG530, used with much success in .13 software release) Hop 1 at 5340 and hop 2 at 5260.

Now the system is in the field - hop 1 at 1.5km, hop 2 at 300M (difficult territory in NZ, need to have multihop) and the latency is 3-400ms and throughput down to sub 1mbps.

Signal strength is ok (~75) but less than expected. Connects at 36 or 48mbps. It's got to be software. I look like an ass 'cause I've been fscking around with this for a week and it's still crap.

I've never done a downgrade. Is this the only answer? How could I do it? Would it be possible to downgrade to .13 without visiting all three sites again?

Would appreciate advice / feedback ASAP.

Cheers...

jonbrewer · Wed Oct 13, 2004 12:08 pm

Additional info: have tried both with and without nstreme -no difference. Started on .16 release, upgraded to .17 release in the field when .16 turned out to be crap at distance. As I said before, it worked fine in the lab, so I think it's all about distance.

Michaelg · Wed Oct 13, 2004 3:33 pm

You can downgrade your system by uploading the packages you want via ftp. then in terminal window;

/system package downgrade

After that just reboot your system

jonbrewer · Wed Oct 13, 2004 9:46 pm

You can downgrade your system by uploading the packages you want via ftp. then in terminal window;
Code: Select all
/system package downgrade
After that just reboot your system

Yes but after a downgrade from .17 wireless using nstreme to .13 (last one I know to work) wireless, will all the settings be gone? Do I need to make three site visits to do this?

[ASM] · Wed Oct 13, 2004 10:01 pm

Set the stations to 802.11a and then install the wireless-legacy package... See if there is a better link speed

jonbrewer · Thu Oct 14, 2004 6:23 am

Set the stations to 802.11a and then install the wireless-legacy package... See if there is a better link speed

This helps quite a bit. Latency goes from 3-400ms over two hops down to 10-50ms. Throughput is ok on the second hop (10mbps/10mbps), 300Meters, but on the first hop is crap, avg. 350k/1.5mbps send/receive

This, of course, is exactly opposite of what a customer would want.

Can't say I had these problems on .13. Still thinking of downgrading and would like to know if anyone has done it.

jonbrewer · Thu Oct 14, 2004 6:23 am

Set the stations to 802.11a and then install the wireless-legacy package... See if there is a better link speed

This helps quite a bit. Latency goes from 3-400ms over two hops down to 10-50ms. Throughput is ok on the second hop (10mbps/10mbps), 300Meters, but on the first hop is crap, avg. 350k/1.5mbps send/receive

This, of course, is exactly opposite of what a customer would want.

Can't say I had these problems on .13. Still thinking of downgrading and would like to know if anyone has done it.

[ASM] · Thu Oct 14, 2004 12:27 pm

I had the same issue with AR5211 It was because of low signal strenght. N-Streme works very good with signal strenght of -65 dBm or bellow

ttiwireless · Thu Oct 14, 2004 8:24 pm

jonbrewer -

I am having similar problems with Atheros 5.8GHz. I have tried versions .15, .16, .17. Would like to try .13. Do you have the .13 download that you can send to me or place on an ftp server so I can download? My email is dale.albright@ttiwireless.com.

Thanks - Dale

Michaelg · Thu Oct 14, 2004 9:26 pm

Dale: 2.8.13 is in your mailbox...

My experince with 2.8.17;

Latency problems.
Big problems using RB14 (Wireles disconnects every 1 minute)
Wireless disconnects on hevy load.
Signal strength jumps up and down, changing wireless rate.

jonbrewer · Thu Oct 14, 2004 10:50 pm

Set the stations to 802.11a and then install the wireless-legacy package... See if there is a better link speed
This helps quite a bit. Latency goes from 3-400ms over two hops down to 10-50ms. Throughput is ok on the second hop (10mbps/10mbps), 300Meters, but on the first hop is crap, avg. 350k/1.5mbps send/receive

This, of course, is exactly opposite of what a customer would want.

Can't say I had these problems on .13. Still thinking of downgrading and would like to know if anyone has done it.

Update: one of the three stations was still using wireless instead of wireless legacy. Now all three are using wireless legacy and I have 9mbps full-duplex (TCP 400byte packets) over two hops, avg. latency 1ms at idle, 40ms at 60% load.

What a PITA to get going though. Miktotik, guys, what's up with these drivers?

[ASM] · Fri Oct 15, 2004 12:00 am

I'm not sure where the problem could be. I have ping latency of 1-2 ms at 12 km link with packet size of 1500. Using n-streme I have 2-4 ms but doubled throughput (46 MBs at tcp bandwidth test). Signal strenght about -63 dBm

5213 distance issues w/ .17 software

5213 distance issues w/ .17 software

5213 and distance issue update

.17 update

Who is online