Weird Problem-o

[Frotihngdog.ca]

Put up a PS5 for an Access Point today, and we're having a WEIRD problem. We can only get 1 SM to register to the AP.

Here is the AP config:

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=enabled
netconf.3.devname=br0
netconf.3.ip=10.1.48.11
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.acktimeout=75
radio.1.channel=165
radio.1.chanshift=0
radio.1.clksel=2
radio.1.countrycode=124
radio.1.devname=ath0
radio.1.dfs.status=
radio.1.frag=off
radio.1.ieee_mode=a
radio.1.mcastrate=1.5M
radio.1.mode=master
radio.1.rate.auto=disabled
radio.1.rate.max=12M
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=124
radio.ratemodule=ath_rate_minstrel
radio.status=enabled
resolv.host.1.name=AP1
resolv.host.1.status=enabled
resolv.nameserver.1.ip=216.185.64.10
resolv.nameserver.1.status=enabled
resolv.nameserver.2.ip=216.185.64.6
resolv.nameserver.2.status=enabled
resolv.status=enabled
route.1.devname=br0
route.1.gateway=10.1.48.1
route.1.ip=0.0.0.0
route.1.netmask=0
route.1.status=enabled
route.status=enabled
snmp.community=ops
snmp.contact=RB
snmp.location=TOWER
snmp.status=enabled
tshaper.status=disabled
users.1.name=root
users.1.password=YyLKle4wdGq6w
users.1.status=enabled
users.status=enabled
wireless.1.addmtikie=disabled
wireless.1.ap=
wireless.1.authmode=1
wireless.1.compression=disabled
wireless.1.devname=ath0
wireless.1.fastframes=enabled
wireless.1.frameburst=enabled
wireless.1.hide_ssid=enabled
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.security.4.key=**********************
wireless.1.security.default_key=4
wireless.1.security=wep128
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=AP1
wireless.1.status=enabled
wireless.1.wds=disabled
wireless.1.wmm=enabled
wireless.1.wmmlevel=0
wireless.status=enabled
wpasupplicant.device.1.status=disabled
wpasupplicant.status=disabled

I tried 2 different NS5's, I even downloaded the config from the WORKING NS5 and applied it to the other 2 and then changed the IP and the HOST NAME but still nothing...no signal at all. Site Survey shows nothing in the NS5's.

Any ideas?

[UBNT-Mike.Ford]

Hey Frot,

Did you try a factory default? Also what version of the software is on that unit?

Thanks,

[Frotihngdog.ca]

Yes did 2 factory defaults...one form the GUI and the other form the Default button on the radio.

FW version: 3.2.3-rc on all the radios

[UBNT-Mike.Ford]

Hey Frot,

Can you rebuild the firmware:

http://www.ubnt.com/downloads/LS-Recovery.txt

Thanks,

[Frotihngdog.ca]

I think we are gonna replace the unit. I'll try a Recovery when I have the time.

[UBNT-Mike.Ford]

Hey Frot,

Let me know if replacing it fixes the problem. If so Ill get that unit back from you and replace it.

Thanks,

Mike

[Frotihngdog.ca]

Great...thanks Mike.

[UBNT-Mike.Ford]

Hey Frot,

Any update?

Mike

[Frotihngdog.ca]

Possibly Friday...was busy with other things today.

[Frotihngdog.ca]

Mike,

Here's an update on my situation.

We went back today and replaced the PS5 with a NEW PS5 that was upgraded to 3.2.3-rc. This did NOT fix the problem. During this we noticed that on the MAIN screen the channel said "0" and not the selected channel (165). So at this point I started changing channels to see if any of them actually said the proper channel. I found that the 5.7 channels up to 154 where fine...anything over that it said channel '0' on the main screen.

However when I changed to channel 154 it still did not fix the problem. I even tryed 153,152...and so on. No luck.

At that point I decided to change the Channel WIDTH from 5mhz to 10mhz and then check the Channels. at 10mhz it was fine all the channels appeared as normal on the MAIN screen. At that point I tried to register the second SM to the AP and what do ya know it worked.

