View Full Version : 4.3 mile Bullet M5-HP PTP Link
Premier
11-02-2009, 01:29 PM
Hi,
I have set up our first Bullet M5 PTP link from our office to our first tower.
At the office...
At the office we have a 23db panel with the bullet screwed directly in to it. The office is in AP mode and can see the tower at -66. The AP is set up as follows:
v5.0.2
112/5560
20Mhz
85/6 miles
Airmax: Disabled
Output Power: 23db
Bridge Mode
At the tower...
At the tower we have a 29db dish with the bullet also screwed in to it. The tower is in station mode can see the office at -65. The Station is set up as follows:
v5.0.2
112/5560
20Mhz
85/6 miles
Airmax: Disabled
Output Power: 23db
Bridge Mode
Now the problem:
With the link idle and just a regular ping going through it TX/RX rates are at a steady 65Mb. Transmit CCQ does be 100%.
But when I do a throughput test from one Star-os box to another It can peak 25Mb ( about the max our star-os cpu's can handle anyway) but CCQ can be anywhere from 40%-80% and pings go up to 50ms and no higher.
I have tried loads of different channels that we are not using and that I know are clear. Went out of band also where there would be no radios operating within 200 megs. I have also changed the AP to the STATION and vise versa. Tried 10Mhz bandwidths, adjust the distance, etc but I can not get the CCQ to remain constant, it's all over the place when traffic is flowing through it.
Please Help! :icon_frown:
At 6 miles, you should have a 56 dBm or so signal, so your path would be all right. Do you have clear line of sight?
Your ACK is 6 miles, what is your actual physical distance?
The ACK works best with Auto not used and then set the distance to 15% greater than the actual distance.
See if that helps.
Premier
11-02-2009, 02:29 PM
Perfect line of sight. Actual distance is 4.3 miles
UBNT-Mike.Ford
11-02-2009, 02:37 PM
Hello,
Can you post your configuration files from both sides?
Thanks,
Mike
Premier
11-02-2009, 02:55 PM
aaa.1.status=disabled
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.stp.status=disabled
bridge.status=enabled
dhcpc.1.devname=br0
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=enabled
ebtables.2.cmd=-t nat -A POSTROUTING --out-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.2.status=enabled
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
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=10.10.18.2
netconf.3.netmask=255.255.255.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.delay=300
pwdog.host=10.10.18.1
pwdog.period=300
pwdog.retry=3
pwdog.status=enabled
radio.1.ack.auto=disabled
radio.1.ackdistance=9600
radio.1.acktimeout=85
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=5760
radio.1.ieee_mode=11naht20
radio.1.mcastrate=
radio.1.mode=managed
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=0xe205
radio.1.thresh62a=
radio.1.thresh62b=
radio.1.thresh62g=
radio.1.txpower=23
radio.countrycode=511
radio.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=10.10.18.1
route.1.ip=0.0.0.0
route.1.netmask=0
route.1.status=enabled
route.status=enabled
snmp.status=disabled
sshd.port=22
sshd.status=disabled
syslog.remote.status=
syslog.status=disabled
telnetd.status=disabled
tshaper.status=disabled
users.1.name=ubnt
users.1.password=VvpvCwhccFv6Q
users.1.status=enabled
users.status=enabled
wireless.1.addmtikie=enabled
wireless.1.ap=
wireless.1.authmode=1
wireless.1.compression=0
wireless.1.devname=ath0
wireless.1.fastframes=0
wireless.1.frameburst=0
wireless.1.hide_ssid=disabled
wireless.1.l2_isolation=enabled
wireless.1.mac_acl.1.mac=
wireless.1.mac_acl.1.status=disabled
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=
wireless.1.mac_acl.2.status=disabled
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=disabled
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=link
wireless.1.status=enabled
wireless.1.wds=disabled
wireless.1.wmm=enabled
wireless.1.wmmlevel=
wireless.status=enabled
wpasupplicant.device.1.status=disabled
wpasupplicant.status=disabled
Premier
11-02-2009, 02:56 PM
aaa.1.status=disabled
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.stp.status=disabled
bridge.status=enabled
dhcpc.1.devname=br0
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
httpd.port.http=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=10.10.18.10
netconf.3.netmask=255.255.255.0
netconf.3.status=enabled
netconf.3.up=enabled
netconf.status=enabled
netmode=bridge
ppp.1.password=
ppp.1.status=disabled
ppp.status=disabled
radio.1.ack.auto=disabled
radio.1.ackdistance=9600
radio.1.acktimeout=85
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=5640
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=0xe205
radio.1.thresh62a=
radio.1.thresh62b=
radio.1.thresh62g=
radio.1.txpower=23
radio.countrycode=511
radio.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=10.10.18.1
route.1.ip=0.0.0.0
route.1.netmask=0
route.1.status=enabled
route.status=enabled
sshd.port=22
sshd.status=enabled
tshaper.status=disabled
users.1.name=ubnt
users.1.password=VvpvCwhccFv6Q
users.1.status=enabled
users.status=enabled
wireless.1.addmtikie=enabled
wireless.1.ap=
wireless.1.authmode=1
wireless.1.compression=0
wireless.1.devname=ath0
wireless.1.fastframes=0
wireless.1.frameburst=0
wireless.1.hide_ssid=disabled
wireless.1.l2_isolation=disabled
wireless.1.mac_acl.1.mac=
wireless.1.mac_acl.1.status=disabled
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=
wireless.1.mac_acl.2.status=disabled
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=disabled
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=65
wireless.1.signal_led4=60
wireless.1.ssid=link
wireless.1.status=enabled
wireless.1.wds=disabled
wireless.1.wmm=enabled
wireless.1.wmmlevel=
wireless.status=enabled
wpasupplicant.device.1.status=disabled
wpasupplicant.status=disabled
Premier
11-02-2009, 03:01 PM
Just for the benefit of a doubt, I have Star-os running for 2 years now from the office to our first tower on 5640, 20Mhz channel size and I can get 25-30 megs accross it and the quality is always between 90-100%. So I moved this link off 5640 and on to another band as i know this slot is clear from interference, and moved the Ubnt link on to it instead, but the quality is still dropping.
along5664
11-02-2009, 04:52 PM
I am seeing the same type results with a rocket and nano5 link. not under load 100% ccq, under load 40-90% ccq...does not seem to bother my traffic flow, although I am only doing about 15mb/s across the link.
Premier
11-03-2009, 01:01 AM
Maybe its just cosmetic? When I push 25-30Mb accross the link the pings do climb up to 50ms which is a little bit high for my liking. I also would be happy with 50mb going accross this link with lower pings.
Premier
11-04-2009, 10:03 AM
I had both antennas in vertical so is most of my links. When the station done a site survey it could pick up 7-8 5.8 AP's. So I turned both antennas to horizontal and now the station can only see 2 AP's, but still the problem persists. As soon as i push traffic accross the link the ccq rate takes a nose dive and the link sync's at a lower rate than 65Mb
UBNT-Mike.Ford
11-04-2009, 02:24 PM
Hello,
Can you play with the ACK values? The ACK is very sensitive. If its off by a little it can cause link instability. Can you try an ack value of 105?
Thanks,
Mike
Premier
11-04-2009, 03:15 PM
will do Mike...
Premier
11-04-2009, 03:19 PM
Should I like be trying the ACK in increments of just 1's or perhaps 5's at a time?
whitedot
11-04-2009, 03:50 PM
Are these ACK issues going to be sorted in v5.1, and is it still on track for release later this month?
UBNT-Mike.Ford
11-04-2009, 03:52 PM
Are these ACK issues going to be sorted in v5.1, and is it still on track for release later this month?
Yes and Yes.
UBNT-Mike.Ford
11-04-2009, 03:53 PM
Should I like be trying the ACK in increments of just 1's or perhaps 5's at a time?
I generally move by 3.
Thanks,
Premier
11-04-2009, 04:06 PM
Why is ACK 28, 43, 58, 72, 87, etc, etc missing out of the ACK list?
whitedot
11-05-2009, 04:50 AM
Yes and Yes.
Cheers. :icon_smile:
UBNT-Mike.Ford
11-05-2009, 01:30 PM
Why is ACK 28, 43, 58, 72, 87, etc, etc missing out of the ACK list?
Have you tried entering the values is manually?
Thanks,
Mike
Premier
11-05-2009, 01:37 PM
No, just wondered thats all. I have been adjusting my ack by steps of 2 or 3 at a time and testing the link. Spent hours last night and today moving it bit by bit and testing in between, but still I dont see any performance increase. CCQ still craps out.
UBNT-Mike.Ford
11-05-2009, 01:38 PM
No, just wondered thats all. I have been adjusting my ack by steps of 2 or 3 at a time and testing the link. Spent hours last night and today moving it bit by bit and testing in between, but still I dont see any performance increase. CCQ still craps out.
Can you give us SSH access into your units?
Thanks,
Mike
Premier
11-05-2009, 02:54 PM
Can you give us SSH access into your units?
Thanks,
Mike
I will see if I can route a public out to them.....
Premier
11-05-2009, 03:05 PM
PM sent Mike
Premier
11-06-2009, 10:33 AM
Did you get what you wanted Mike?
UBNT-Mike.Ford
11-06-2009, 02:48 PM
Hello Premier,
Sorry just now checking my PM's. Its always faster to reach me by email at mike@ubnt.com
Thanks,
Premier
11-06-2009, 03:00 PM
Hello Premier,
Sorry just now checking my PM's. Its always faster to reach me by email at mike@ubnt.com
Thanks,
Ah...you live and learn!
overburn
11-06-2009, 03:09 PM
premier I solved the crappy ccq issue by setting the sped from auto to manual in my case 104 and since then i have always 100% ccq
Premier
11-06-2009, 03:24 PM
premier I solved the crappy ccq issue by setting the sped from auto to manual in my case 104 and since then i have always 100% ccq
I never used auto, always manual. I have went from an ack of 79 to 148 at the moment. I done this in steps of 2 or 3 at a time and re-tested each time.
NZFoxnet
11-06-2009, 03:37 PM
Hes talking about the negotiation rate not the ack.
Premier
11-06-2009, 03:39 PM
Damn, so he was. Thats what the lack of sleep does! Thankx for pointing that out, I will give it a go.
Premier
11-06-2009, 03:58 PM
Oh my God, Oh my God, Oh my God, that just made some difference.
I set the link to sync at 52Mb both ends, I can push a constant 30Meg over the link, limited to the cpu power of the boards star-os is on, the CCQ% Does not go below 65% (vast improvement) pings are average 21ms with absolutely no PL.
I think it just needs some final ACK adjustments to get it right.
Overburn...you can take a bow! :icon_lol:
overburn
11-06-2009, 04:09 PM
glad to help :] and wishing constant 100% ccq like mine:]
Premier
11-06-2009, 04:35 PM
The strange thing though is that if I manually force both radios to sync at a low rate the CCQ goes to crap when I pass traffic. Setting it to its highest gives me a CCQ of between 88% and 100%. Average ping times are 16ms when pushing 30+Mb. Normally its the complete opposite.
kijoma
11-07-2009, 04:40 AM
hi,
one thing i was going to suggest was to turn the power down a bit, that improves the linearity of the PA which can be useful under heavy traffic.
Premier
11-07-2009, 07:41 AM
I relocated one of the antennas today and got the signal down to -53 at one end and -60 at the other. I have connected up a Ubuntu server at the station end, running iperf and my windows laptop at the other end also running iperf.
The most I can get is 35Mb/sec in one direction at a time. When I switch from 20Mhz channels to 40Mhz channels its the very same apart from one test where I got 49Mb/sec. The CCQ rate hovers from 80% to 100% but always syncing at 65Mb. I am wondering is there something on my windows machine limiting me?
pings are always less than 16ms. What should I be getting on this link if both sides are syncing at 65Mb?
Premier
11-08-2009, 02:54 AM
I ran some more iperf tests accross the link, this time doing it in 10 streams at a time, and while the link was using 20Mhz of spectrum I could only get 30Mb+ accross it. But when I used 40Mhz of spectrum it shot right up to 80Megs with about 5 Megs of real traffic going throught it. Not too bad and the CCQ rate remained in the high 90's with ping times no more than 40ms.
Although when I was using 20Mhz of spectrum, and had both ends syncing at 65Mb/65Mb should I not be getting around 50Megs with an iperf test?
ozric
11-08-2009, 11:10 AM
Hello Premier,
What's your iperf param ?
it's a TCP or UDP test ?
Premier
11-08-2009, 01:12 PM
Hello Premier,
What's your iperf param ?
it's a TCP or UDP test ?
Dunne, never used this before.
on the server side I just type in IPERF -S and on the client side I just type in IPERF -C X.X.X.X -P 10
gullisig
11-08-2009, 02:11 PM
You should get your self jperf from here
http://www.ubnt.com/forum/showthread.php?t=12740
ozric
11-08-2009, 02:48 PM
ok and you have same results in udp and tcp ?
Premier
11-08-2009, 02:52 PM
ok and you have same results in udp and tcp ?
I dont know, the commands I posted are the only commands I used. Never even heard of Iperf until I came here.