Rocket M5 7.5Km PTPlink

[Commander Mittens]

not sure if creating a new thread is the right thing
but here goes i picked up a pair of rocket m5 and 30dbi Rocket Dish Antennas
to replace a trango link 45 the ones with the integrated 23 dbi antenna i had basically wanted more throughput
the trango link 45 was running in 5735 H polar for last year with no problems
but as the site feeds several other pop sites its come time to give the site a bit more bandwidth so original idea was to put the rocket 5's into low power channel and get the
full 40 mhz channel however because the power cant be lowered beyond 8dbi without
attenuators ive put it where the link 45 was in a 20mhz channel so far so good
first thing i noticed once radios were up was the ht chains have very different signal
on ht 1 i was getting -88 and on ht 0 -66 at 8dbm of input
when i upped it step by step this didn't change until i hit 20dbm then it went to -55 -55
on both chains what could cause this ? (is the power uneven till a certain point ?)
so not so much of a issue as 20dbm is fine just a little overkill for the distance
but my main issue is that throughput is good but... here it comes the latency
goes all over the place as in it averages around 2ms but every few minutes
itll go to like 2400ms theres no drop on the wireless but traffic crawls for a few seconds
then goes back to 2ms i found this to be loads worse with airmax enabled once disabled
latency is better but it still skyrockets every few minutes for a few seconds
before stabilizing in attempt to overcome this i thought ill lower the data rate works a treat for n5's from auto to anything lower but this does not work once set to anything other than auto the radios refuse to associate so they have to be left to auto least for now
also the ack does not seem to match and tends to greatly vary from 100 odd down to 60
they cant seem to make up there mind where they want to sit
so in summary does any one have a clue where i could be going wrong with these
the throughput seems to well exceed that of a trango link 45 but the latency issue seems to have me stuck to the point where im considering putting the link 45 back although im utterly loath to but unless i can come up with a way to make them more usable i feel i might be stuck doing that as this latency breaks voip calls and theres alot of voip clients behind this link and this didn't exist with the link 45 also i have site surveyed with a wispy dbx and i cannot see any interference i even stuck it into the dish to c if it could pick any noise and there isn't thankfully with the rocket m5 channel wise sits where its supposed to and its clean from what i can tell so im guessing its config or firmware
any thoughts would be greatly appreciated
these are gps coordinates to sites
AP WDS mode
36°48'56.26"S
175° 4'58.93"E

Station WDS Mode
36°47'36.64"S
175° 0'14.44"E

(am i being a muppet or is something just not right)

[Barlennan]

Maker sure you have the 5.0.2 firmware on both sides. Some of the signal strength reporting isn't 100% accurate yet either. And you probably noticed that the noise floor is always at -96 this doesn't mean the channel is clean right now it just always reports and -96. Set your ack first and don't worry about any of the other stuff until they get it fixed in a later firmware... Sounds like most of your problem is auto ack. They haven't fixed it yet so set it manually to 125% of distance. Had a similar problem with my 9 mile link until I set the ack manually on both sides.

[Commander Mittens]

ive set the ack to 82 9.3 seems to be a bit better im still seeing ccq at times go down to 58% but at least its getting to 100% usualy hovering at 80-90% main thing is latency seems to be where it should be nice and low now thankyou
could wpa2 be affecting the ccq ?
Packets: Sent = 22840, Received = 22840, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 17ms, Average = 3ms

[UBNT-Mike.Ford]

ive set the ack to 82 9.3 seems to be a bit better im still seeing ccq at times go down to 58% but at least its getting to 100% usualy hovering at 80-90% main thing is latency seems to be where it should be nice and low now thankyou
could wpa2 be affecting the ccq ?
Packets: Sent = 22840, Received = 22840, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 17ms, Average = 3ms


Hello,

Can you measure the CCQ while running a 2 minute traffic saturation test?

Thanks,

MIke

[Commander Mittens]

i moved radio last night to 5300 so there was no other radios nearby worked fine for nine hours then the rocket in station mode disconnected and just sat there associating and disassociating until i reboot it something is not really right
on a 2 minute link test i get varying throughput from 40m tcp down to 6m ccq tends to stay around 80% and moves between 100% and 55% but this radio getting stuck in a association cycle is a bit disturbing i didn’t reboot other end just station end to get it working again but I’m positive it’s not a noise issue

