Deco M4 Internet outages on some clients

Deco M4 Internet outages on some clients

Deco M4 Internet outages on some clients
Deco M4 Internet outages on some clients
2024-05-02 13:38:31
Model: Deco M4  
Hardware Version: V2
Firmware Version: 1.6.2 Build 20240308 Rel. 55841

Hi,

 

I have the following setup:

 

  • Teltonika TRB500 router with good connection on Mobile WAN, no issues, 180Mbs downlink
    • 192.168.2.1, DHCP active 192.168.2.1 --> 
    • Only connected device = Deco main unit, wired
       
  • 3 x Deco M4 Mesh
    • 192.168.1.1
    • DHCP active, 192.168.1.100 --> 
    • Mesh = +2 Deco with wire
    • About 30-40 Wifi clients, 10 LAN clients
  • Mostly ESP / Tuya / Other IoT devices
  • Couple Xboxes, TV, computers etc.
  • 5 x LAN cameras 

 

Problem

 

  • Suddenly the Wifi dropped few clients out, like Xbox.
  • My phone also dropped to "Not connected to Internet" but Wifi remained active.
  • PC was really sluggish. Ping worked to 192.168.1.1 / 8.8.8.8 / www.google.com just fine, but any page couldn't be loaded with Chrome.
    • Speedtest worked 1/10, usually ended up "Network error" or download OK but upload failed.

​​​​

Troubleshooting

 

  • Rebooted 4G router, no change
  • Rebooted Deco via App, no change
  • Moved DHCP away from Deco --> AP mode. No change

 

After 10 minutes everything went back to normal.

 

This has happened now maybe 5 times for the past couple of months. I'm pretty much the "not liked" person in my house, because can't get it fixed.

 

I have the logs on my computer (Deco / Teltonika), but wouldn't like to share them for public because possible data security issues. 

 

Some interesting lines from todays event, CRITICAL level:

 

Thu May  2 15:48:58 2024 user.emerg syslog: tp217,505[5705]:
Thu May  2 15:48:59 2024 user.emerg syslog: tp215,21[5748]:
Thu May  2 15:49:00 2024 daemon.err client_mgmt: wireless client associate or disassociate.
Thu May  2 15:49:00 2024 daemon.err client_mgmt: client_mac:72-49-DE-B6-6A-EB, client_ifname:ath1, client_action:associate
Thu May  2 15:49:00 2024 daemon.err client_mgmt: client(72-49-DE-B6-6A-EB) assocaite by if(ath1).
Thu May  2 15:49:03 2024 daemon.err nrd[5915]: netdb_apHandleResolveWlanIfaces: Failed to resolve radio and VAP names from 
Thu May  2 15:49:03 2024 daemon.err nrd[5915]: netdb_apHandleCreate: Failed to resolve wlan ifaces
Thu May  2 15:49:03 2024 daemon.err nrd[5915]: nrd init failed!
Thu May  2 15:49:04 2024 daemon.err client_mgmt: wireless client associate or disassociate.
Thu May  2 15:49:04 2024 daemon.err client_mgmt: client_mac:78-11-DC-80-57-C7, client_ifname:ath0, client_action:disassociate
Thu May  2 15:49:04 2024 daemon.err client_mgmt: client(78-11-DC-80-57-C7) disassocaite by if(ath0).
Thu May  2 15:49:04 2024 daemon.err client_mgmt: wireless client associate or disassociate.
Thu May  2 15:49:04 2024 daemon.err client_mgmt: client_mac:C8-C9-A3-0B-CF-C3, client_ifname:ath0, client_action:disassociate
Thu May  2 15:49:04 2024 daemon.err client_mgmt: client(C8-C9-A3-0B-CF-C3) disassocaite by if(ath0).
Thu May  2 15:49:04 2024 daemon.err client_mgmt: wireless client associate or disassociate.
Thu May  2 15:49:04 2024 daemon.err client_mgmt: client_mac:E8-68-E7-89-0E-ED, client_ifname:ath0, client_action:disassociate
Thu May  2 15:49:04 2024 daemon.err client_mgmt: client(E8-68-E7-89-0E-ED) disassocaite by if(ath0).
Thu May  2 15:49:04 2024 daemon.err client_mgmt: wireless client associate or disassociate.
Thu May  2 15:49:04 2024 daemon.err client_mgmt: client_mac:C8-2B-96-DB-1F-D4, client_ifname:ath0, client_action:disassociate
Thu May  2 15:49:04 2024 daemon.err client_mgmt: client(C8-2B-96-DB-1F-D4) disassocaite by if(ath0).
Thu May  2 15:49:04 2024 daemon.err client_mgmt: wireless client associate or disassociate.
Thu May  2 15:49:04 2024 daemon.err client_mgmt: client_mac:1C-90-FF-04-7F-90, client_ifname:ath0, client_action:disassociate
Thu May  2 15:49:04 2024 daemon.err client_mgmt: client(1C-90-FF-04-7F-90) disassocaite by if(ath0).
Thu May  2 15:49:04 2024 daemon.err client_mgmt: wireless client associate or disassociate.
Thu May  2 15:49:04 2024 daemon.err client_mgmt: client_mac:1C-90-FF-74-11-14, client_ifname:ath0, client_action:disassociate
Thu May  2 15:49:04 2024 daemon.err client_mgmt: client(1C-90-FF-74-11-14) disassocaite by if(ath0).
Thu May  2 15:49:04 2024 daemon.err client_mgmt: wireless client associate or disassociate.
Thu May  2 15:49:04 2024 daemon.err client_mgmt: client_mac:00-22-6C-0E-88-33, client_ifname:ath0, client_action:disassociate
Thu May  2 15:49:04 2024 daemon.err client_mgmt: client(00-22-6C-0E-88-33)
disassocaite by if(ath0).
Thu May  2 15:49:04 2024 daemon.err client_mgmt: wireless client associate or disassociate.

 

