Home Network Community > Deco > Deco S4 filling its event log after firmware update
< Deco

Deco S4 filling its event log after firmware update

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

Deco S4 filling its event log after firmware update

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Deco S4 filling its event log after firmware update
Deco S4 filling its event log after firmware update
2020-10-05 20:38:53
Model: Deco S4  
Hardware Version:
Firmware Version: 1.4.3 Build 20200918 Rel. 77820

After updating the firmware, the event log quickly fills up with the following entries. These did not appear with the older firmware.

 

Mon Oct 5 11:51:39 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address

Mon Oct 5 11:51:40 2020 user.notice IMPROXY: INFO[mcast_is_ex_hander@41]: Group 239.255.255.250 Group Compatibility Modeis lesser than IGMPV3

Mon Oct 5 11:51:41 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::2:ff9f:36b7 is link-local multicast address

Mon Oct 5 11:51:41 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::2:ff9f:36b7 is link-local multicast address

Mon Oct 5 11:52:06 2020 user.warn dnsproxy: [ 7696] [online_test_event_cb 260] nameserver isn't in the resolve.conf file!!!

 

A little Google research shows address ff02: and Group 239 belong to RFC 2365 

 

Administratively Scoped IP Multicast protocols.

I assume those messages are used while implementing the mesh protocols between nodes.  That's, fine, but why are they being logged and filling up the event log?

 

Thanks

  0      
 
  0      
 
#1
Options
10 Reply
Re:Deco S4 filling its event log after firmware update
2020-10-06 18:19:18

@RogerHi 

 

Good Question.  We will look into it and let you know.

Check out the Latest: Recent Smart Home Features and Updates for Tapo and Kasa Securing Your TP-Link ID with 2FA:Deco and Tether | Smart Home Splash into a Smarter Summer with Sub-G Sensors, Matter, and Apple Home!
  0  
  0  
#2
Options
Re:Deco S4 filling its event log after firmware update
2020-10-13 16:09:18

@RogerHi 

 

I was provided a Beta firmware that can stop the logging for these messages 

 

https://static.tp-link.com/2020/202010/20201013/s4-SP1-up-ver1-4-3-P1[20201012-rel53916]_2020-10-12_15.40.04.zip 

Check out the Latest: Recent Smart Home Features and Updates for Tapo and Kasa Securing Your TP-Link ID with 2FA:Deco and Tether | Smart Home Splash into a Smarter Summer with Sub-G Sensors, Matter, and Apple Home!
  0  
  0  
#3
Options
Re:Deco S4 filling its event log after firmware update
2020-10-14 18:19:26

@Carl   The Beta firmware appears to have fixed the problem. Thanks!   

 

I assume the fix will be included in the next official firmware release?

  0  
  0  
#4
Options
Re:Deco S4 filling its event log after firmware update
2020-10-14 20:49:09

@RogerHi 

 

I can't say for certain.  As its just a logging issue and not something that affects operation it might be lower on the list of updates.  We also don't find out what is in an update until its launched and published.  That happens typically every friday, provided its not a holiday. 

Check out the Latest: Recent Smart Home Features and Updates for Tapo and Kasa Securing Your TP-Link ID with 2FA:Deco and Tether | Smart Home Splash into a Smarter Summer with Sub-G Sensors, Matter, and Apple Home!
  0  
  0  
#5
Options
Re:Deco S4 filling its event log after firmware update
2021-10-15 07:35:35

@Carl Will this firmware update also work on the M9 Plus? I am have a very similar situation with repeating log entries that started after the most recent update.

 

Here is a sample snippet. It just goes on and on and on...multiple entries per second:

 

Thu Oct 14 22:07:51 2021 daemon.err nrd[30060]: estimatorDot11kIterateCB: Timeout waiting for 802.11k response from 86:D5:BD:84:22:84

