New Member
Posts: 10
Registered: ‎12-23-2018

NanoStations Loco m5AP becomes unaxcessable from network

[ Edited ]

Arrival to site Ap down. From station using discovery tool I can see both ap and station. Can not talk to AP.

Below is screen shot of station and AP.

Also line of site is clear with 700 ft between AP acn Station.

Both AP and Station radios, poe injectors,cat5e, switches and routers have been replaced. Ap location on building also moved

UPDATE

about 6 hrs after reboot the AP lost lan0. Can not talk to AP over lan but can see it with discovery tool from station and also

the station is connected to ap and shows up. The problem looks like the problem is the loss of lan-0.I can talk to other devices on lan just not AP.

HELP-HELP-HELP

.

21.png22.png23.png24.png

Oct  3 14:14:17 wireless: ath0     New Access Point/Cell address:Not-Associated

Oct  3 14:14:24 wireless: ath0     Set Mode:Managed

Oct  3 14:14:24 wireless: ath0     Set Frequency:5.265 GHz (Channel 53)

Oct  3 14:14:25 wireless: ath0     New Access Point/Cell address:78:8A:20:6A:43:48

Oct  3 14:20:26 httpd[8014]: Password auth succeeded for 'ubnt' from 192.168.254.45

Oct  3 14:21:47 init: reloading /etc/inittab

Oct  3 14:21:47 system: Stop

Oct  3 14:21:48 dropbear[7995]: Early exit: Terminated by signal

