Home Network Community > Deco > Strange set-up problem with E4R
< Deco

Strange set-up problem with E4R

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Strange set-up problem with E4R

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Strange set-up problem with E4R
Strange set-up problem with E4R
2021-05-07 23:10:11 - last edited 2021-05-08 11:54:03
Model: Deco E4  
Hardware Version: V1
Firmware Version: 1.4.3 Build 20200918 Rel. 44982

Hi.

I have pretty strange problem:

I did build a MESH using 4 Deco E4R which were all connected via backhaul ethernet - 2 were directly LAN wired - 2 via Powerline equiment. Everything worked fine until today when I did change the Powerline adapters to try faster ones. When re-connecting the ethernet backhaul the whole network crashed with all 4 Deco re-booting. When the 4 Decos came up again they did not connect again. So I did a hard reset (pressing the reset button) and re-configuered the Mesh network.

 

And here the problem started: while connecting one Deco to myrouter I configure the base station without a problem. Then tried to re-set the Deco from Router to AP. The unit went down but didn't came up again (flashing red led). Resetting the unit and keeping it in "Router" mode - everything works fine. But as I have a Fritz!Box cable router I have to run the Decos as APs. Leaving the base station in router mode I am able to connect all units. I changed the base station to another Deco - and I was able to configure the base, changed into AP, connected the other untis - but the one with the "changing" problem can't connect when the base station is in AP mode. When setting the base station in "Router" mode - I can connect the unit but when changing the base unit to AP - the unit will not boot up again (flashing red again).

 

I think the easy answer is that the unit is faulty - but I'm reluctant to accept that as it did work fine before "just" changing the Powerline adapters.

 

Anyone has a tip what to try? My god feel tells me that when setting the base unit from Router to AP all connected units will be removed from the Deco IP adress range (192.168.68.xxx) and will get their adress from my Fritz router (192.168.0.xxx). And it seems that the one unit can't deal with that. But not having the chance to understand in which state of the booting process the unit fails - it isn't easy to trace down the problem.

 

Thanks for any advice.

 

-L

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:Strange set-up problem with E4R-Solution
2021-05-08 11:53:41 - last edited 2021-05-08 11:54:03

A short update:

I realized that despite fact that the TP Link app told me that all Decos are up to date there is a newer version available (1.5.1 Build 20210330 Rel. 64251) which I installed on all Decos (even the faulty one while connecting that as an additional network in router mode).

 

 

And now, while I was trying to troubleshoot further suddenly the faulty satellite connected to the base!!!???!!!

 

This is the logfile entry when suddenly the association happened:

 