* * *

 

Thu May  2 15:49:37 2024 user.emerg syslog: tp211,51[6717]:
Thu May  2 15:49:37 2024 user.emerg syslog: tp211,502[6717]:
Thu May  2 15:49:37 2024 user.emerg syslog: tp211,1[6717]:
Thu May  2 15:49:37 2024 daemon.emerg procd: Normal env generate
Thu May  2 15:49:37 2024 daemon.emerg procd: /etc/rc.common: eval: line 1: __network_device: not found
Thu May  2 15:49:38 2024 daemon.emerg procd: /etc/rc.common: eval: line 1: __network_device: not found
Thu May  2 15:49:38 2024 daemon.emerg procd: Flush nat forwarding chain
Thu May  2 15:49:38 2024 daemon.err nrd[7024]: netdb_apHandleResolveWlanIfaces: Failed to resolve radio and VAP names from 
Thu May  2 15:49:38 2024 daemon.err nrd[7024]: netdb_apHandleCreate: Failed to resolve wlan ifaces
Thu May  2 15:49:38 2024 daemon.err nrd[7024]: nrd init failed!
Thu May  2 15:49:39 2024 daemon.emerg procd: Sorry, rule does not exist.
Thu May  2 15:49:40 2024 daemon.emerg procd: Sorry, rule does not exist.
Thu May  2 15:49:43 2024 daemon.emerg procd: killall: leds_set_nightmode: no process killed
Thu May  2 15:49:43 2024 daemon.emerg procd: uci: Entry not found
Thu May  2 15:49:43 2024 daemon.err nrd[7214]: netdb_apHandleResolveWlanIfaces: Failed to resolve radio and VAP names from 
Thu May  2 15:49:43 2024 daemon.err nrd[7214]: netdb_apHandleCreate: Failed to resolve wlan ifaces
Thu May  2 15:49:43 2024 daemon.err nrd[7214]: nrd init failed!

 

* * *