Thu Oct 14 22:07:56 2021 user.err csrMeshGw[8132]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Thu Oct 14 22:07:56 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Thu Oct 14 22:07:56 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Thu Oct 14 22:07:56 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Thu Oct 14 22:07:56 2021 user.err csrMeshGw[8132]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Thu Oct 14 22:07:57 2021 daemon.err nrd[30060]: triggerMonSteering: Failed to get uplink rssi for 86:D5:BD:84:22:84

Thu Oct 14 22:08:04 2021 daemon.err client_mgmt: client(74-81-14-68-D1-89) not found in arp table disconnect_counter=0

Thu Oct 14 22:08:06 2021 daemon.notice nrd[30060]: estimatorPerformMeasurement: Do 11k measuremrent for 86:D5:BD:84:22:84 on channel 36 from serving BSS APId 255 ChanId 8 ESSId 0

Thu Oct 14 22:08:06 2021 user.err csrMeshGw[8132]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Thu Oct 14 22:08:06 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Thu Oct 14 22:08:06 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Thu Oct 14 22:08:06 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Thu Oct 14 22:08:06 2021 user.err csrMeshGw[8132]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Thu Oct 14 22:08:09 2021 daemon.err nrd[30060]: estimatorDot11kIterateCB: Timeout waiting for 802.11k response from 86:D5:BD:84:22:84

Thu Oct 14 22:08:15 2021 daemon.err nrd[30060]: triggerMonSteering: Failed to get uplink rssi for 86:D5:BD:84:22:84

Thu Oct 14 22:08:16 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block

Thu Oct 14 22:08:16 2021 user.err csrMeshGw[8132]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Thu Oct 14 22:08:16 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Thu Oct 14 22:08:16 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Thu Oct 14 22:08:16 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Thu Oct 14 22:08:16 2021 user.err csrMeshGw[8132]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Thu Oct 14 22:08:19 2021 daemon.err udhcpd[1919]: Sending ACK to 192.168.68.7

Thu Oct 14 22:08:20 2021 daemon.err udhcpd[1919]: clear ip 744a8c0

Thu Oct 14 22:08:26 2021 user.err csrMeshGw[8132]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Thu Oct 14 22:08:26 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Thu Oct 14 22:08:26 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Thu Oct 14 22:08:26 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Thu Oct 14 22:08:26 2021 user.err csrMeshGw[8132]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Thu Oct 14 22:08:31 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block

Thu Oct 14 22:08:36 2021 user.err csrMeshGw[8132]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Thu Oct 14 22:08:36 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Thu Oct 14 22:08:36 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Thu Oct 14 22:08:36 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Thu Oct 14 22:08:36 2021 user.err csrMeshGw[8132]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Thu Oct 14 22:08:46 2021 user.err csrMeshGw[8132]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Thu Oct 14 22:08:46 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Thu Oct 14 22:08:46 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Thu Oct 14 22:08:46 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Thu Oct 14 22:08:46 2021 user.err csrMeshGw[8132]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Thu Oct 14 22:08:55 2021 daemon.notice nrd[30060]: estimatorPerformMeasurement: Do 11k measuremrent for 86:D5:BD:84:22:84 on channel 36 from serving BSS APId 255 ChanId 8 ESSId 0

Thu Oct 14 22:08:56 2021 user.err csrMeshGw[8132]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Thu Oct 14 22:08:56 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Thu Oct 14 22:08:56 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Thu Oct 14 22:08:56 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Thu Oct 14 22:08:56 2021 user.err csrMeshGw[8132]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Thu Oct 14 22:08:58 2021 daemon.err nrd[30060]: estimatorDot11kIterateCB: Timeout waiting for 802.11k response from 86:D5:BD:84:22:84

Thu Oct 14 22:09:01 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block

Thu Oct 14 22:09:03 2021 daemon.err udhcpd[1919]: Found static lease: c44a8c0

Thu Oct 14 22:09:03 2021 daemon.err udhcpd[1919]: Sending ACK to 192.168.68.12