Sat May  8 12:45:42 2021 daemon.notice awn[1806]: [awnd_mode_convert:4640]: The configuration is going into effect.
Sat May  8 12:46:29 2021 daemon.err client_mgmt: client_mac:72-FF-7B-9D-A0-BF, client_ifname:ath14, client_action:associate
Sat May  8 12:46:29 2021 daemon.err client_mgmt: client(72-FF-7B-9D-A0-BF) assocaite by if(ath14).
Sat May  8 12:46:29 2021 daemon.err client_mgmt: wireless client associate or disassociate.
Sat May  8 12:46:29 2021 daemon.err client_mgmt: client_mac:72-FF-7B-9D-A0-BE, client_ifname:ath04, client_action:associate
Sat May  8 12:46:29 2021 daemon.err client_mgmt: client(72-FF-7B-9D-A0-BE) assocaite by if(ath04).
Sat May  8 12:46:49 2021 daemon.err client_mgmt: client(A2-8B-34-C5-AF-36) not found in arp table disconnect_counter=0
Sat May  8 12:47:08 2021 daemon.err client_mgmt: client(A2-8B-34-C5-AF-36) not found in arp table disconnect_counter=1
Sat May  8 12:47:26 2021 daemon.err client_mgmt: client(A2-8B-34-C5-AF-36) not found in arp table disconnect_counter=2
Sat May  8 12:51:19 2021 daemon.notice awn[1806]: [awnd_onboarding_inspect:1712]: Disable config mesh network when offboarding.
Sat May  8 12:51:20 2021 daemon.notice awn[1806]: [awnd_mode_convert:4640]: The configuration is going into effect.
Sat May  8 12:51:21 2021 daemon.err client_mgmt: wireless client associate or disassociate.
Sat May  8 12:51:21 2021 daemon.err client_mgmt: client_mac:72-FF-7B-9D-A0-BE, client_ifname:ath04, client_action:disassociate
Sat May  8 12:51:21 2021 daemon.err client_mgmt: client(72-FF-7B-9D-A0-BE) disassocaite by if(ath04).
Sat May  8 12:51:21 2021 daemon.err client_mgmt: wireless client associate or disassociate.
Sat May  8 12:51:21 2021 daemon.err client_mgmt: client_mac:72-FF-7B-9D-A0-BF, client_ifname:ath14, client_action:disassociate
Sat May  8 12:51:21 2021 daemon.err client_mgmt: client(72-FF-7B-9D-A0-BF) disassocaite by if(ath14).
Sat May  8 12:53:05 2021 authpriv.warn dropbear[31740]: Login attempt for nonexistent user from 192.168.0.125:62860
Sat May  8 12:53:05 2021 authpriv.notice dropbear[31740]: Password auth succeeded from 192.168.0.125:62860
Sat May  8 12:53:15 2021 daemon.err tmpsvr[4938]: Error: tmp_trans_relay
Sat May  8 12:59:20 2021 daemon.err client_mgmt: client(A2-8B-34-C5-AF-36) not found in arp table disconnect_counter=0
Sat May  8 12:59:38 2021 daemon.err client_mgmt: client(A2-8B-34-C5-AF-36) not found in arp table disconnect_counter=1
Sat May  8 12:59:57 2021 daemon.err tmpsvr[4938]: Error: tmp_trans_relay
Sat May  8 13:00:02 2021 daemon.err tmpsvr[4938]: Error: tmp_trans_relay
Sat May  8 13:00:06 2021 daemon.err tmpsvr[4938]: Error: tmp_trans_relay
Sat May  8 13:00:10 2021 daemon.err tmpsvr[4938]: Error: tmp_trans_relay
Sat May  8 13:01:43 2021 daemon.notice awn[1806]: [awnd_onboarding_inspect:1699]: Enable config mesh network when onboarding.
Sat May  8 13:01:44 2021 daemon.notice awn[1806]: [awnd_mode_convert:4640]: The configuration is going into effect.

 

Conclusion: When ever you need to physically re-configure your Deco network  ALWAYS disconnect power first - than make any changes (i.e. Ethernet backhaul re-configuration). And check the TPLink website from time to time for any updats as the app doesn't seem to work right!

 

Recommended Solution
  0  
  0  
#4
Options
3 Reply
Re:Strange set-up problem with E4R
2021-05-08 01:17:20

@Sailor 

Hi, please try the following suggestion to have a look:

1. for the last E4, Please do not connect it to the powerline adapters at first and leave it wirelessly connected to other Deco units;

2. Then switch it to access point and after that please check whether it would be online again;

3. Finally, connect it back via powerline adapters;

As for whether it is faulty or not, you could run a simple test, use this one to replace other satellite Decos to see if it was always this one that caused the problem;

And there might be another possible reason, due to the powerline connection, this Deco might not change to access point mode successfully;

Thank you.

  0  
  0  
#2
Options
Re:Strange set-up problem with E4R
2021-05-08 08:15:38

@TP-Link Maybe I wasn't clear in my explanation: while trying to set-up the Deco which causes the problems it isn't connected through a Powerline adaptor. It sits next to the base Deco, not connected to Ethernet at all and is being configure only via WiFi.

And as such I can't replace any satellite Deco.

Status at the moment:

Base Deco in AP mode. 2 satelittes successfully connected, 4th Deco sits 40 cm away from base and is blinking blue. When using an iPAD with TPLink Deco App trying to add the blinking Deco the app times out without being able to "see" the satellite. When scanning for WLANs the blinking Deco is visible. Adding a new network to the TPLink app works with the blinking Deco becoming the base for the new network. Changing the Deco to AP mode is resulting in inaccessibility of the Deco (blinking red forever). To re-access I have to reset the Deco. I tried to connect the Deco directly to the base (through an Ethernet cable) as shown in one of the support videos - no success. Using the suspect Deco as a base results in a WLAN with a second router as the switch to AP mode does not work either.

 

Any idea?

  0  
  0  
#3
Options
Re:Strange set-up problem with E4R-Solution
2021-05-08 11:53:41 - last edited 2021-05-08 11:54:03

A short update:

I realized that despite fact that the TP Link app told me that all Decos are up to date there is a newer version available (1.5.1 Build 20210330 Rel. 64251) which I installed on all Decos (even the faulty one while connecting that as an additional network in router mode).

 

 