Oct  3 14:21:48 init: process '/bin/dropbear -F -r /etc/persistent/dropbear_dss_host_key -r /etc/persistent/dropbear_rsa_host_key -p 22 ' (pid 7995

Oct  3 14:21:48 init: process '/bin/lighttpd -D -f /etc/lighttpd.conf' (pid 7996) exited. Scheduling for restart.

Oct  3 14:21:49 wireless: ath0     Sending disassoc to 78:8a:20:6a:43:48. Reason: Disassociated because sending STA is leaving (or has left) BSS (8).

Oct  3 14:21:49 wireless: ath0     New Access Point/Cell address:Not-Associated

Oct  3 14:21:49 init: process '/bin/wpa_supplicant -D wext -i ath0 -c /etc/wpasupplicant_WPA-PSK.conf' (pid 7994) exited. Scheduling for restart.

Oct  3 14:21:51 syslogd exiting

Oct 03 14:22:10 system: Start

Oct  3 14:22:10 syslogd started: BusyBox v1.24.2

Oct  3 14:22:11 dropbear[8447]: Not backgrounding

Oct  3 14:22:14 wireless: ath0     Set Mode:Managed

Oct  3 14:22:25 wireless: ath0     Set Mode:Managed

Oct  3 14:22:25 wireless: ath0     Set Frequency:5.265 GHz (Channel 53)

Oct  3 14:22:26 wireless: ath0     New Access Point/Cell address:78:8A:20:6A:43:48

Oct  3 14:31:41 wireless: ath0     Received deauth from 78:8a:20:6a:43:48. Reason: Unspecified reason (1).

Oct  3 14:31:48 wireless: ath0     New Access Point/Cell address:Not-Associated

Oct  3 14:31:55 wireless: ath0     Set Mode:Managed

Oct  3 14:31:55 wireless: ath0     Set Frequency:5.485 GHz (Channel 97)

Oct  3 14:31:56 wireless: ath0     New Access Point/Cell address:78:8A:20:6A:43:01

Oct  3 14:31:59 wireless: ath0     Received deauth from 78:8a:20:6a:43:01. Reason: 4-way keying handshake timeout (15).

Oct  3 14:32:06 wireless: ath0     New Access Point/Cell address:Not-Associated

Oct  3 14:32:13 wireless: ath0     Set Mode:Managed

Oct  3 14:32:13 wireless: ath0     Set Frequency:5.265 GHz (Channel 53)

Oct  3 14:32:14 wireless: ath0     New Access Point/Cell address:78:8A:20:6A:43:48

Oct  3 14:32:17 wireless: ath0     Received deauth from 78:8a:20:6a:43:48. Reason: 4-way keying handshake timeout (15).

Oct  3 14:32:24 wireless: ath0     New Access Point/Cell address:Not-Associated

Oct  3 14:32:31 wireless: ath0     Set Mode:Managed

Oct  3 14:32:31 wireless: ath0     Set Frequency:5.485 GHz (Channel 97)

Oct  3 14:32:32 wireless: ath0     New Access Point/Cell address:78:8A:20:6A:43:01

Oct  3 14:32:35 wireless: ath0     Received deauth from 78:8a:20:6a:43:01. Reason: 4-way keying handshake timeout (15).

Oct  3 14:32:42 wireless: ath0     New Access Point/Cell address:Not-Associated

Oct  3 14:32:49 wireless: ath0     Set Mode:Managed

Oct  3 14:32:49 wireless: ath0     Set Frequency:5.265 GHz (Channel 53)

Oct  3 14:32:50 wireless: ath0     New Access Point/Cell address:78:8A:20:6A:43:48

Oct  3 14:32:53 wireless: ath0     Received deauth from 78:8a:20:6a:43:48. Reason: 4-way keying handshake timeout (15).

Oct  3 14:33:00 wireless: ath0     New Access Point/Cell address:Not-Associated

Oct  3 14:33:07 wireless: ath0     Set Mode:Managed

Oct  3 14:33:07 wireless: ath0     Set Frequency:5.265 GHz (Channel 53)

Oct  3 14:33:08 wireless: ath0     New Access Point/Cell address:78:8A:20:6A:43:48

Oct  3 14:33:11 wireless: ath0     Received deauth from 78:8a:20:6a:43:48. Reason: 4-way keying handshake timeout (15).

Oct  3 14:33:18 wireless: ath0     New Access Point/Cell address:Not-Associated

Oct  3 14:33:25 wireless: ath0     Set Mode:Managed

Oct  3 14:33:25 wireless: ath0     Set Frequency:5.485 GHz (Channel 97)

Oct  3 14:33:26 wireless: ath0     New Access Point/Cell address:78:8A:20:6A:43:01

Oct  7 14:58:20 wireless: ath0     New Access Point/Cell address:Not-Associated

Oct  7 15:00:07 wireless: ath0     Set Mode:Managed

Oct  7 15:00:07 wireless: ath0     Set Frequency:5.485 GHz (Channel 97)

Oct  7 15:00:08 wireless: ath0     New Access Point/Cell address:78:8A:20:6A:43:01

Oct  7 15:08:39 httpd[8464]: Password auth succeeded for 'ubnt' from 192.168.10.2

Oct  7 15:15:15 httpd[8500]: Password auth succeeded for 'ubnt' from 192.168.10.10

 

station shots

30.png31.png32.png33.png34.png35.png

Regular Member
Posts: 619
Registered: ‎03-17-2016
Kudos: 119
Solutions: 41

Re: NanoStations Loco m5AP becomes unaxcessable from network

Find a clean channel for the AP and get it off AUTO. It's constantly changing channels as shown in the log and the station has to re-associate. Any reason for using the Frequency scan list and the channels you chose (AP)? I would choose one specific channel on the AP, set the Station to auto and disable the frequency scan list on both radios.

Can you provide a basic map/description of how the network is setup/cabled? Whats plugged into what etc etc.

DeepThinkCo.com - IT Consulting
Highlighted
New Member
Posts: 10
Registered: ‎12-23-2018

Re: NanoStations Loco m5AP becomes unaxcessable from network

Here is the site map that i leave at site.

img001.jpg

New Member
Posts: 10
Registered: ‎12-23-2018

Re: NanoStations Loco m5AP becomes unaxcessable from network

Update

Placed AP on its own router not connected to local lan. Ap freq list off and on one clean channel. stations set to auto channel.

Lan 0 locked up within 6 hrs. Still see ap and stations with discovery tool from behind station. no lan comm to AP

Ubiquiti Employee
Posts: 11,657
Registered: ‎04-14-2017
Kudos: 2180
Solutions: 335

Re: NanoStations Loco m5AP becomes unaxcessable from network

There is a lot of information here. Can you please give me a brief summary of the problem?
New Member
Posts: 10
Registered: ‎12-23-2018

Re: NanoStations Loco m5AP becomes unaxcessable from network

The AP looses connunications with lan.I can go to any station with discovery tool and see AP. All three ststions are good and I can see and access cammeras with SADP from any station connected switch.

Must power cycle injector get lan/poe port on AP back.

Have replaced AP, power injector, lan switch, lan cables andall power coards.

Ubiquiti Employee
Posts: 11,657
Registered: ‎04-14-2017
Kudos: 2180
Solutions: 335

Re: NanoStations Loco m5AP becomes unaxcessable from network

Ok, thanks. How long is the cable between the AP and the switch? Is it grounded?