Reply
Highlighted
New Member
Posts: 19
Registered: 2 weeks ago
Solutions: 1
Accepted Solution

Replacement Nano M2 XW will not connect and maintain connection to AP

[ Edited ]

Hi,

 

 

This is the screen when the New nano XW shows as connected, it only connects briefly.

Nano Fwd Connected.pngNano fwd Disconnected.png

This the usual screen when the new nano XW does not connect to the AP.

Nano fwd Disconnected.png

This is the screen for the other nano XM which connects perfectly and shares the same config as the new one.

AP Data.png

 

 

 

 

 

 

 

 

 

 

It is a long time since I trawled these boards as my Nano M2 set up has been fault free for years.

 

However I recently lost a Nano M2 due to water ingress into the POE cable which shorted out the pwer supply and Nano.

 

I purchased a replacement Loco M2 and uploaded the confog file but it will not maintain a stable connection with the AP.

 

The AP is an M2 on a shore office building about 0.1 miles away, at the moment and the two Loco M2 are on a ship.

 

I have two pointing in opposite directions to cater for either side to.

 

The only difference i can see is the old Loco M2 is XM and the new one is WM, I have tried the latest firmware, v6.1.8. The old, aft facing one connects flawlessly, the new fwd facing does not.

 

Any ideas?Nano Fwd Connected.pngNano fwd Disconnected.pngNano Aft.png


Accepted Solutions
New Member
Posts: 19
Registered: 2 weeks ago
Solutions: 1

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

All sorted, I uploaded the Config file from the other ship and it worked.

 

I compared both set ups and noticed that WDS (Transparent Bridge Mode) and CDP were unticked.

 

I reverted to my original config, unticked both and it works.

 

Thanks for all your input.

 

Nano.png

 

 

View solution in original post


All Replies
Ubiquiti Employee
Posts: 583
Registered: ‎09-24-2018
Kudos: 119
Solutions: 29

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

It's hard to determine from all your screenshots, but it seems like you have multiple APs sharing the same SSID on different channels?

UBNT_Alternate_Logo.png
Ubiquiti Networks airMAX Support Team

Check out our ever-evolving Help Center for answers to many common questions!

FREE UBWA Student Guide-Great RF Primer!

New Member
Posts: 19
Registered: 2 weeks ago
Solutions: 1

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

Hi Josh,

 

it looks like I have posted the screen shots twice, the first two show the new M2 connected and as far as I can make out scanning other channels. It only connects briefly on Channel 8 2447 mhz then reverts to the 2nd pic.

 

The third shot is of the other M2 showing the AP details, this M2 stays connected perfectly. I was connected to both last night using a Laptop for one and a PC the other. I even changed power supplies and tried a different ethernet cable, the one in use is a brand new one after the water incident.

 

As I said i have uploaded the config from the original one to the new one. I am not in range/ sight at the moment but will be again from 0900 until 1400 today.

 

     Cheers Mike

Ubiquiti Employee
Posts: 10,200
Registered: ‎04-14-2017
Kudos: 1878
Solutions: 284

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

Could you please edit your post to remove the duplicates? This will make it easier for us to troubleshoot your issue.

XM vs XW should not make a significant difference here. I am not sure what you mean by it reverting to the second pic.
Ubiquiti Employee
Posts: 583
Registered: ‎09-24-2018
Kudos: 119
Solutions: 29

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

Also provide a diagram of the topology. I'm not sure how to visualize your case.

UBNT_Alternate_Logo.png
Ubiquiti Networks airMAX Support Team

Check out our ever-evolving Help Center for answers to many common questions!

FREE UBWA Student Guide-Great RF Primer!

New Member
Posts: 19
Registered: 2 weeks ago
Solutions: 1

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

Hi SNK,

 

The new nano XW appears to scan and occasionally, briefly connect to the AP, this is the the first screenshot.

 

However it usually just appears to be continually scanning the channels, this is the 2nd screenshot.

 

