I've had this a couple of times now.... my RT-AC86U running 386.3.2 drops the 5Ghz network and then won't allow devices to connect until it's rebooted.
My log has:
Jan 18 18:26:26 wlceventd: wlceventd_proc_event(527): eth5: Auth 90:61:AE:**********, status: Successful (0), rssi:0
Jan 18 18:26:26 wlceventd: wlceventd_proc_event(537): eth5: ReAssoc 90:61:AE:*******, status: Successful (0), rssi:0
Jan 18 18:26:26 kernel: br0: received packet on eth5 with own address as source address
Jan 18 18:26:27 dnsmasq-dhcp[2463]: DHCPREQUEST(br0) 192.168.1.xxx 90:61:ae:********
Jan 18 18:26:27 dnsmasq-dhcp[2463]: DHCPACK(br0) 192.168.1.xxx 90:61:ae:******* DEVICENAME
Jan 18 18:26:57 miniupnpd[2297]: upnp_event_process_notify: connect(192.168.1.xxx:2869): Connection timed out
Jan 18 18:27:01 miniupnpd[2297]: upnp_event_process_notify: connect(192.168.1.xxx:2869): Connection timed out
Jan 18 18:27:13 miniupnpd[2297]: upnp_event_process_notify: connect(192.168.1.xxx:2869): Connection timed out
Jan 18 18:27:14 miniupnpd[2297]: upnp_event_process_notify: connect(192.168.1.xxx:2869): Connection timed out
Jan 18 18:27:14 miniupnpd[2297]: upnpevents_processfds: 0x71c968, remove subscriber uuid:9aa1f22e-****-48e7-9dc0-b842fc34dafb after an ERROR cb: http://192.168.1.xxx:2869/upnp/eventing/ppobxhniym
Jan 18 18:27:26 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 90:61:AE:*******, status: 0, reason: Unspecified reason (1), rssi:0
Jan 18 18:27:26 wlceventd: wlceventd_proc_event(508): eth5: Disassoc 90:61:AE:******, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 18 18:27:35 miniupnpd[2297]: upnp_event_process_notify: connect(192.168.1.xxx:2869): Connection timed out
Jan 18 18:27:35 miniupnpd[2297]: upnp_event_process_notify: connect(192.168.1.xxx:2869): Connection timed out
Jan 18 18:27:35 miniupnpd[2297]: upnpevents_processfds: 0x71c8a0, remove subscriber uuid:a98df8ff-****-4928-8c7b-1b2e71464c23 after an ERROR cb: http://192.168.1.xxx:2869/upnp/eventing/stamokltma
Jan 18 18:29:04 kernel: IGMPV3 type=ef
Jan 18 18:29:04 kernel: IGMPV3 type=35
Jan 18 18:29:04 kernel: IGMPV3 type=ce
Jan 18 18:29:04 kernel: IGMPV3 type=0
Jan 18 18:29:04 kernel: IGMPV3 type=0
Jan 18 18:29:04 kernel: IGMPV3 type=0
Jan 18 18:29:04 kernel: IGMPV3 type=0
(and many more)
The machine is question went into sleep mode, so I think those events are a red-herring, but once the IGMPV3 errors start, that's it.
If I try, I just get - Windows was unable to connect to the network (or something like that). 2.4ghz is still working ok though.
I've found one thread only here - https://www.snbforums.com/threads/asuswrt-merlin-386-2-is-now-available.71625/post-686750
but it doesn't tell me much.
Anyone got any ideas?
My log has:
Jan 18 18:26:26 wlceventd: wlceventd_proc_event(527): eth5: Auth 90:61:AE:**********, status: Successful (0), rssi:0
Jan 18 18:26:26 wlceventd: wlceventd_proc_event(537): eth5: ReAssoc 90:61:AE:*******, status: Successful (0), rssi:0
Jan 18 18:26:26 kernel: br0: received packet on eth5 with own address as source address
Jan 18 18:26:27 dnsmasq-dhcp[2463]: DHCPREQUEST(br0) 192.168.1.xxx 90:61:ae:********
Jan 18 18:26:27 dnsmasq-dhcp[2463]: DHCPACK(br0) 192.168.1.xxx 90:61:ae:******* DEVICENAME
Jan 18 18:26:57 miniupnpd[2297]: upnp_event_process_notify: connect(192.168.1.xxx:2869): Connection timed out
Jan 18 18:27:01 miniupnpd[2297]: upnp_event_process_notify: connect(192.168.1.xxx:2869): Connection timed out
Jan 18 18:27:13 miniupnpd[2297]: upnp_event_process_notify: connect(192.168.1.xxx:2869): Connection timed out
Jan 18 18:27:14 miniupnpd[2297]: upnp_event_process_notify: connect(192.168.1.xxx:2869): Connection timed out
Jan 18 18:27:14 miniupnpd[2297]: upnpevents_processfds: 0x71c968, remove subscriber uuid:9aa1f22e-****-48e7-9dc0-b842fc34dafb after an ERROR cb: http://192.168.1.xxx:2869/upnp/eventing/ppobxhniym
Jan 18 18:27:26 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 90:61:AE:*******, status: 0, reason: Unspecified reason (1), rssi:0
Jan 18 18:27:26 wlceventd: wlceventd_proc_event(508): eth5: Disassoc 90:61:AE:******, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 18 18:27:35 miniupnpd[2297]: upnp_event_process_notify: connect(192.168.1.xxx:2869): Connection timed out
Jan 18 18:27:35 miniupnpd[2297]: upnp_event_process_notify: connect(192.168.1.xxx:2869): Connection timed out
Jan 18 18:27:35 miniupnpd[2297]: upnpevents_processfds: 0x71c8a0, remove subscriber uuid:a98df8ff-****-4928-8c7b-1b2e71464c23 after an ERROR cb: http://192.168.1.xxx:2869/upnp/eventing/stamokltma
Jan 18 18:29:04 kernel: IGMPV3 type=ef
Jan 18 18:29:04 kernel: IGMPV3 type=35
Jan 18 18:29:04 kernel: IGMPV3 type=ce
Jan 18 18:29:04 kernel: IGMPV3 type=0
Jan 18 18:29:04 kernel: IGMPV3 type=0
Jan 18 18:29:04 kernel: IGMPV3 type=0
Jan 18 18:29:04 kernel: IGMPV3 type=0
(and many more)
The machine is question went into sleep mode, so I think those events are a red-herring, but once the IGMPV3 errors start, that's it.
If I try, I just get - Windows was unable to connect to the network (or something like that). 2.4ghz is still working ok though.
I've found one thread only here - https://www.snbforums.com/threads/asuswrt-merlin-386-2-is-now-available.71625/post-686750
but it doesn't tell me much.
Anyone got any ideas?