Archer C80 1.0: hangs on attempt to use EasyMesh, exception in system log

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

Archer C80 1.0: hangs on attempt to use EasyMesh, exception in system log

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Archer C80 1.0: hangs on attempt to use EasyMesh, exception in system log
Archer C80 1.0: hangs on attempt to use EasyMesh, exception in system log
2024-01-15 21:09:01
Model: Archer C80  
Hardware Version: V1
Firmware Version: 1.13.2 Build 230824 Rel.74702n(4555)

I've bought Archer C80 plus RE315 for my home network setup. Before the firmware had an option to support Ethernet-backhauled mesh (since the only points I could put the devices are located in a way that blocks direct radio) I used them as 2 separate Wi-Fi networks. After recent firmware updates I tried to setup the EasyMesh, and while the devices have easily agreed to setup one it didn't really work. I guess the Re315 was loosing the radio connection to the Archer C80 and was always trying to reestablish it. On top of that, while Re315 was busy establishing the connection, my PC connected to the Archer router started loosing speed. After checking the system logs I've found that router has recorded an exception. I've switched off the repeater and the router went back to operating normally.

 

Here I attach the whole log. I've cleaned it up before the latest test.


##########################################################################
#                    Archer C80  System Log
# Time = 2024-01-15 22:20:01 670s
# H-Ver = Archer C80 1.0 : S-Ver = 1.13.2 Build 230824 Rel.74702n(4555)
# L = 192.168.0.1 : M = 255.255.255.0
# WAN = DHCP : W = 192.168.10.10 : M = 255.255.255.0 : G = 192.168.10.254
# Cnt = 10624, Free = 10540, Busy = 84
##########################################################################
  0days, 00:00:06, [tmpd]register tmp app, type: 1
  0days, 00:00:06, [portal]portal init

  0days, 00:00:06, [lan]LAN: Set interface br-lan0 ip=192.168.0.1 netmask 255.255.255.0.
  0days, 00:00:06, [tmpd]register tmp app, type: 2
  0days, 00:00:07, [tmpd]register tmp app, type: 4
  0days, 00:00:30, [DSLite]Dslite disable
  0days, 00:00:30, [portal]portal not enabled

  0days, 00:00:30, [portal]portal stop

  0days, 00:00:30, [httpd]Http server start!
  0days, 00:00:34, [wan]Wan ethernet port plug on.
  0days, 00:00:35, [dhcpc]Send DISCOVER with unicast flag 0
  0days, 00:00:37, [dhcps]Send OFFER with ip 192.168.0.110.
  0days, 00:00:37, [dhcpc]Send DISCOVER with unicast flag 0
  0days, 00:00:37, [dhcpc]Recv OFFER from server 192.168.10.254 with ip 192.168.10.10
  0days, 00:00:37, [dhcpc]Send REQUEST to server 192.168.10.254 with request ip 192.168.10.10
  0days, 00:00:38, [dhcps]Send ACK to 192.168.0.110.
  0days, 00:00:38, [dhcpc]eth0 set ip 192.168.10.10 mask 255.255.255.0 gateway 192.168.10.254
  0days, 00:00:38, [wan]advanced ddns -wanChanged
  0days, 00:00:38, [wan]systool sntpc -sntpRequest
  0days, 00:00:38, [dnsproxy]Register Dns Detect
  0days, 00:00:38, [dnsproxy]Register primary = 0xc59bcfd5, secondary = 0x1010101
  0days, 00:00:38, [inetd]INETD: select error, abort.
  0days, 00:00:38, [cwmp]cwmp is not start
  0days, 00:01:03, [dhcps]Send OFFER with ip 192.168.0.105.
  0days, 00:01:03, [dhcps]Send ACK to 192.168.0.105.
  0days, 00:01:10, [dhcps]Send OFFER with ip 192.168.0.105.
  0days, 00:01:10, [dhcps]Send ACK to 192.168.0.105.
  0days, 00:01:33, [dhcps]Send OFFER with ip 192.168.0.105.
  0days, 00:01:33, [dhcps]Send ACK to 192.168.0.105.
  0days, 00:02:00, [dhcps]Send OFFER with ip 192.168.0.105.
  0days, 00:02:00, [dhcps]Send ACK to 192.168.0.105.
  0days, 00:02:18, [dhcps]Send OFFER with ip 192.168.0.105.
  0days, 00:02:18, [dhcps]Send OFFER with ip 192.168.0.105.
  0days, 00:02:18, [dhcps]Send ACK to 192.168.0.105.
  0days, 00:02:18, [dhcps]Send OFFER with ip 192.168.0.105.
  0days, 00:02:18, [dhcps]Send ACK to 192.168.0.105.
  0days, 00:02:27, [dhcps]Send OFFER with ip 192.168.0.105.
  0days, 00:02:27, [dhcps]Send ACK to 192.168.0.105.
  0days, 00:02:49, [dhcps]Send OFFER with ip 192.168.0.105.
  0days, 00:02:49, [dhcps]Send ACK to 192.168.0.105.
  0days, 00:03:02, [dhcps]Send OFFER with ip 192.168.0.105.
  0days, 00:03:02, [dhcps]Send ACK to 192.168.0.105.
  0days, 00:03:28, [dhcps]Send OFFER with ip 192.168.0.105.
  0days, 00:03:28, [dhcps]Send ACK to 192.168.0.105.
  0days, 00:03:31, [dhcps]192.168.0.105 belongs to someone, reserving it for 600 seconds.
  0days, 00:03:31, [dhcps]Send ACK to 192.168.0.105.
  0days, 00:03:33, [dhcps]Send OFFER with ip 192.168.0.100.
  0days, 00:03:33, [dhcps]Send ACK to 192.168.0.100.
  0days, 00:03:43, [dhcps]Send OFFER with ip 192.168.0.101.
  0days, 00:03:44, [dhcps]Send ACK to 192.168.0.101.
  0days, 00:04:21, [dhcps]Send OFFER with ip 192.168.0.102.
  0days, 00:04:22, [dhcps]Send ACK to 192.168.0.102.
  0days, 00:04:34, [dhcps]Send OFFER with ip 192.168.0.102.
  0days, 00:04:34, [dhcps]Send ACK to 192.168.0.102.
  0days, 00:05:01, [dhcps]Send OFFER with ip 192.168.0.102.
  0days, 00:05:01, [dhcps]Send ACK to 192.168.0.102.
  0days, 00:05:16, [dhcps]Send OFFER with ip 192.168.0.102.
  0days, 00:05:16, [dhcps]Send OFFER with ip 192.168.0.102.
  0days, 00:05:16, [dhcps]192.168.0.102 belongs to someone, reserving it for 600 seconds.
  0days, 00:05:16, [dhcps]Send ACK to 192.168.0.102.
  0days, 00:05:16, [dhcps]REQUEST ip c0a80066 already reserved by 00:00:00:00:00:00
  0days, 00:05:17, [dhcps]Send OFFER with ip 192.168.0.101.
  0days, 00:05:17, [dhcps]Send OFFER with ip 192.168.0.101.
  0days, 00:05:17, [dhcps]Send OFFER with ip 192.168.0.101.
  0days, 00:05:17, [dhcps]Send ACK to 192.168.0.101.
  0days, 00:05:17, [dhcps]Send OFFER with ip 192.168.0.101.
  0days, 00:05:17, [dhcps]192.168.0.101 belongs to someone, reserving it for 600 seconds.
  0days, 00:05:17, [dhcps]Send ACK to 192.168.0.101.
  0days, 00:05:17, [dhcps]REQUEST ip c0a80065 already reserved by 00:00:00:00:00:00
  0days, 00:05:20, [dhcps]Send OFFER with ip 192.168.0.100.
  0days, 00:05:21, [dhcps]Send ACK to 192.168.0.100.
  0days, 00:05:42, [dhcps]Send OFFER with ip 192.168.0.103.
  0days, 00:05:43, [dhcps]Send ACK to 192.168.0.103.
  0days, 00:05:56, [dhcps]Send OFFER with ip 192.168.0.103.
  0days, 00:05:56, [dhcps]Send OFFER with ip 192.168.0.103.
  0days, 00:05:56, [dhcps]Send OFFER with ip 192.168.0.103.
  0days, 00:05:56, [dhcps]Send OFFER with ip 192.168.0.103.
  0days, 00:05:56, [dhcps]Send ACK to 192.168.0.103.
  0days, 00:05:56, [dhcps]Send ACK to 192.168.0.103.
  0days, 00:05:59, [dhcps]Send OFFER with ip 192.168.0.103.
  0days, 00:05:59, [dhcps]Send ACK to 192.168.0.103.
  0days, 00:06:22, [dhcps]Send OFFER with ip 192.168.0.103.
  0days, 00:06:22, [dhcps]Send ACK to 192.168.0.103.
  0days, 00:06:37, [dhcps]Send OFFER with ip 192.168.0.103.
  0days, 00:06:37, [dhcps]Send OFFER with ip 192.168.0.103.
  0days, 00:06:37, [dhcps]Send OFFER with ip 192.168.0.103.
  0days, 00:06:37, [dhcps]Send OFFER with ip 192.168.0.103.
  0days, 00:06:37, [dhcps]Send ACK to 192.168.0.103.
  0days, 00:06:37, [dhcps]Send OFFER with ip 192.168.0.103.
  0days, 00:06:37, [dhcps]Send ACK to 192.168.0.103.
  0days, 00:06:37, [dhcps]Send OFFER with ip 192.168.0.103.
  0days, 00:06:37, [dhcps]192.168.0.103 belongs to someone, reserving it for 600 seconds.
  0days, 00:06:37, [dhcps]Send ACK to 192.168.0.103.
  0days, 00:06:37, [dhcps]REQUEST ip c0a80067 already reserved by 00:00:00:00:00:00
  0days, 00:06:43, [dhcps]Send OFFER with ip 192.168.0.104.
  0days, 00:06:43, [dhcps]Send ACK to 192.168.0.104.
  0days, 00:07:09, [dhcps]Send OFFER with ip 192.168.0.104.
  0days, 00:07:09, [dhcps]Send ACK to 192.168.0.104.
  0days, 00:07:23, [dhcps]Send OFFER with ip 192.168.0.104.
  0days, 00:07:23, [dhcps]Send OFFER with ip 192.168.0.104.
  0days, 00:07:23, [dhcps]Send OFFER with ip 192.168.0.104.
  0days, 00:07:23, [dhcps]Send ACK to 192.168.0.104.
  0days, 00:07:23, [dhcps]Send ACK to 192.168.0.104.
  0days, 00:07:27, [dhcps]Send OFFER with ip 192.168.0.104.
  0days, 00:07:27, [dhcps]Send ACK to 192.168.0.104.
  0days, 00:07:50, [dhcps]Send OFFER with ip 192.168.0.104.
  0days, 00:07:50, [dhcps]Send ACK to 192.168.0.104.
  0days, 00:07:53, [dhcps]192.168.0.104 belongs to someone, reserving it for 600 seconds.
  0days, 00:07:53, [dhcps]Send ACK to 192.168.0.104.
  0days, 00:07:54, [dhcps]Send OFFER with ip 192.168.0.100.
  0days, 00:07:54, [dhcps]Send ACK to 192.168.0.100.
  0days, 00:08:07, [dhcps]Send OFFER with ip 192.168.0.106.
  0days, 00:08:07, [dhcps]Send ACK to 192.168.0.106.
  0days, 00:08:45, [dhcps]Send OFFER with ip 192.168.0.107.
  0days, 00:08:46, [dhcps]Send ACK to 192.168.0.107.
  0days, 00:08:59, [dhcps]Send OFFER with ip 192.168.0.107.
  0days, 00:08:59, [dhcps]Send OFFER with ip 192.168.0.107.
  0days, 00:08:59, [dhcps]Send OFFER with ip 192.168.0.107.
  0days, 00:08:59, [dhcps]Send OFFER with ip 192.168.0.107.
  0days, 00:09:00, [dhcps]Send OFFER with ip 192.168.0.107.
  0days, 00:09:00, [dhcps]192.168.0.107 belongs to someone, reserving it for 600 seconds.
  0days, 00:09:00, [dhcps]Send ACK to 192.168.0.107.
  0days, 00:09:00, [dhcps]Send OFFER with ip 192.168.0.108.
  0days, 00:09:00, [dhcps]Send NAK to 0, lease ip c0a8006c.
  0days, 00:09:00, [dhcps]Send OFFER with ip 192.168.0.108.
  0days, 00:09:00, [dhcps]Send NAK to 0, lease ip c0a8006c.
  0days, 00:09:00, [dhcps]Send OFFER with ip 192.168.0.108.
  0days, 00:09:00, [dhcps]Send NAK to 0, lease ip c0a8006c.
  0days, 00:09:00, [dhcps]Send NAK to 0, lease ip c0a8006c.
  0days, 00:09:00, [dhcps]Send OFFER with ip 192.168.0.106.
  0days, 00:09:00, [dhcps]Send OFFER with ip 192.168.0.106.
  0days, 00:09:00, [dhcps]Send OFFER with ip 192.168.0.106.
  0days, 00:09:01, [dhcps]Send ACK to 192.168.0.106.
  0days, 00:09:01, [dhcps]Send ACK to 192.168.0.106.
  0days, 00:09:01, [dhcps]Send ACK to 192.168.0.106.
  0days, 00:09:01, [dhcps]192.168.0.106 belongs to someone, reserving it for 600 seconds.
  0days, 00:09:01, [dhcps]Send ACK to 192.168.0.106.
  0days, 00:09:01, [dhcps]REQUEST ip c0a8006a already reserved by 00:00:00:00:00:00
  0days, 00:09:28, [dhcps]Send OFFER with ip 192.168.0.108.
  0days, 00:09:29, [dhcps]Send ACK to 192.168.0.108.
  0days, 00:09:42, [dhcps]Send OFFER with ip 192.168.0.108.
  0days, 00:09:42, [dhcps]Send OFFER with ip 192.168.0.108.
  0days, 00:09:42, [dhcps]Send OFFER with ip 192.168.0.108.
  0days, 00:09:42, [dhcps]Send ACK to 192.168.0.108.
  0days, 00:09:42, [dhcps]Send ACK to 192.168.0.108.
  0days, 00:09:48, [dhcps]Send OFFER with ip 192.168.0.108.
  0days, 00:09:48, [dhcps]Send ACK to 192.168.0.108.
  0days, 00:10:09, [dhcps]Send OFFER with ip 192.168.0.108.
  0days, 00:10:09, [dhcps]Send ACK to 192.168.0.108.
  0days, 00:10:23, [dhcps]Send OFFER with ip 192.168.0.108.
  0days, 00:10:23, [dhcps]Send ACK to 192.168.0.108.
  0days, 00:10:29, [dhcps]Send OFFER with ip 192.168.0.108.
  0days, 00:10:46, [dhcps]Send OFFER with ip 192.168.0.108.
  0days, 00:10:46, [dhcps]Send ACK to 192.168.0.108.
  0days, 00:11:01, [dhcps]Send OFFER with ip 192.168.0.108.
  0days, 00:11:01, [dhcps]Send OFFER with ip 192.168.0.108.
  0days, 00:11:01, [dhcps]Send OFFER with ip 192.168.0.108.
  0days, 00:11:01, [dhcps]Send OFFER with ip 192.168.0.108.
  0days, 00:11:01, [dhcps]Send ACK to 192.168.0.108.
  0days, 00:11:01, [dhcps]Send ACK to 192.168.0.108.
  0days, 00:11:01, [dhcps]Send ACK to 192.168.0.108.
  0days, 00:11:01, [dhcps]Send ACK to 192.168.0.108.
  0days, 00:11:01, [dhcps]Send ACK to 192.168.0.108.
  0days, 00:11:01, [dhcps]Send ACK to 192.168.0.108.

