Network drop..

[calzor suzay]

Not sure how best to describe this but I've recently moved my Home Automation to a different system and been more 'aware' of any network activity, devices not available, dropping off etc.

Today at 4pm though my secondary node in an AiMesh seemed to drop off, I'm not sure why or how but the logs are as below, any ideas what happened and where/what I need to look at next?

This is from the RT-AC68U (node)


On the main node RT-AC86U I can't see much if anything to do with the issue in the syslog.
I know it was down as I lost devices and in the AiMesh GUI it showed as down etc

Both are running 386.2

 

[calzor suzay]

For some reason I can't add the loge as code or even attach it as a txt file...

 

[calzor suzay]

just get this...

 

[ColinTaylor]

That's because it contains banned word combinations. e.g. /etc followed by /hosts.

 

[calzor suzay]

Tweaked, bit of a daft rule?

 

[ColinTaylor]

... bit of a daft rule?

AFAIK it's to stop malware being disguised as forum posts. It blocks swearing as well.

 

[calzor suzay]

Adding as the code direct in a hope it might get looked at.

Apr 12 15:59:35 syslog: wlceventd_proc_event(491): wl0.1: Deauth_ind 00:00:00:00:00:00, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Apr 12 16:00:23 avahi-daemon[408]: Withdrawing address record for 192.168.1.45 on br0.
Apr 12 16:00:23 avahi-daemon[408]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.1.45.

Apr 12 16:00:23 lldpd[206]: removal request for address of 192.168.1.45%10, but no knowledge of it
Apr 12 16:00:23 avahi-daemon[408]: Interface br0.IPv4 no longer relevant for mDNS.
Apr 12 16:00:23 avahi-daemon[408]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.1.
Apr 12 16:00:23 avahi-daemon[408]: New relevant interface br0.IPv4 for mDNS.
Apr 12 16:00:23 avahi-daemon[408]: Registering new address record for 192.168.1.1 on br0.IPv4.
Apr 12 16:00:23 avahi-daemon[408]: Withdrawing address record for 127.0.1.1 on lo.
Apr 12 16:00:23 avahi-daemon[408]: Withdrawing address record for 127.0.0.1 on lo.
Apr 12 16:00:23 avahi-daemon[408]: Host name conflict, retrying with RT-AC68U-1DA8-147


snipped a lot of code here till it got to below...


