Deco BE11000 V2.6 on 1.2.10 — Node crashing with iptables errors and user.emerg in logs

Deco BE11000 V2.6 on 1.2.10 — Node crashing with iptables errors and user.emerg in logs

Deco BE11000 V2.6 on 1.2.10 — Node crashing with iptables errors and user.emerg in logs
Deco BE11000 V2.6 on 1.2.10 — Node crashing with iptables errors and user.emerg in logs
Yesterday
Model: Deco BE11000  
Hardware Version: V2
Firmware Version: 1.2.10

Deco BE11000 V2.6 on 1.2.10 — Node crashing with iptables errors and user.emerg in logs (twice today)

Device: Deco BE11000 V2.6 (3-pack, Costco)
Firmware: 1.2.10 Build 20251229 REL.42008
Setup: Wired MoCA coax backhaul, 3 nodes
ISP: ~310 Mbps down / 110 Mbps up

---

Twice today my Bedroom node went offline and required a manual reboot to recover. The node is wired via MoCA coax backhaul — not wireless — so this is not a signal or backhaul issue.

I exported the system log during the second crash and found the following errors repeating:

• daemon.err client_mgmt: Failed to ubus invoke
• user.err: Error: ssh_channel_read_timeout reached an end
• daemon.err uhttpd: iptables: No chain/target/match by that name
• daemon.err uhttpd: Couldn't load target 'domain_login_rule': No such file or directory
• user.emerg (highest severity system event)

The 2.4 GHz radio on the affected node (ath02, channel 10) appears stuck in a continuous inspection loop, and the iptables firewall rules are failing to load — specifically the domain_login_rule chain. The user.emerg event is the most concerning as this is the highest severity log level.

The node had been stable for a long time prior to today. Both crashes occurred within a few hours of each other. After each reboot it recovered fine.

I have confirmed:
• All three nodes are on the same firmware version (1.2.10 Build 20251229)
• Wired backhaul is intact and functioning (throuhg Moca Coax)
• No recent hardware or network changes

I am aware of the NAT Loopback beta fix (1.2.10 Build 20260212). The iptables errors in my log appear related to the same underlying firewall rule handling, so I may try that patch if crashes continue.

Has anyone else seen these specific log errors on 1.2.10? Is this addressed in the 1.3.0 official release? Any guidance appreciated.

  0      
  0      
#1
Options
2 Reply
Re:Deco BE11000 V2.6 on 1.2.10 — Node crashing with iptables errors and user.emerg in logs
Yesterday

  @DJAlcatraz 

 

First please access the Deco web UI by entering "tplinkdeco.net" in your browser. Navigate to Advanced > System > System Log, select "ALL" in the log type, and save the file to your local computer. Then follow the steps below making sure to attach the logs to the email.

I recommend sending an email to forumsupport.usa@tp-link.com with the following information:

Subject: [Forum Escalation][ID 861498Deco BE11000 V2.6 on 1.2.10 — Node crashing with iptables errors and user.emerg in logs

Forum Nickname: [User Provided]

Thread URL: https://community.tp-link.com/us/home/forum/topic/861498?moduleId=2424

Model&Version: [User Provided]

Description: [User Provided]

Any Other Relevant Information (Logs, Config Files, Images, etc.): [User Provided]

In the template above please fill in the areas that say [User Provided].  This will open a case with our engineering team, and they will work with you via email. 

 

Need help with the Deco app, setup, Ethernet backhaul, network switch or rolling back firmware? Router or AP mode? https://community.tp-link.com/us/home/forum/topic/699816?page=1
  0  
  0  
#2
Options
Re:Deco BE11000 V2.6 on 1.2.10 — Node crashing with iptables errors and user.emerg in logs
Yesterday

  @HelpFixDecoApp Thank you so very much. 

  0  
  0  
#3
Options

Information

Helpful: 0

Views: 58

Replies: 2