Thu May  2 15:49:47 2024 daemon.emerg procd: uci: Entry not found
Thu May  2 15:49:48 2024 daemon.emerg procd: uci: Entry not found
Thu May  2 15:49:48 2024 daemon.emerg procd: uci: Entry not found
Thu May  2 15:49:48 2024 daemon.emerg procd: uci: Entry not found
Thu May  2 15:49:48 2024 daemon.emerg procd: uci: Entry not found
Thu May  2 15:49:48 2024 daemon.emerg procd: uci: Entry not found
Thu May  2 15:49:48 2024 daemon.emerg procd: uci: Entry not found
Thu May  2 15:49:48 2024 daemon.emerg procd: uci: Entry not found
Thu May  2 15:49:48 2024 daemon.emerg procd: uci: Entry not found
Thu May  2 15:49:48 2024 daemon.emerg procd: uci: Entry not found
Thu May  2 15:49:49 2024 daemon.emerg procd: uci: Entry not found
Thu May  2 15:49:49 2024 daemon.emerg procd: uci: Entry not found
Thu May  2 15:49:49 2024 daemon.emerg procd: uci: Entry not found
Thu May  2 15:49:49 2024 daemon.emerg procd: uci: Entry not found
Thu May  2 15:49:50 2024 user.emerg IMPROXY: FATAL[init_interface@251]: exiting.....
Thu May  2 15:49:55 2024 user.emerg IMPROXY: FATAL[init_interface@251]: exiting.....
Thu May  2 15:50:00 2024 user.emerg IMPROXY: FATAL[init_interface@251]: exiting.....
Thu May  2 15:50:05 2024 user.emerg IMPROXY: FATAL[init_interface@251]: exiting.....
Thu May  2 15:53:32 2024 user.emerg syslog: tp217,505[13716]:
Thu May  2 15:53:33 2024 user.emerg syslog: tp215,21[13754]:
Thu May  2 16:07:35 2024 user.emerg syslog: tp217,505[28904]:
Thu May  2 16:08:53 2024 user.emerg syslog: tp215,22[30970]:

 

* * *

Thu May  2 16:12:41 2024 daemon.err nrd[8831]: estimatorCmnHandleBeaconReportEvent: Invalid beacon report for 1C:90:FF:04:7F:90
Thu May  2 16:12:46 2024 daemon.err nrd[8831]: estimatorCmnHandleBeaconReportEvent: Invalid beacon report for 38:1F:8D:41:E5:E3
Thu May  2 16:12:48 2024 daemon.err nrd[8831]: estimatorCmnHandleBeaconReportEvent: Invalid beacon report for 1C:90:FF:04:7F:90
Thu May  2 16:12:52 2024 daemon.err nrd[8831]: estimatorCmnHandleBeaconReportEvent: Invalid beacon report for 38:1F:8D:41:E5:E3
Thu May  2 16:12:53 2024 daemon.err nrd[8831]: estimatorCmnHandleBeaconReportEvent: Invalid beacon report for 1C:90:FF:04:7F:90
Thu May  2 16:12:59 2024 daemon.err nrd[8831]: estimatorCmnHandleBeaconReportEvent: Invalid beacon report for 38:1F:8D:41:E5:E3
Thu May  2 16:13:00 2024 daemon.err nrd[8831]: estimatorCmnHandleBeaconReportEvent: Invalid beacon report for 1C:90:FF:04:7F:90

 

* * *

  0      
  0      
#1
Options
1 Reply
Re:Deco M4 Internet outages on some clients
2024-05-11 06:30:23

  @SaiQmon 

Hi, Thank you very much for the feedback.

I saw you have also updated the Deco M4 to the latest 1.7.0 beta.

It is suggested to set Deco M4 back to Access Point mode, then please also try to turn off "fast roaming" and "beamforming" under Deco APP>More>Advanced.

After that, for the frequently disconnected IOT devices, please also disable "Mesh Technology" first.

 

By the way, have you experienced any disconnection issues on the wired clients?

 

I saw you mentioned about 30 devices are connected to the IOT network which is, I support 2.4GHz only. Have you tried to leave the main Wi-Fi network on 5GHz only, then test whether the mobile phone/Xbox/PC still randomly dropped out?

Thank you very much and best regards.

 

  0  
  0  
#2
Options

Information

Helpful: 0

Views: 151

Replies: 1

Related Articles