Apr 12 16:00:36 avahi-daemon[408]: Host name conflict, retrying with RT-AC68U-1DA8-160
Apr 12 16:00:36 avahi-daemon[408]: Registering new address record for 192.168.1.1 on br0.IPv4.
Apr 12 16:00:36 avahi-daemon[408]: Registering new address record for 127.0.1.1 on lo.IPv4.
Apr 12 16:00:36 avahi-daemon[408]: Registering new address record for 127.0.0.1 on lo.IPv4.
Apr 12 16:00:36 rc_service: udhcpc_lan 20419:notify_rc stop_httpd
Apr 12 16:00:36 rc_service: udhcpc_lan 20419:notify_rc start_httpd
Apr 12 16:00:37 rc_service: waitting "stop_httpd" via udhcpc_lan ...
Apr 12 16:00:38 RT-AC68U: start httpd:80
Apr 12 16:00:38 avahi-daemon[408]: Withdrawing address record for 192.168.1.1 on br0.
Apr 12 16:00:38 avahi-daemon[408]: Server startup complete. Host name is RT-AC68U-1DA8-160.local. Local service cookie is 4051197596.
Apr 12 16:00:38 avahi-daemon[408]: Alias name "RT-AC68U" successfully established.
Apr 12 16:00:38 avahi-daemon[408]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.1.1.
Apr 12 16:00:38 avahi-daemon[408]: Interface br0.IPv4 no longer relevant for mDNS.
Apr 12 16:00:38 avahi-daemon[408]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.45.
Apr 12 16:00:38 avahi-daemon[408]: New relevant interface br0.IPv4 for mDNS.
Apr 12 16:00:38 avahi-daemon[408]: Registering new address record for 192.168.1.45 on br0.IPv4.
Apr 12 16:00:38 rc_service: udhcpc_lan 20419:notify_rc start_dnsmasq
Apr 12 16:00:38 rc_service: waitting "start_httpd" via udhcpc_lan ...
Apr 12 16:00:38 lldpd[206]: removal request for address of 192.168.1.1%10, but no knowledge of it
Apr 12 16:00:39 httpd: Save SSL certificate...80
Apr 12 16:00:39 rc_service: udhcpc_lan 20419:notify_rc stop_ntpd
Apr 12 16:00:39 rc_service: waitting "start_dnsmasq" via udhcpc_lan ...
Apr 12 16:00:39 dnsmasq[7470]: exiting on receipt of SIGTERM
Apr 12 16:00:39 httpd: mssl_cert_key_match : PASS
Apr 12 16:00:40 httpd: Succeed to init SSL certificate...80
Apr 12 16:00:40 dnsmasq[20437]: started, version 2.84-42-g433dc70 cachesize 1500
Apr 12 16:00:40 dnsmasq[20437]: asynchronous logging enabled, queue limit is 5 messages
Apr 12 16:00:40 dnsmasq[20437]: read /etc/   hosts - 6 addresses
Apr 12 16:00:40 dnsmasq[20437]: using nameserver 192.168.1.1#53
Apr 12 16:00:41 rc_service: udhcpc_lan 20419:notify_rc start_ntpd
Apr 12 16:00:41 rc_service: waitting "stop_ntpd" via udhcpc_lan ...
Apr 12 16:00:41 ntpd: Stopped ntpd
Apr 12 16:00:42 ntpd: Started ntpd
Apr 12 16:00:43 LAN: network changes (192.168.1.45/255.255.255.0 --> 192.168.1.45/255.255.255.0)
Apr 12 16:00:43 rc_service: udhcpc_lan 20419:notify_rc stop_samba
Apr 12 16:00:43 rc_service: udhcpc_lan 20419:notify_rc start_samba
Apr 12 16:00:43 rc_service: waitting "stop_samba" via udhcpc_lan ...
Apr 12 16:00:44 Samba_Server: smb daemon is stopped
Apr 12 16:00:44 kernel: gro disabled
Apr 12 16:00:44 kernel: gro disabled
Apr 12 16:00:44 dnsmasq[20437]: exiting on receipt of SIGTERM
Apr 12 16:00:46 dnsmasq[20460]: started, version 2.84-42-g433dc70 cachesize 1500
Apr 12 16:00:46 dnsmasq[20460]: asynchronous logging enabled, queue limit is 5 messages
Apr 12 16:00:46 dnsmasq[20460]: read /etc/   hosts - 6 addresses
Apr 12 16:00:46 dnsmasq[20460]: using nameserver 192.168.1.1#53
Apr 12 16:02:53 syslog: wlceventd_proc_event(527): wl0.1: Auth 84:F3:EB:4B:56:04, status: Successful (0), rssi:0
Apr 12 16:02:53 syslog: wlceventd_proc_event(556): wl0.1: Assoc 84:F3:EB:4B:56:04, status: Successful (0), rssi:0

 

[ColinTaylor]

The log doesn't show anything particularly helpful, only what you already know. The network interface (192.168.1.45) disappeared, briefly failed back to 192.168.1.1 and then reconnected.

 

[calzor suzay]

Looking at the log it did it 03:48, 05:50, 06:56 & 14:03 on the 12th, 21:00 on the 10th, logs vanish prior to the 9thh.
There doesn't appear to be anything in the logs prior to this happening.

Any ideas, anyone?

 

[calzor suzay]

I've done a factory reset of the node and re added to the AiMesh.
See if it behaves better.

 

[calzor suzay]

Having just experienced this once again I quickly diagnosed it looks to be my TP-Link powerline AV adapters I use for the backhaul.
It's been pretty much flawless for nearly 2 years.
Power cycled both ends, found a slightly newer firmware and updated.
Fingers crossed.