Tons of error logs on my BE65
Tons of error logs on my BE65
Hi,
my new Deco BE65 triple set is now in use for some days and I noticed the system log is filling up with tons of messages.
Especially every about 30 seconds these error messages are repeating:
Fri Apr 19 12:05:08 2024 daemon.err nrd[20019]: wlanifMapToPhyMode: Invalid PHY mode from driver: 0 Fri Apr 19 12:05:08 2024 daemon.err nrd[20019]: wlanifConvertToSingleStreamMCSIndex: Invalid PHY mode from driver: 0 Fri Apr 19 12:05:08 2024 daemon.err nrd[20019]: wlanifMapToPhyMode: Invalid PHY mode from driver: 0 Fri Apr 19 12:05:08 2024 daemon.err nrd[20019]: wlanifConvertToSingleStreamMCSIndex: Invalid PHY mode from driver: 0 Fri Apr 19 12:05:39 2024 daemon.err nrd[20019]: wlanifMapToPhyMode: Invalid PHY mode from driver: 0 Fri Apr 19 12:05:39 2024 daemon.err nrd[20019]: wlanifConvertToSingleStreamMCSIndex: Invalid PHY mode from driver: 0 Fri Apr 19 12:05:39 2024 daemon.err nrd[20019]: wlanifMapToPhyMode: Invalid PHY mode from driver: 0 Fri Apr 19 12:05:39 2024 daemon.err nrd[20019]: wlanifConvertToSingleStreamMCSIndex: Invalid PHY mode from driver: 0 Fri Apr 19 12:06:10 2024 daemon.err nrd[20019]: wlanifMapToPhyMode: Invalid PHY mode from driver: 0 Fri Apr 19 12:06:10 2024 daemon.err nrd[20019]: wlanifConvertToSingleStreamMCSIndex: Invalid PHY mode from driver: 0 Fri Apr 19 12:06:10 2024 daemon.err nrd[20019]: wlanifMapToPhyMode: Invalid PHY mode from driver: 0 Fri Apr 19 12:06:10 2024 daemon.err nrd[20019]: wlanifConvertToSingleStreamMCSIndex: Invalid PHY mode from driver: 0 There are a lot more error messages like this for instance: Fri Apr 19 12:04:56 2024 daemon.err uhttpd[6922]: iptables: No chain/target/match by that name. Fri Apr 19 12:04:56 2024 daemon.err uhttpd[6922]: iptables v1.8.3 (legacy): Couldn't load target `domain_login_rule':No such file or directory Fri Apr 19 12:04:56 2024 daemon.err uhttpd[6922]: Fri Apr 19 12:04:56 2024 daemon.err uhttpd[6922]: Try `iptables -h' or 'iptables --help' for more information. Fri Apr 19 12:04:56 2024 daemon.err uhttpd[6922]: iptables: No chain/target/match by that name. Fri Apr 19 12:04:56 2024 daemon.err uhttpd[6922]: iptables: No chain/target/match by that name.
And there also messages with level critical:
Fri Apr 19 10:13:26 2024 user.emerg : tp217,505[2486]: Fri Apr 19 10:18:38 2024 user.emerg : tp217,505[7085]: Fri Apr 19 11:27:35 2024 user.emerg : tp217,505[30986]: Fri Apr 19 11:38:01 2024 user.emerg : tp215,22[8306]: Fri Apr 19 11:44:58 2024 user.emerg : tp215,22[15335]: Fri Apr 19 12:04:56 2024 user.emerg : tp215,22[31075]: Fri Apr 19 12:20:30 2024 user.emerg : tp215,22[11360]:
What is going on there? I expect to nearly see none error message on a working device.
Thomas