And now, while I was trying to troubleshoot further suddenly the faulty satellite connected to the base!!!???!!!

 

This is the logfile entry when suddenly the association happened:

 

Sat May  8 12:45:42 2021 daemon.notice awn[1806]: [awnd_mode_convert:4640]: The configuration is going into effect.
Sat May  8 12:46:29 2021 daemon.err client_mgmt: client_mac:72-FF-7B-9D-A0-BF, client_ifname:ath14, client_action:associate
Sat May  8 12:46:29 2021 daemon.err client_mgmt: client(72-FF-7B-9D-A0-BF) assocaite by if(ath14).
Sat May  8 12:46:29 2021 daemon.err client_mgmt: wireless client associate or disassociate.
Sat May  8 12:46:29 2021 daemon.err client_mgmt: client_mac:72-FF-7B-9D-A0-BE, client_ifname:ath04, client_action:associate
Sat May  8 12:46:29 2021 daemon.err client_mgmt: client(72-FF-7B-9D-A0-BE) assocaite by if(ath04).
Sat May  8 12:46:49 2021 daemon.err client_mgmt: client(A2-8B-34-C5-AF-36) not found in arp table disconnect_counter=0
Sat May  8 12:47:08 2021 daemon.err client_mgmt: client(A2-8B-34-C5-AF-36) not found in arp table disconnect_counter=1
Sat May  8 12:47:26 2021 daemon.err client_mgmt: client(A2-8B-34-C5-AF-36) not found in arp table disconnect_counter=2
Sat May  8 12:51:19 2021 daemon.notice awn[1806]: [awnd_onboarding_inspect:1712]: Disable config mesh network when offboarding.
Sat May  8 12:51:20 2021 daemon.notice awn[1806]: [awnd_mode_convert:4640]: The configuration is going into effect.
Sat May  8 12:51:21 2021 daemon.err client_mgmt: wireless client associate or disassociate.
Sat May  8 12:51:21 2021 daemon.err client_mgmt: client_mac:72-FF-7B-9D-A0-BE, client_ifname:ath04, client_action:disassociate
Sat May  8 12:51:21 2021 daemon.err client_mgmt: client(72-FF-7B-9D-A0-BE) disassocaite by if(ath04).
Sat May  8 12:51:21 2021 daemon.err client_mgmt: wireless client associate or disassociate.
Sat May  8 12:51:21 2021 daemon.err client_mgmt: client_mac:72-FF-7B-9D-A0-BF, client_ifname:ath14, client_action:disassociate
Sat May  8 12:51:21 2021 daemon.err client_mgmt: client(72-FF-7B-9D-A0-BF) disassocaite by if(ath14).
Sat May  8 12:53:05 2021 authpriv.warn dropbear[31740]: Login attempt for nonexistent user from 192.168.0.125:62860
Sat May  8 12:53:05 2021 authpriv.notice dropbear[31740]: Password auth succeeded from 192.168.0.125:62860
Sat May  8 12:53:15 2021 daemon.err tmpsvr[4938]: Error: tmp_trans_relay
Sat May  8 12:59:20 2021 daemon.err client_mgmt: client(A2-8B-34-C5-AF-36) not found in arp table disconnect_counter=0
Sat May  8 12:59:38 2021 daemon.err client_mgmt: client(A2-8B-34-C5-AF-36) not found in arp table disconnect_counter=1
Sat May  8 12:59:57 2021 daemon.err tmpsvr[4938]: Error: tmp_trans_relay
Sat May  8 13:00:02 2021 daemon.err tmpsvr[4938]: Error: tmp_trans_relay
Sat May  8 13:00:06 2021 daemon.err tmpsvr[4938]: Error: tmp_trans_relay
Sat May  8 13:00:10 2021 daemon.err tmpsvr[4938]: Error: tmp_trans_relay
Sat May  8 13:01:43 2021 daemon.notice awn[1806]: [awnd_onboarding_inspect:1699]: Enable config mesh network when onboarding.
Sat May  8 13:01:44 2021 daemon.notice awn[1806]: [awnd_mode_convert:4640]: The configuration is going into effect.

 

Conclusion: When ever you need to physically re-configure your Deco network  ALWAYS disconnect power first - than make any changes (i.e. Ethernet backhaul re-configuration). And check the TPLink website from time to time for any updats as the app doesn't seem to work right!

 

Recommended Solution
  0  
  0  
#4
Options

Information

Helpful: 0

Views: 6

Replies: 0

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.