Strange entries in syslog

[bertradio]

I am running 386.2.2 on an AC68U and getting a lot of messages in my syslog like this:

Apr 19 07:47:30 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 07:49:01 kernel: D0:C53:28:ED:39 not mesh client, can't update it's ip
Apr 19 07:49:01 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 07:50:30 kernel: D0:C53:28:ED:39 not mesh client, can't update it's ip
Apr 19 07:50:30 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 07:56:30 kernel: D0:C53:28:ED:39 not mesh client, can't update it's ip
Apr 19 07:56:30 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:02:31 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:08:30 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:10:55 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:14:30 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:19:09 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:20:47 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:22:18 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:26:03 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:28:43 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:29:16 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip

There seems to be no pattern and sometimes they come almost every minute.

Is this something to worry about? I just have the single router, no mesh.

Thanks

 

[GSpock]

Mesh messages in syslog while Mesh not being used/defined

Hi, I am getting those messages in syslog while I am not using Mesh. The MAC address reported is the one of my Synology NAS. Any idea why this is showing-up ?

www.snbforums.com

 

[MvW]

I am running 386.2.2 on an AC68U and getting a lot of messages in my syslog like this:

Apr 19 07:47:30 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 07:49:01 kernel: D0:C53:28:ED:39 not mesh client, can't update it's ip
Apr 19 07:49:01 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 07:50:30 kernel: D0:C53:28:ED:39 not mesh client, can't update it's ip
Apr 19 07:50:30 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 07:56:30 kernel: D0:C53:28:ED:39 not mesh client, can't update it's ip
Apr 19 07:56:30 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:02:31 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:08:30 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:10:55 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:14:30 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:19:09 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:20:47 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:22:18 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:26:03 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:28:43 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip
Apr 19 08:29:16 kernel: 44:39:C4:B7:26:AD not mesh client, can't update it's ip

There seems to be no pattern and sometimes they come almost every minute.

Is this something to worry about? I just have the single router, no mesh.

Thanks

These are apparently debug messages that someone at the ASUS developers team has forgotten to turn off or hide before the (last few) GPLs got released. As AIMesh is a closed source component RMerlin has no influence on this. It's waiting for a future release where the ASUS developers decide to turn them off. Until then you can safely ignore them.

The fact that you have no Mesh network, doesn't matter. AIMesh 2.0 is still in the firmware for your router and apparently looking for nodes to update their IP. Nothing you can do about it for now, except if your running (ui)Scribe and syslog-ng, then you could write a filter, to filter these repeating lines out of your log.

Best regards,
Marco

 

[bertradio]

Thanks Marco. I'll just ignore them and wait on Asus.