Picostation2HP Hit or Miss!

[bigdessert]

I have a picostation2HP that I have recently purchased. I was trying to get this thing setup in an AP-WDS fasion with 1 other ap. Well 3 days no go....seems to be a performance issue on the pictostation. I played with many different settings and still the same results.

Here is the problem:

I can connect to the AP, but my data rate seems to fluctuate anywhere from 1Mbps-54Mbps and this is with the pico 5 ft away from my laptop.

I have ruled out WDS and set it up as a simple AP. sometimes I can pass traffic through the AP, but most times I cannot. Seems to be related when I get 48-54Mbps I can usually send data through, anything below that and nogo.

Here is the config any suggestions welcome:

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.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=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.status=enabled
netconf.2.up=enabled
netconf.3.autoip.status=disabled
netconf.3.devname=br0
netconf.3.ip=192.168.254.89
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=enabled
radio.1.ackdistance=750
radio.1.acktimeout=26
radio.1.ani.status=disabled
radio.1.channel=8
radio.1.chanshift=0
radio.1.clksel=0
radio.1.countrycode=840
radio.1.devname=ath0
radio.1.dfs.status=
radio.1.frag=off
radio.1.ieee_mode=g
radio.1.mcastrate=1M
radio.1.mode=master
radio.1.rate.auto=enabled
radio.1.rate.max=54M
radio.1.rts=off
radio.1.rx_antenna=1
radio.1.rx_antenna_diversity=disabled
radio.1.status=enabled
radio.1.thresh62a=28
radio.1.thresh62b=28
radio.1.thresh62g=28
radio.1.tx_antenna=1
radio.1.tx_antenna_diversity=disabled
radio.1.txpower=19
radio.countrycode=840
radio.ratemodule=ath_rate_minstrel
radio.status=enabled
resolv.nameserver.1.ip=208.67.222.222
resolv.nameserver.1.status=enabled
resolv.nameserver.2.ip=208.67.220.220
resolv.nameserver.2.status=enabled
resolv.status=enabled
route.1.devname=br0
route.1.gateway=192.168.254.1
route.1.ip=0.0.0.0
route.1.netmask=0
route.1.status=enabled
route.status=enabled
tshaper.in.1.devname=eth0
tshaper.in.burst=0
tshaper.in.cburst=0
tshaper.in.rate=256
tshaper.out.1.devname=ath0
tshaper.out.burst=0
tshaper.out.cburst=0
tshaper.out.rate=256
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.autowds=disabled
wireless.1.compression=disabled
wireless.1.devname=ath0
wireless.1.fastframes=disabled
wireless.1.frameburst=disabled
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.17.mac=
wireless.1.mac_acl.17.status=disabled
wireless.1.mac_acl.18.mac=
wireless.1.mac_acl.18.status=disabled
wireless.1.mac_acl.19.mac=
wireless.1.mac_acl.19.status=disabled
wireless.1.mac_acl.2.mac=
wireless.1.mac_acl.2.status=disabled
wireless.1.mac_acl.20.mac=
wireless.1.mac_acl.20.status=disabled
wireless.1.mac_acl.21.mac=
wireless.1.mac_acl.21.status=disabled
wireless.1.mac_acl.22.mac=
wireless.1.mac_acl.22.status=disabled
wireless.1.mac_acl.23.mac=
wireless.1.mac_acl.23.status=disabled
wireless.1.mac_acl.24.mac=
wireless.1.mac_acl.24.status=disabled
wireless.1.mac_acl.25.mac=
wireless.1.mac_acl.25.status=disabled
wireless.1.mac_acl.26.mac=
wireless.1.mac_acl.26.status=disabled
wireless.1.mac_acl.27.mac=
wireless.1.mac_acl.27.status=disabled
wireless.1.mac_acl.28.mac=
wireless.1.mac_acl.28.status=disabled
wireless.1.mac_acl.29.mac=
wireless.1.mac_acl.29.status=disabled
wireless.1.mac_acl.3.mac=
wireless.1.mac_acl.3.status=disabled
wireless.1.mac_acl.30.mac=
wireless.1.mac_acl.30.status=disabled
wireless.1.mac_acl.31.mac=
wireless.1.mac_acl.31.status=disabled
wireless.1.mac_acl.32.mac=
wireless.1.mac_acl.32.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.security=none
wireless.1.signal_led1=94
wireless.1.signal_led2=80
wireless.1.signal_led3=73
wireless.1.signal_led4=65
wireless.1.sper=disabled
wireless.1.ssid=test
wireless.1.status=enabled
wireless.1.wds.1.peer=00:23:69:82:B9:40
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=disabled
wireless.1.wmm=disabled
wireless.1.wmmlevel=-1
wireless.status=enabled
wpasupplicant.device.1.status=disabled
wpasupplicant.status=disabled

[UBNT-Mike.Ford]

Hello,

Please vist the Advanced page. Please uncheck "enable extra reporting" and test the link again.

Thanks,

Mike

[bigdessert]

tried disabling extra reporting and still same problem.

[davekall]

Hello,
Did this problem ever get resolved? I am having the exact same issue with the PicoHPs. I have spent 2 days with no results myself.

[bigdessert]

no resolution here. I have pretty much given up and have been trying to get ahold of a bullet hp. Mike do you have any other insight to help us out??

[davekall]

It has been pretty frustrating. We have tried almost every tweak and it doesn't seem to change anything. The ping times and dropped packets are very consistently inconsistent. sometimes only one person can ping the gateway while the other cannot. Also if we hop from one AP to the other we also drop connection to the gateway IP. Are the Bullets supposed to work better?

[bigdessert]

supposedly our supplier says lots of problems with the pico's and no problems with the bullet's. I am going on their word though. Problem is that they are out until the end of july.

[WHT]

supposedly our supplier says lots of problems with the pico's and no problems with the bullet's
Hmmmmmmmmmmmm..................

[davekall]

Double hmmmmmmmm...............

[davekall]

Hey Bigdessert,
Just curious, who is your supplier?

[UBNT-Mike.Ford]

Hey Guys,

I do apologize for the delay in getting back to you. I have been unable to reproduce this problem here in the lab. can you email your .sup and .cfg files to support@ubnt.com ?

thanks,

Mike

[davekall]

I just sent them to you.

[bobcopro]

Are you guys actually getting Pico2-HP's as all of our suppliers are saying they're not available until mid August. All our Pico's are coming through with the stickers on the box saying 1000mw, but it's the standard 250mw Pico in the box (what's up with the false advertising Ubiquiti?) If you look at the power settings in the webui the 250mw Pico's will only go up to 20dbm. In that case the Bullet2-HP's will work better as they are 800mw.

We have recently started using Pico's as the receiving end on our customer's backhauls due to the lack of Nano's and have had good luck with them. Now the Nanos are available again and I can't find Bullet-HP's (once again - what's up with that Ubiquiti?)