Exception:|2024-01-15 22:08:41|
[4-10]PC=405276b0,LR=40527d5c
->[404d9de4]->[404e7ca8]->[4039d020]->[4039e194]

  0      
  0      
#1
Options
3 Reply
Re:Archer C80 1.0: hangs on attempt to use EasyMesh, exception in system log
2024-01-15 23:02:18 - last edited 2024-01-15 23:05:04

  @LDVSoft 

 

This behavior could be due to the fact that when building an Easymesh over ethernet backhaul it should fall back to a wireless backhaul if the ethernet backhaul fails.

Since the devices are located in a way that blocks direct wireless radio, this could be a reason for RE315 always trying to reestablish it.

You can test if that's the case by placing the RE315 in an Archer C80 wireless range and observe their behavior.

If this was helpful click once on the arrow pointing upward. If this solves your issue, click once the star to mark it as a "Recommended Solution".
  1  
  1  
#2
Options
Re:Archer C80 1.0: hangs on attempt to use EasyMesh, exception in system log
2024-01-16 11:26:50

  @terziyski I'd agree, but I know for sure that the wired connection is fine. I guess devices themselves might have a bit of trouble, but I don't remeber seing how RE315 was shown as radio-connected on the Archer.

  0  
  0  
#3
Options
Re:Archer C80 1.0: hangs on attempt to use EasyMesh, exception in system log
2024-01-26 18:44:22 - last edited 2024-01-27 15:40:37

  @LDVSoft 

 

"(since the only points I could put the devices are located in a way that blocks direct radio) " you've probably used the RE315 in AP mode until the ethernet backhaul has been implemented.

TP-Link support has confirmed this behavior in a similar case here.

If this was helpful click once on the arrow pointing upward. If this solves your issue, click once the star to mark it as a "Recommended Solution".
  0  
  0  
#4
Options

Information

Helpful: 0

Views: 957

Replies: 3

Related Articles