Thu Oct 14 22:09:04 2021 daemon.err udhcpd[1919]: clear ip c44a8c0

Thu Oct 14 22:09:06 2021 user.err csrMeshGw[8132]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Thu Oct 14 22:09:06 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Thu Oct 14 22:09:06 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Thu Oct 14 22:09:06 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Thu Oct 14 22:09:06 2021 user.err csrMeshGw[8132]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Thu Oct 14 22:09:16 2021 user.err csrMeshGw[8132]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Thu Oct 14 22:09:16 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Thu Oct 14 22:09:16 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Thu Oct 14 22:09:16 2021 user.err csrMeshGw[8132]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Thu Oct 14 22:09:16 2021 user.err csrMeshGw[8132]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Thu Oct 14 22:09:17 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block

Thu Oct 14 22:09:18 2021 daemon.notice nrd[30060]: estimatorPerformMeasurement: Do 11k measuremrent for 86:D5:BD:84:22:84 on channel 36 from serving BSS APId 255 ChanId 8 ESSId 0

Thu Oct 14 22:09:18 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block

Thu Oct 14 22:09:20 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block

Thu Oct 14 22:09:21 2021 daemon.err nrd[30060]: estimatorDot11kIterateCB: Timeout waiting for 802.11k response from 86:D5:BD:84:22:84

 

I would love a fix for this as it is taxing the router CPU.

 

Let me know what you think.

 

Todd

  0  
  0  
#6
Options
Re:Deco S4 filling its event log after firmware update
2021-10-15 20:20:49

@thovorka 

 

I'll reach out to the team to get a stauts update and will let you know if there is any update. 

Check out the Latest: Recent Smart Home Features and Updates for Tapo and Kasa Securing Your TP-Link ID with 2FA:Deco and Tether | Smart Home Splash into a Smarter Summer with Sub-G Sensors, Matter, and Apple Home!
  0  
  0  
#7
Options
Re:Deco S4 filling its event log after firmware update
2021-10-19 01:33:45

@Carl Thank you sir.

  0  
  0  
#8
Options
Re:Deco S4 filling its event log after firmware update
2021-12-09 21:49:13

@Carl Any luck on an update regarding tis issue?

  0  
  0  
#9
Options
Re:Deco S4 filling its event log after firmware update
2021-12-09 23:39:22

@thovorka 

 

Hello,  no response.  And shortly after i sent this I got hit with Covid and was out of action for 3 weeks.  II did not have any reminders to follow up on it so it fell through the cracks.  Sorry about that I will reach out and get you an answer. 

Check out the Latest: Recent Smart Home Features and Updates for Tapo and Kasa Securing Your TP-Link ID with 2FA:Deco and Tether | Smart Home Splash into a Smarter Summer with Sub-G Sensors, Matter, and Apple Home!
  0  
  0  
#10
Options
Re:Deco S4 filling its event log after firmware update
2021-12-13 17:31:13

@thovorka 

 

So I got a response.  Those logs are legitimate, created by Bluetooth devices generated by the chip manufacturer. Since the source code is not known, we can't modify it the way the log entries broadcast for now.  

Check out the Latest: Recent Smart Home Features and Updates for Tapo and Kasa Securing Your TP-Link ID with 2FA:Deco and Tether | Smart Home Splash into a Smarter Summer with Sub-G Sensors, Matter, and Apple Home!
  0  
  0  
#11
Options

Information

Helpful: 0

Views: 1772

Replies: 10

Related Articles
 Deco S4 performance drops from ~350Mbps to 22Mbps when experiencing an event recorded in System log.
545 0
 Deco S4 firmware update
246 0
 AX3000 Filling Up System Log
964 0
 Deco S4
406 0
deco S4 disconnects to my Roku only on certain channels
674 0
Deco S4 only operating at 100Mbps on Ethernet ports
1876 2
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.