Hi everyone,
I've read here in the forum quite a bit on the subject of people having the above error, and most have fixed it (those who succeeded) either by disabling various Guest Network or LAN access in Guest Networks, or disabling some QoS, disabling some IPv6, etc.
I myself have never seen this error before in my Asus RT-AC5300 (who has happily run Suricata for years too), and started to see it this week-end when I swapped it with an RT-AC86U, apparently configured exactly the same (GUI screen by GUI screen, same entware config files for the same installed packages with just the bare minimum differences due to the switch to the HND platform).
In my case, the single responsible seems to be suricata, meaning that the error starts appearing once Suricata completes its startup, and disappears when I stop Suricata. Anything else (like the above) in my case seems to be ineffective.
So my question is: does anyone running Suricata have succeeded in getting rid of this error message spamming in thousands per day the system log ? Or can anyone suggest any clue that I can try to succeed ?
I hope the only suggestion is not to factory reset the router as this would take a so-long time to reconfigure in my case that I would probably defer it to ... don't know when.
P.S. I've updated from 386.2_4 to 386.2_6 today in the hope ... but honestly the issue didn't seem to be related to anything mentioned in recent firmware release notes, and indeed this one didn't fix it neither.
I've read here in the forum quite a bit on the subject of people having the above error, and most have fixed it (those who succeeded) either by disabling various Guest Network or LAN access in Guest Networks, or disabling some QoS, disabling some IPv6, etc.
I myself have never seen this error before in my Asus RT-AC5300 (who has happily run Suricata for years too), and started to see it this week-end when I swapped it with an RT-AC86U, apparently configured exactly the same (GUI screen by GUI screen, same entware config files for the same installed packages with just the bare minimum differences due to the switch to the HND platform).
In my case, the single responsible seems to be suricata, meaning that the error starts appearing once Suricata completes its startup, and disappears when I stop Suricata. Anything else (like the above) in my case seems to be ineffective.
So my question is: does anyone running Suricata have succeeded in getting rid of this error message spamming in thousands per day the system log ? Or can anyone suggest any clue that I can try to succeed ?
I hope the only suggestion is not to factory reset the router as this would take a so-long time to reconfigure in my case that I would probably defer it to ... don't know when.
P.S. I've updated from 386.2_4 to 386.2_6 today in the hope ... but honestly the issue didn't seem to be related to anything mentioned in recent firmware release notes, and indeed this one didn't fix it neither.