this is config of the rocket back in 5735
aaa.1.br.devname=br0
aaa.1.devname=ath0
aaa.1.driver=madwifi
aaa.1.ssid=YNETLNK
aaa.1.status=disabled
aaa.1.wpa.1.pairwise=CCMP
aaa.1.wpa.key.1.mgmt=WPA-PSK
aaa.1.wpa.psk=historysuxass
aaa.1.wpa=2
aaa.status=disabled
bridge.1.devname=br0
bridge.1.fd=1
bridge.1.port.1.devname=eth0
bridge.1.port.1.status=enabled
bridge.1.port.2.devname=ath0
bridge.1.port.2.status=enabled
bridge.1.port.3.devname=eth1
bridge.1.port.3.status=enabled
bridge.1.stp.status=disabled
bridge.status=enabled
dhcpc.1.devname=br0
dhcpc.1.fallback=192.168.1.20
dhcpc.1.status=disabled
dhcpc.status=disabled
dhcpd.1.status=disabled
dhcpd.status=disabled
dnsmasq.1.devname=eth0
dnsmasq.1.status=enabled
dnsmasq.status=disabled
ebtables.1.cmd=-t nat -A PREROUTING --in-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.1.status=disabled
ebtables.2.cmd=-t nat -A POSTROUTING --out-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.2.status=disabled
ebtables.3.cmd=-t broute -A BROUTING --protocol 0x888e --in-interface ath0 -j DROP
ebtables.3.status=disabled
ebtables.50.status=disabled
ebtables.51.status=disabled
ebtables.52.status=disabled
ebtables.status=enabled
gui.language=en_US
httpd.https.status=disabled
httpd.port.http=80
httpd.port=80
httpd.status=enabled
igmpproxy.status=disabled
iptables.3.status=disabled
iptables.status=disabled
netconf.1.alias.1.status=disabled
netconf.1.alias.2.status=disabled
netconf.1.alias.3.status=disabled
netconf.1.alias.4.status=disabled
netconf.1.alias.5.status=disabled
netconf.1.alias.6.status=disabled
netconf.1.alias.7.status=disabled
netconf.1.alias.8.status=disabled
netconf.1.devname=eth0
netconf.1.ip=0.0.0.0
netconf.1.netmask=255.255.255.0
netconf.1.promisc=enabled
netconf.1.status=enabled
netconf.1.up=enabled
netconf.2.alias.1.status=disabled
netconf.2.alias.2.status=disabled
netconf.2.alias.3.status=disabled
netconf.2.alias.4.status=disabled
netconf.2.alias.5.status=disabled
netconf.2.alias.6.status=disabled
netconf.2.alias.7.status=disabled
netconf.2.alias.8.status=disabled
netconf.2.allmulti=disabled
netconf.2.devname=ath0
netconf.2.ip=0.0.0.0
netconf.2.netmask=255.255.255.0
netconf.2.promisc=enabled
netconf.2.status=enabled
netconf.2.up=enabled
netconf.3.autoip.status=enabled
netconf.3.devname=br0
netconf.3.ip=172.27.253.104
netconf.3.netmask=255.255.0.0
netconf.3.status=enabled
netconf.3.up=enabled
netconf.status=enabled
netmode=bridge
ntpclient.status=disabled
ppp.1.password=
ppp.1.status=disabled
ppp.status=disabled
pwdog.status=disabled
radio.1.ack.auto=disabled
radio.1.ackdistance=9300
radio.1.acktimeout=83
radio.1.ampdu.bytes=50000
radio.1.ampdu.frames=32
radio.1.ampdu.status=enabled
radio.1.chanshift=0
radio.1.clksel=1
radio.1.countrycode=511
radio.1.cwm.enable=0
radio.1.cwm.mode=0
radio.1.devname=ath0
radio.1.dfs.status=
radio.1.forbiasauto=0
radio.1.frag=off
radio.1.freq=5735
radio.1.ieee_mode=11naht20
radio.1.mcastrate=
radio.1.mode=master
radio.1.polling=disabled
radio.1.rate.auto=enabled
radio.1.rate.mcs=auto
radio.1.rts=off
radio.1.status=enabled
radio.1.subsystemid=0xe105
radio.1.thresh62a=
radio.1.thresh62b=
radio.1.thresh62g=
radio.1.txpower=22
radio.countrycode=511
radio.status=enabled
resolv.host.1.name=Airfield-APBridge
resolv.host.1.status=enabled
resolv.nameserver.1.ip=0.0.0.0
resolv.nameserver.1.status=enabled
resolv.nameserver.2.status=disabled
resolv.status=enabled
route.1.devname=br0
route.1.gateway=172.27.254.254
route.1.ip=0.0.0.0
route.1.netmask=0
route.1.status=enabled
route.status=enabled
snmp.community=ynetpublic997
snmp.contact=felix
snmp.location=airfield
snmp.status=disabled
sshd.port=22
sshd.status=enabled
syslog.remote.status=
syslog.status=enabled
telnetd.status=disabled
tshaper.status=disabled
users.1.name=ubnt
users.1.password=VvpvCwhccFv6Q
users.1.status=enabled
users.2.status=disabled
users.status=enabled
wireless.1.addmtikie=enabled
wireless.1.ap=
wireless.1.authmode=1
wireless.1.autowds=disabled
wireless.1.compression=0
wireless.1.devname=ath0
wireless.1.fastframes=0
wireless.1.frameburst=0
wireless.1.hide_ssid=enabled
wireless.1.l2_isolation=enabled
wireless.1.mac_acl.1.mac=00:15:6D:DC:BF:E0
wireless.1.mac_acl.1.status=enabled
wireless.1.mac_acl.10.mac=
wireless.1.mac_acl.10.status=disabled
wireless.1.mac_acl.11.mac=
wireless.1.mac_acl.11.status=disabled
wireless.1.mac_acl.12.mac=
wireless.1.mac_acl.12.status=disabled
wireless.1.mac_acl.13.mac=
wireless.1.mac_acl.13.status=disabled
wireless.1.mac_acl.14.mac=
wireless.1.mac_acl.14.status=disabled
wireless.1.mac_acl.15.mac=
wireless.1.mac_acl.15.status=disabled
wireless.1.mac_acl.16.mac=
wireless.1.mac_acl.16.status=disabled
wireless.1.mac_acl.2.mac=00:15:6D:DD:BF:E0
wireless.1.mac_acl.2.status=enabled
wireless.1.mac_acl.3.mac=
wireless.1.mac_acl.3.status=disabled
wireless.1.mac_acl.4.mac=
wireless.1.mac_acl.4.status=disabled
wireless.1.mac_acl.5.mac=
wireless.1.mac_acl.5.status=disabled
wireless.1.mac_acl.6.mac=
wireless.1.mac_acl.6.status=disabled
wireless.1.mac_acl.7.mac=
wireless.1.mac_acl.7.status=disabled
wireless.1.mac_acl.8.mac=
wireless.1.mac_acl.8.status=disabled
wireless.1.mac_acl.9.mac=
wireless.1.mac_acl.9.status=disabled
wireless.1.mac_acl.policy=allow
wireless.1.mac_acl.status=enabled
wireless.1.macclone=disabled
wireless.1.scan_list.status=disabled
wireless.1.security=none
wireless.1.signal_led1=94
wireless.1.signal_led2=80
wireless.1.signal_led3=73
wireless.1.signal_led4=65
wireless.1.ssid=YNETLNK
wireless.1.status=enabled
wireless.1.wds.1.peer=
wireless.1.wds.2.peer=
wireless.1.wds.3.peer=
wireless.1.wds.4.peer=
wireless.1.wds.5.peer=
wireless.1.wds.6.peer=
wireless.1.wds=enabled
wireless.1.wmm=enabled
wireless.1.wmmlevel=
wireless.status=enabled
wpasupplicant.device.1.profile=
wpasupplicant.device.1.status=disabled
wpasupplicant.profile.1.name=
wpasupplicant.profile.1.network.1.bssid=
wpasupplicant.profile.1.network.1.eap.1.status=disabled
wpasupplicant.profile.1.network.1.key_mgmt.1.name=
wpasupplicant.profile.1.network.1.psk=