The last shot is of the other nano XM which has connected perectly for the last 3 years, I uploaded the config from this one to the failed Nano just as I did when I cloned the original one. I incuded the AP details.

Ubiquiti Employee
Posts: 583
Registered: ‎09-24-2018
Kudos: 119
Solutions: 29

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

Add screenshots of the other config tabs.

UBNT_Alternate_Logo.png
Ubiquiti Networks airMAX Support Team

Check out our ever-evolving Help Center for answers to many common questions!

FREE UBWA Student Guide-Great RF Primer!

New Member
Posts: 19
Registered: 2 weeks ago
Solutions: 1

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

 
Advanced.png
Services.png
System.png
New Member
Posts: 19
Registered: 2 weeks ago
Solutions: 1

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

 
Network.png
Wireless.png
Ubiquiti Employee
Posts: 10,200
Registered: ‎04-14-2017
Kudos: 1878
Solutions: 284

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

@UBNT-JoshMcGee could you please take this one?
New Member
Posts: 19
Registered: 2 weeks ago
Solutions: 1

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

here is a video  of the scanning/ intermittent connection

New Member
Posts: 19
Registered: 2 weeks ago
Solutions: 1

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

Regular Member
Posts: 326
Registered: ‎02-19-2015
Kudos: 67
Solutions: 13

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

this is usually causes by incorrect password on station or AP
Senior Member
Posts: 3,264
Registered: ‎07-17-2010
Kudos: 755
Solutions: 188

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

Yes This is security related. Change AP to WPA2-AES. 

 

Then change station and make sure key matches.

 

This change will also offer higher modulation schemes.

New Member
Posts: 19
Registered: 2 weeks ago
Solutions: 1

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

The set up and password is identical to the other working Nano.

Regular Member
Posts: 326
Registered: ‎02-19-2015
Kudos: 67
Solutions: 13

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

Double check the password, also look at the log on the station and the AP and it will tell you wahts going on
Senior Member
Posts: 3,264
Registered: ‎07-17-2010
Kudos: 755
Solutions: 188

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

Also, do not use a different config, config from scratch AFTER you reset to default.

 

Make those security changes too. It's worth the effort.

New Member
Posts: 19
Registered: 2 weeks ago
Solutions: 1

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

Unfortunately I have no access to the AP as the office is shut for the weekend.

 

I tried inputting the password again and got a security message that WPA-TKIP is no longer supported.

 

I will not be back here during office hours until Wednesday.

New Member
Posts: 19
Registered: 2 weeks ago
Solutions: 1

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

I reset to default but the set up stalls on the Security settings as WPA-TKIP is no longer supported.

 

It has been 5 or 6 years since I set it up with another bloke from another company ship. he did the AP.

 

I will attack the AP on Wednesday and revert, unless anyone has any other ideas.

 

I will be here until tomorrow 0930 then back again late tomorrrow and Sunday.

 

Thanks for your help and patience.

New Member
Posts: 19
Registered: 2 weeks ago
Solutions: 1

Re: Replacement Nano M2 XW will not connect and maintain connection to AP