So at a 10Mhz wide channel and on Channel 165 with WEP-128 and no ACL it works fine. But at 5Mhz, channel 165, WEP-128 and no ACL it does not work.

I even tried removing the WEP but that didn't fix it either. There is something funky happening with the 5Mhz channel.

Weird thing is that we don't have this problem with the PS2's or the NS2. We run all our 2.4AP's on a 5Mhz channel.

Any ideas Mike?

[UBNT-Mike.Ford]

Hey Frot,

Im gonna get my software guys to jump back in here.

Mike

[Frotihngdog.ca]

Ok

[Frotihngdog.ca]

Were is this software guy that I've been hearing so much about :)

[UBNT-Mike.Ford]

Hey Frot,

Sorry for the delay, ill jump on there case.

Thanks

Mike

[Frotihngdog.ca]

It's alright Mike...I'm just messin' around. I'm sure you gys are busy. It's not a major problem. The key point is that you know about it.

Let me know if there is any progress or you want me to beta a new firware.

cheers

[WHT]

Were is this software guy that I've been hearing so much about

They have him chained to his cubicle recliner and pumping coffee in him on a 108 Mbps Turbo intravenous drip until he gets some mesh firmware ready to shock and awe us.

[kijoma]

hey!,

not until the get the hardware guy to supply a grip washer and a better wingnut :D

[Frotihngdog.ca]

I'd prefer a PS9 personally

[Frotihngdog.ca]

Mike, any update on this issue??

[UBNT-keba]

Hi,
Just found this post ;-)


During this we noticed that on the MAIN screen the channel said "0" and not the selected channel (165)


This is know issue related to the standard Linux Wireless extensions implementation. It support just up to 32 channels list for reporting so it does not report correct channel number for 5MHz list:

FCC1_FCCA
Freq Chan
5180 36
5185 37
5190 38
5195 39
5200 40
5205 41
5210 42
5215 43
5220 44
5225 45
5230 46
5235 47
5240 48
5260 52
5265 53
5270 54
5275 55
5280 56
5285 57
5290 58
5295 59
5300 60
5305 61
5310 62
5315 63
5320 64
5745 149
5750 150
5755 151
5760 152
5765 153
5770 154
5775 155
5780 156
5785 157
5790 158
5795 159
5800 160
5805 161
5810 162
5815 163
5820 164
5825 165

List has more than 32 entries so for channel greater than 5770(154) are reported as 0.
We are working on it to use private implementation instead of standard wireless extensions to report correct channels in 5MHz mode.


I even tried removing the WEP but that didn't fix it either. There is something funky happening with the 5Mhz channel.


Is it happen on low channels as well (< 100)? Can you connect by using low 5MHz channels?

[Frotihngdog.ca]

None of the channels we tried worked. I can't remember exactly what chcannels we tried but I'm pretty sure we tried 5745 and 5825 and I believe we tried 5320 even though our Omni only runs from 5700-5900, it still broadcasted a signal and we were still only able to get 1 SM to register to the AP.

Once we changed to 10MHz mode everything was fine.

[Frotihngdog.ca]

Mike, Keba...

Any firmware fix for this yet? My Boss wants to turn that Access Point up soon.

[UBNT-Mike.Ford]

Hey Frot,

Asking my software guys for an update.

Thanks,

Mike

[UBNT-keba]

Frotihngdog.ca

Have you a chance to try 3.3-beta?

[Frotihngdog.ca]

Sure..email me a link to download it and I can test it out.

[Frotihngdog.ca]

Mike, Keba

3.3-beta no workie either.

[UBNT-keba]

May I ask what is AckTimeout on them?
v3.3-beta was setting to low Acktimeout for quarter rates by default and almost all packets was not acked.

Also is channel shifting is enabled together with 5MHz feature?

[Frotihngdog.ca]

Each radio was set to 5miles so I guess that's a ACK of about 93. Channel Shifting is DISABLED

[UBNT-keba]

On 5MHz channels acktimeout has to be 129us at least for 5milles.
v3.3-beta is starting to take in account operational mode (40/20/10/5MHz) so acktime is different for the same distance but for different operational mode.

[Frotihngdog.ca]

So I should turn off AUTO ACK and set it to 129 or higher and test again?