how do i interpret messages systemlog deco m4r (there are a lot in the log)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I notice ther are many messages in the system log that could indicate a faulty situation.
Example:
IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
message occurs 3-4 times per second.
This looks like unnecessary overhead.
How can I resolve this?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Kevin_Z wrote
Thanks for your reply.
The log mentioned indicates the IPV6's multicast management information, it is related to the clients which uses the multicast services, which cannot be removed from the log.
While please be assured of it, it won't affect the performance.
Best regards.
Wrong. The information can be removed from the log, by simply clicking "Clear all".
But that is not the point of the question asked by the other users, and myself.
I would like to see an answer how such warnings can be avoided, if the information is a warning of no concern (as you suggest).
Don't give us a complete runaround answer.
Take your customers' questions serious.
Thank you.
- Copy Link
- Report Inappropriate Content
@arnie2019 Same problem here, waiting for an answer from TP-Link ...
- Copy Link
- Report Inappropriate Content
I'm having the same problem... but this is not the only one, I opened a ticket a week ago, but no response from tp-link, i'm seriously considering buying tp-link products again, this support is bull****
- Copy Link
- Report Inappropriate Content
The same problem. IGMP and IPv6 off..... But log have a lot of same errors:
Sun Apr 18 18:11:56 2021 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ffd0:5b7 is link-local multicast address
Sun Apr 18 18:11:56 2021 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ffd0:5b7 is link-local multicast address
Sun Apr 18 18:11:56 2021 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ffd0:5b7 is link-local multicast address
Sun Apr 18 18:11:56 2021 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ffd0:5b7 is link-local multicast address
Sun Apr 18 18:11:56 2021 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ffd0:5b7 is link-local multicast address
Sun Apr 18 18:11:56 2021 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ffd0:5b7 is link-local multicast address
Sun Apr 18 18:11:56 2021 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ffd0:5b7 is link-local multicast address
Sun Apr 18 18:11:56 2021 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ffd0:5b7 is link-local multicast address
Sun Apr 18 18:11:56 2021 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ffd0:5b7 is link-local multicast address
Sun Apr 18 18:11:56 2021 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ffd0:5b7 is link-local multicast address
Sun Apr 18 18:11:56 2021 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ffd0:5b7 is link-local multicast address
- Copy Link
- Report Inappropriate Content
@arnie2019 Same problems on my Deco M4R. CPU low as 4% for about 5s then skipping to 97% for another 5s and so on resulting (?) in bad performance (www loading).
I am not happy with performance problems of this mesh system (not wifi signal strength but websites, videos, images sometimes - not always!) and I don't know what to look for and what to do as everything seems to be setup the standard way and I get no error messages nor advices from system.
- Copy Link
- Report Inappropriate Content
Hi, After checking with the senior engineers, whether the IGMP snooping is on or off on the web UI is not related to these logs.
It mainly used to confirm whether the packets were sent from the IGMP group address;
Thank you.
- Copy Link
- Report Inappropriate Content
Hi,
The massive flow usage and High-frequency operation would lead to CPU usage spikes.
It would drop to a stable level after a while and it would not cause slow speed or internet instability.
About the bad performance on the Deco M4, you might need to provide us more details about it;
And after checking your TP-Link ID, I noticed that you also have a router Archer C6;
If possible, you could configure the Archer C6 as the main router and let the Deco M4 work as the access point;
Thank you.
- Copy Link
- Report Inappropriate Content
@TP-Link Hi and thanks for your reply. The Archer is in another location, so in no relation to the Deco network.
I notice bigger performance drops after couple weeks online, system reboot mostly solves it. From my point of view a scheduled reboot in router config could help to solve some of these problems - I would set it to reboot weekly.
- Copy Link
- Report Inappropriate Content
Thank you and the reboot schedule has been taken into consideration and it would be added into the later firmware upgrade;
- Copy Link
- Report Inappropriate Content
@ir11 To be fair I have to mention, that after some changes the performance of my Deco mesh system is OK now;
- I upgraded my PiHole hardware
- my internet provider got better recently
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 11449
Replies: 21
Voters 3