wpasupplicant.status=disabled

[Barlennan]

I thought it was just a quirk with my setup but mine would do the same thing, sync up work good for anywhere from 4hrs to a day and then one side would lock up. Weird thing is they both said they were still associated but the signal strength was reporting terrible and they were not passing data, until I set the rate lower on both sides and turned auto best off. I have it on a 40mhz channel and set to mcs4 seemed to solve the disassociation problem it probably doesn't need to be locked at mcs4 might be able to push it higher, but I'd start around mcs3 and step it up after it consistently works for a while.

[Commander Mittens]

locking data rate makes my link totaly fail i hav to leave on auto for some reason tried to throw it to mcs3 but it just went into association loop unit it was set back
pretty odd further mucking round tho i found if i set it to mcs15 the highest
ccq sits 100% and so far link is rock solid so finally it looks like i might have this sorted
thanks for responses ill post a update in a couple of days on how it runs
side note if i set link to anything lower than mcs15 link either goes into loop or ccq drops very badly

[UBNT-Edmundas]

Wireless driver developers are working to get wireless lockups fixed, which appears when AirMax is disabled. As a temporally solution I do recommend to configure ping watchdog script on Station to the AP's IP address. It will initiate devices reboot to get wireless link working again.

-Edmundas

[vicenteroca]

