What's new

Wireless Devices losing Internet connection

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

BGood

Regular Contributor
I'm running an RT-AC5300 (with Merlin 384.14_2). On Monday morning, I booted my work laptop which complained that despite connecting to my router (guest WiFi) lacked Internet access. My work cell phone (guest WiFi) and personal cell phone (principal WiFi) were both fine, as was my wired desktop. I rebooted the work laptop without success. I rebooted my router. Turned off the wireless on the router and turned it back on. I was getting late for a meeting, so I didn't have much time to troubleshoot, but it suddenly started working.

Today, after working on my work laptop wirelessly all day without incident, I powered it off and switched to my wired desktop. A bit later, my cell phone complained it wasn't able to reach the Internet, but my wired desktop was still fine.

Here's part of the log. I've redacted part of my cell phone's MAC address (maybe I'm paranoid):
Jun 3 18:49:52 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind 30:07:xx:yy:D1:zz, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jun 3 18:50:27 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 30:07:xx:yy:D1:zz, status: 0, reason: d11 RC reserved (0)
Jun 3 18:50:27 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 30:07:xx:yy:D1:zz, status: 0, reason: d11 RC reserved (0)
Jun 3 18:50:47 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind 30:07:xx:yy:D1:zz, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jun 3 18:50:47 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind 30:07:xx:yy:D1:zz, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jun 3 18:50:47 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind 30:07:xx:yy:D1:zz, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jun 3 18:50:47 syslog: WLCEVENTD wlceventd_proc_event(386): eth1: Deauth_ind 30:07:xx:yy:D1:zz, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Jun 3 18:50:51 syslog: WLCEVENTD wlceventd_proc_event(420): eth3: Auth 30:07:xx:yy:D1:zz, status: 0, reason: d11 RC reserved (0)
Jun 3 18:50:51 syslog: WLCEVENTD wlceventd_proc_event(449): eth3: Assoc 30:07:xx:yy:D1:zz, status: 0, reason: d11 RC reserved (0)
Jun 3 18:50:51 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc 30:07:xx:yy:D1:zz, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 3 18:50:54 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 30:07:xx:yy:D1:zz, status: 0, reason: d11 RC reserved (0)
Jun 3 18:50:54 syslog: WLCEVENTD wlceventd_proc_event(430): eth1: ReAssoc 30:07:xx:yy:D1:zz, status: 0, reason: d11 RC reserved (0)
Jun 3 18:50:54 syslog: WLCEVENTD wlceventd_proc_event(401): eth3: Disassoc 30:07:xx:yy:D1:zz, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 3 18:50:54 syslog: WLCEVENTD wlceventd_proc_event(401): eth3: Disassoc 30:07:xx:yy:D1:zz, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 3 18:52:44 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc 30:07:xx:yy:D1:zz, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 3 18:52:45 syslog: WLCEVENTD wlceventd_proc_event(420): wl0.1: Auth 30:07:xx:yy:D1:zz, status: 0, reason: d11 RC reserved (0)
Jun 3 18:52:45 syslog: WLCEVENTD wlceventd_proc_event(449): wl0.1: Assoc 30:07:xx:yy:D1:zz, status: 0, reason: d11 RC reserved (0)
Jun 3 18:52:59 syslog: WLCEVENTD wlceventd_proc_event(401): wl0.1: Disassoc 30:07:xx:yy:D1:zz, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 3 18:52:59 syslog: WLCEVENTD wlceventd_proc_event(386): wl0.1: Deauth_ind 30:07:xx:yy:D1:zz, status: 0, reason: Class 3 frame received from nonassociated station (7)

I've had this router for about two years and had zero issues with it. Nothing has changed with the router (no new firmware in a few months). The last new device was added nearly a month ago. Nothing since then has changed on the network.

I did try switching my cell phone to the 2.4 GHz guest network, rather than the Tri-band Smart Connect primary WiFi network.

Note, all the devices in question are no more than 5 feet, unobstructed, from my router.

I'm not sure what I should do next. Looking for some good advice, please.
 
From the third last paragraph in your writing above I conclude that you have smart connect running. Turn it off, select a fixed channel for each wifi, switch of the beam forming for 2.4GHz, keep only AC beam forming on for your 5GHz, turn of mu-mimo, disable wmm apsd for your 5GHz, disable roaming assistent for all wifi's, disable IGMP snooping for all wifi's. Your wifi may have worked good so far but when in your environment other users change their routers it may affect the spectrum where your router operates.
 
I'm in a single family home and I'm not sure I'm close enough for my neighbors to be stepping on my signal. I might do a factory reset, re-flash my current Merlin version and restore my configuration to see if that helps.

Thanks for the suggestion, though!
 
If you're going to restore the current configuration don't do the factory reset then. :)
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top