Jan 11 00:00:15 system: Start
Jan 11 00:00:15 syslogd started: BusyBox v1.24.2
Jan 11 00:00:17 dropbear[2950]: Not backgrounding
Jan 11 00:00:17 dnsmasq[2949]: started, version 2.66 cachesize 150
Jan 11 00:00:17 dnsmasq[2949]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-scripts no-TFTP no-conntrack no-ipset no-auth
Jan 11 00:00:17 dnsmasq-dhcp[2949]: DHCP, IP range 192.168.11.100 -- 192.168.11.200, lease time 10m
Jan 11 00:00:17 dnsmasq[2949]: no servers found in /etc/resolv.conf, will retry
Jan 11 00:00:17 dnsmasq[2949]: read /etc/hosts - 1 addresses
Jan 11 00:00:18 dnsmasq-dhcp[2949]: DHCPREQUEST(eth0) 192.168.11.131 b8:70:f4:95:64:7f 
Jan 11 00:00:18 dnsmasq-dhcp[2949]: DHCPACK(eth0) 192.168.11.131 b8:70:f4:95:64:7f Boyler
Jan 11 00:00:20 wireless: ath0     Set Mode:Managed
Jan 11 00:00:28 wireless: ath0     Set Mode:Managed
Jan 11 00:00:28 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Jan 11 00:00:29 wireless: ath0     New Access Point/Cell address:00:27:22:AC:C9:FC
Jan 11 00:00:32 wireless: ath0     Received deauth from 00:27:22:ac:c9:fc. Reason: 4-way keying handshake timeout (15).
Jan 11 00:00:36 wireless: ath0     New Access Point/Cell address:Not-Associated
Jan 11 00:00:41 wireless: ath0     Set Mode:Managed
Jan 11 00:00:41 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Jan 11 00:00:42 wireless: ath0     New Access Point/Cell address:00:27:22:AC:C9:FC
Jan 11 00:00:44 wireless: ath0     Received deauth from 00:27:22:ac:c9:fc. Reason: 4-way keying handshake timeout (15).
Jan 11 00:00:49 wireless: ath0     New Access Point/Cell address:Not-Associated
Jan 11 00:00:54 wireless: ath0     Set Mode:Managed
Jan 11 00:00:54 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Jan 11 00:00:55 wireless: ath0     New Access Point/Cell address:00:27:22:AC:C9:FC
Jan 11 00:00:57 wireless: ath0     Received deauth from 00:27:22:ac:c9:fc. Reason: 4-way keying handshake timeout (15).
Jan 11 00:01:02 wireless: ath0     New Access Point/Cell address:Not-Associated
Jan 11 00:01:07 wireless: ath0     Set Mode:Managed
Jan 11 00:01:07 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Jan 11 00:01:08 wireless: ath0     New Access Point/Cell address:00:27:22:AC:C9:FC
Jan 11 00:01:10 wireless: ath0     Received deauth from 00:27:22:ac:c9:fc. Reason: 4-way keying handshake timeout (15).
Jan 11 00:01:15 wireless: ath0     New Access Point/Cell address:Not-Associated
Jan 11 00:01:20 wireless: ath0     Set Mode:Managed
Jan 11 00:01:20 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Jan 11 00:01:21 wireless: ath0     New Access Point/Cell address:00:27:22:AC:C9:FC
Jan 11 00:01:23 wireless: ath0     Received deauth from 00:27:22:ac:c9:fc. Reason: 4-way keying handshake timeout (15).
Jan 11 00:01:28 wireless: ath0     New Access Point/Cell address:Not-Associated
Jan 11 00:01:33 wireless: ath0     Set Mode:Managed
Jan 11 00:01:33 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Jan 11 00:01:34 wireless: ath0     New Access Point/Cell address:00:27:22:AC:C9:FC
Jan 11 00:01:36 wireless: ath0     Received deauth from 00:27:22:ac:c9:fc. Reason: 4-way keying handshake timeout (15).
Jan 11 00:01:41 wireless: ath0     New Access Point/Cell address:Not-Associated
Jan 11 00:01:46 wireless: ath0     Set Mode:Managed
Jan 11 00:01:46 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Jan 11 00:01:47 wireless: ath0     New Access Point/Cell address:00:27:22:AC:C9:FC
Jan 11 00:01:49 wireless: ath0     Received deauth from 00:27:22:ac:c9:fc. Reason: 4-way keying handshake timeout (15).
Jan 11 00:01:50 httpd[3017]: Password auth succeeded for 'ubnt' from 192.168.11.131
Jan 11 00:01:54 wireless: ath0     New Access Point/Cell address:Not-Associated
Jan 11 00:01:59 wireless: ath0     Set Mode:Managed
Jan 11 00:01:59 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Jan 11 00:02:00 wireless: ath0     New Access Point/Cell address:00:27:22:AC:C9:FC
Jan 11 00:02:02 wireless: ath0     Received deauth from 00:27:22:ac:c9:fc. Reason: 4-way keying handshake timeout (15).
Jan 11 00:02:07 wireless: ath0     New Access Point/Cell address:Not-Associated
Jan 11 00:02:12 wireless: ath0     Set Mode:Managed
Jan 11 00:02:12 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Jan 11 00:02:13 wireless: ath0     New Access Point/Cell address:00:27:22:AC:C9:FC
Jan 11 00:02:15 wireless: ath0     Received deauth from 00:27:22:ac:c9:fc. Reason: 4-way keying handshake timeout (15).
Jan 11 00:02:20 wireless: ath0     New Access Point/Cell address:Not-Associated
Jan 11 00:02:25 wireless: ath0     Set Mode:Managed
Jan 11 00:02:25 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Jan 11 00:02:26 wireless: ath0     New Access Point/Cell address:00:27:22:AC:C9:FC
Jan 11 00:02:28 wireless: ath0     Received deauth from 00:27:22:ac:c9:fc. Reason: 4-way keying handshake timeout (15).
Jan 11 00:02:32 wireless: ath0     New Access Point/Cell address:Not-Associated
Jan 11 00:02:38 wireless: ath0     Set Mode:Managed
Jan 11 00:02:38 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Jan 11 00:02:39 wireless: ath0     New Access Point/Cell address:00:27:22:AC:C9:FC
Jan 11 00:02:41 wireless: ath0     Received deauth from 00:27:22:ac:c9:fc. Reason: 4-way keying handshake timeout (15).
Jan 11 00:02:46 wireless: ath0     New Access Point/Cell address:Not-Associated
Jan 11 00:02:51 wireless: ath0     Set Mode:Managed
Jan 11 00:02:51 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Jan 11 00:02:52 wireless: ath0     New Access Point/Cell address:00:27:22:AC:C9:FC
Jan 11 00:02:54 wireless: ath0     Received deauth from 00:27:22:ac:c9:fc. Reason: 4-way keying handshake timeout (15).
Jan 11 00:02:59 wireless: ath0     New Access Point/Cell address:Not-Associated
Jan 11 00:03:04 wireless: ath0     Set Mode:Managed
Jan 11 00:03:04 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Jan 11 00:03:05 wireless: ath0     New Access Point/Cell address:00:27:22:AC:C9:FC
Jan 11 00:03:07 wireless: ath0     Received deauth from 00:27:22:ac:c9:fc. Reason: 4-way keying handshake timeout (15).
Jan 11 00:03:12 wireless: ath0     New Access Point/Cell address:Not-Associated
Jan 11 00:03:17 wireless: ath0     Set Mode:Managed
Jan 11 00:03:17 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Jan 11 00:03:18 wireless: ath0     New Access Point/Cell address:00:27:22:AC:C9:FC
Jan 11 00:03:20 wireless: ath0     Received deauth from 00:27:22:ac:c9:fc. Reason: 4-way keying handshake timeout (15).
Jan 11 00:03:25 wireless: ath0     New Access Point/Cell address:Not-Associated
Jan 11 00:03:30 wireless: ath0     Set Mode:Managed
Jan 11 00:03:30 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Jan 11 00:03:31 wireless: ath0     New Access Point/Cell address:00:27:22:AC:C9:FC
Jan 11 00:03:33 wireless: ath0     Received deauth from 00:27:22:ac:c9:fc. Reason: 4-way keying handshake timeout (15).
Jan 11 00:03:38 wireless: ath0     New Access Point/Cell address:Not-Associated
Jan 11 00:03:43 wireless: ath0     Set Mode:Managed
Jan 11 00:03:43 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Jan 11 00:03:44 wireless: ath0     New Access Point/Cell address:00:27:22:AC:C9:FC
Jan 11 00:03:46 wireless: ath0     Received deauth from 00:27:22:ac:c9:fc. Reason: 4-way keying handshake timeout (15).

 

 

Log from the new nano 

Reply