More loockups?!
:(

[Commander Mittens]

what would be your recommended ping interval
for ping watchdog script
Just noticed but the bridge table is pretty big how large can they get before problems happen
this is bridge table after 3 hours
MAC Address Interface Ageing Timer
00:01:DE:00:57:7B LAN 4.88
00:01:DE:00:57:7C LAN 16.83
00:01:DE:10:E1:89 LAN 292.11
00:01:DE:12:64:8A LAN 1.78
00:01:DE:12:65:92 LAN 19.64
00:01:DE:12:66:68 LAN 24.16
00:01:DE:12:88:29 LAN 5.25
00:01:DE:12:96:CA LAN 5.26
00:01:DE:1E:E2:34 LAN 2.94
00:01:DE:1E:E2:60 LAN 19.43
00:01:DE:1E:E5:FF LAN 1.31
00:01:DE:1F:12:6F LAN 5.20
00:01:DE:1F:15:42 LAN 5.27
00:01:DE:1F:18:BF LAN 14.53
00:01:DE:1F:18:C2 LAN 5.29
00:01:DE:1F:19:3D LAN 24.00
00:01:DE:1F:19:3F LAN 2.24
00:01:DE:1F:39:C7 LAN 5.31
00:01:DE:1F:3A:BB LAN 5.27
00:01:DE:1F:4B:EC LAN 5.30
00:01:DE:1F:6E:41 LAN 18.22
00:01:DE:1F:6E:43 LAN 22.06
00:01:DE:1F:72:2C LAN 5.03
00:01:DE:5F:D5:55 LAN 0.60
00:01:DE:5F:D5:6A LAN 5.30
00:02:6F:60:24:7F LAN 5.83
00:04:AC:18:E5:29 LAN 2.77
00:0C:41:CD:0C:D8 LAN 16.84
00:0C:42:20:9C:3C WLAN 0.00
00:0C:42:22:F4:72 LAN 5.32
00:0C:42:27:1C:44 LAN 4.32
00:0C:42:27:D8:8F LAN 0.12
00:0C:42:2A:D6:31 LAN 0.12
00:0C:42:2B:A9:7F LAN 3.28
00:0C:42:30:37:E5 LAN 23.28
00:0C:42:40:30:F6 LAN 16.27
00:11:3B:06:C3:02 LAN 0.12
00:11:3B:06:DD:10 LAN 28.71
00:11:3B:06:DF:22 LAN 2.66
00:11:3B:06:EC:77 LAN 7.50
00:11:3B:0C:8C:41 LAN 3.98
00:11:3B:0C:8D:97 LAN 2.19
00:11:3B:11:AF:69 LAN 0.07
00:11:6B:26:C2:5F LAN 2.07
00:11:6B:26:E4:67 LAN 15.12
00:11:6B:2B:D4:A9 LAN 11.15
00:11:6B:2B:D4:B3 LAN 0.04
00:11:6B:E0:2A:31 LAN 27.75
00:11:6B:E0:2A:33 LAN 15.15
00:11:6B:E0:3E:11 LAN 9.70
00:11:6B:E0:3E:17 LAN 15.24
00:15:6D:A9:F6:68 LAN 9.31
00:15:6D:AB:46:96 LAN 4.31
00:15:6D:BB:73:95 LAN 18.36
00:15:6D:BB:77:59 LAN 0.14
00:15:6D:D0:C8:F2 LAN 0.24
00:15:6D:D0:CD:28 LAN 10.32
00:15:6D:D0:E9:EC LAN 4.40
00:15:6D:D2:28:73 LAN 1.47
00:15:6D:D2:28:74 LAN 5.31
00:15:6D:D2:28:9A LAN 3.04
00:15:6D:D2:28:A3 LAN 10.31
00:15:6D:D2:29:A4 LAN 4.48
00:15:6D:D2:29:A8 LAN 0.00
00:15:6D:D2:29:A9 LAN 5.32
00:15:6D:D2:29:BE LAN 10.46
00:15:6D:D2:29:C0 LAN 0.00
00:15:6D:D2:2A:29 LAN 3.48
00:15:6D:D2:2A:51 LAN 0.28
00:15:6D:D2:2A:C2 LAN 3.35
00:15:6D:D2:2A:C8 LAN 1.78
00:15:6D:D2:2B:FE LAN 8.35
00:15:6D:D2:A2:6C LAN 4.93
00:15:6D:D2:A2:D0 LAN 21.22
00:15:6D:D2:A3:58 LAN 1.12
00:15:6D:D4:16:FE LAN 5.31
00:15:6D:DC:BF:CD WLAN 0.42
00:15:6D:DC:D4:D3 LAN 16.46
00:15:6D:DC:D7:35 LAN 5.31
00:15:6D:DC:D8:27 LAN 1.04
00:15:6D:DC:D8:43 LAN 5.31
00:15:6D:DC:D8:6E LAN 2.65
00:18:39:AB:BC:59 LAN 1.04
00:18:39:AB:BC:97 LAN 10.80
00:18:4D:9E:37:B3 LAN 18.89
00:18:F3:C9:67:1B LAN 17.79
00:18:F3:C9:67:33 LAN 15.48
00:18:F3:C9:6A:21 LAN 17.10
00:18:F3:C9:E9:2F LAN 10.01
00:1B:11:34:79:BE LAN 9.63
00:1C:10:3D:91:22 LAN 14.75
00:1C:10:A8:C3:85 LAN 13.41
00:1D:7E:FE:79:B5 LAN 0.54
00:1D:7E:FE:79:CD LAN 4.16
00:1D:7E:FF:F8:11 LAN 1.26
00:21:29:7B:44:8C LAN 23.77
00:21:29:9D:B3:6B LAN 10.99
00:21:29:9D:B7:F4 LAN 2.98
00:22:6B:63:F8:8C LAN 20.89
00:22:6B:63:F8:BF LAN 4.79
00:23:69:1C:7F:C0 LAN 2.38
00:23:69:2C:26:6E LAN 8.30
00:23:69:C1:35:1D LAN 15.37
00:E0:4C:7C:50:12 LAN 2.94

[UBNT-Edmundas]

More loockups?!
:(

In some unexpected environment conditions Station gets cycled in re-association state... Enabling AirMax these lockups are not seen.

[UBNT-Edmundas]

what would be your recommended ping interval
for ping watchdog script
Just noticed but the bridge table is pretty big how large can they get before problems happen
this is bridge table after 3 hours
MAC Address Interface Ageing Timer
00:01:DE:00:57:7B LAN 4.88
00:01:DE:00:57:7C LAN 16.83
...


It up to you, how long you can have link down and then to chose correct ping interval :) It may be 30sec or 1min.

Bridge table size isn't the case for this lockup...

[Commander Mittens]

In some unexpected environment conditions Station gets cycled in re-association state... Enabling AirMax these lockups are not seen.

problem is when airmax is one latency goes and i get packet loss
airmax off
http://www.pingtest.net/result/2039520.png (http://www.pingtest.net)
airmax on
http://www.pingtest.net/result/2039275.png (http://www.pingtest.net)

pingtest.net does not let u pick server just goes for the closest but notice the packet loss
so i have to leave airmax off watchdog i guess fixes it going down for long periods but in production environment this is far from ideal

[UBNT-Edmundas]

problem is when airmax is one latency goes and i get packet loss
airmax off
http://www.pingtest.net/result/2039520.png (http://www.pingtest.net)
airmax on
http://www.pingtest.net/result/2039275.png (http://www.pingtest.net)

pingtest.net does not let u pick server just goes for the closest but notice the packet loss
so i have to leave airmax off watchdog i guess fixes it going down for long periods but in production environment this is far from ideal

We are working on latency issues as well...