What's new

Network throughput dropping

  • 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!

Livy

Occasional Visitor
Hi.
Not sure if this is the right place
Got an RT-ac86u
Every so often it's like the network connection just drops. Device still shows connected to WiFi. But won't connect to anything.
Can't even connect to the router itself. Which makes me think this is an internal problem.
Running 386.4 and have an ac88u wired backhaul in mesh mode. Running latest stock firmware.
Only add-ons on device is diversion.
Yet this was happening before upgrading to merlin.
I followed the reset guide when upgrading.

Some logs below at the time it happened. Not sure if anything here is untoward.

Thanks.

Jan 28 21:24:10 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 28:16:7F:6D:9D:24, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Jan 28 21:24:10 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 28:16:7F:6D:9D:24, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 28 21:24:13 wlceventd: wlceventd_proc_event(527): eth6: Auth 28:16:7F:6D:9D:24, status: Successful (0), rssi:0
Jan 28 21:24:15 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 28:16:7F:6D:9D:24, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 28 21:24:16 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc0156161e8 next ffffffc0192caca0 prev ffffffc0192caca0 rep_entry->list ffffffc0192caca0 next ffffffc0156161e8 prev ffffffc0156161e8
Jan 28 21:25:47 wlceventd: wlceventd_proc_event(527): eth5: Auth A4:77:33:3F:3E:72, status: Successful (0), rssi:0
Jan 28 21:25:47 wlceventd: wlceventd_proc_event(556): eth5: Assoc A4:77:33:3F:3E:72, status: Successful (0), rssi:0
Jan 28 21:25:47 wlceventd: wlceventd_proc_event(508): eth6: Disassoc A4:77:33:3F:3E:72, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 28 21:25:47 wlceventd: wlceventd_proc_event(508): eth6: Disassoc A4:77:33:3F:3E:72, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 28 21:25:48 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc0155dd728 next ffffffc00554ca60 prev ffffffc00554ca60 rep_entry->list ffffffc00554ca60 next ffffffc0155dd728 prev ffffffc0155dd728
Jan 28 21:25:49 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind A4:77:33:3F:3E:72, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Jan 28 21:25:57 wlceventd: wlceventd_proc_event(527): eth6: Auth A4:77:33:3F:3E:72, status: Successful (0), rssi:0
Jan 28 21:25:57 wlceventd: wlceventd_proc_event(527): eth6: Auth A4:77:33:3F:3E:72, status: Successful (0), rssi:0
Jan 28 21:25:57 wlceventd: wlceventd_proc_event(556): eth6: Assoc A4:77:33:3F:3E:72, status: Successful (0), rssi:0
Jan 28 21:25:57 wlceventd: wlceventd_proc_event(508): eth5: Disassoc A4:77:33:3F:3E:72, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 28 21:25:58 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 7C:D6:61:C5:E7:C1, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Jan 28 21:25:58 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 7C:D6:61:C5:E7:C1, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 28 21:26:02 wlceventd: wlceventd_proc_event(508): eth6: Disassoc A4:77:33:3F:3E:72, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 28 21:26:02 wlceventd: wlceventd_proc_event(527): eth6: Auth A4:77:33:3F:3E:72, status: Successful (0), rssi:0
Jan 28 21:26:02 wlceventd: wlceventd_proc_event(527): eth6: Auth A4:77:33:3F:3E:72, status: Successful (0), rssi:0
Jan 28 21:26:02 wlceventd: wlceventd_proc_event(527): eth6: Auth A4:77:33:3F:3E:72, status: Successful (0), rssi:0
Jan 28 21:26:02 wlceventd: wlceventd_proc_event(556): eth6: Assoc A4:77:33:3F:3E:72, status: Successful (0), rssi:0
Jan 28 21:26:12 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind A4:77:33:3F:3E:72, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Jan 28 21:26:27 wlceventd: wlceventd_proc_event(527): eth5: Auth A4:77:33:3F:3E:72, status: Successful (0), rssi:0
Jan 28 21:26:27 wlceventd: wlceventd_proc_event(556): eth5: Assoc A4:77:33:3F:3E:72, status: Successful (0), rssi:0
Jan 28 21:26:27 wlceventd: wlceventd_proc_event(508): eth6: Disassoc A4:77:33:3F:3E:72, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 28 21:26:30 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind A4:77:33:3F:3E:72, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Jan 28 21:26:36 wlceventd: wlceventd_proc_event(527): eth5: Auth A4:77:33:3F:3E:72, status: Successful (0), rssi:0
Jan 28 21:26:36 wlceventd: wlceventd_proc_event(556): eth5: Assoc A4:77:33:3F:3E:72, status: Successful (0), rssi:0
Jan 28 21:26:57 roamast: sta 18:4E:CB:78:38:B5 ap 04:D9:F5:53:1C:CC rcpi 75
Jan 28 21:26:57 roamast: after rssi -73
Jan 28 21:26:57 roamast: sta 18:4E:CB:78:38:B5 ap D4:5D:64:D8:E7:E4 rcpi 86
Jan 28 21:26:57 roamast: after rssi -67
Jan 28 21:27:03 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 0C:43:F9:0A:BA:75, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Jan 28 21:27:03 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 0C:43:F9:0A:BA:75, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 28 21:27:06 wlceventd: wlceventd_proc_event(527): eth5: Auth 0C:43:F9:0A:BA:75, status: Successful (0), rssi:0
Jan 28 21:27:06 wlceventd: wlceventd_proc_event(556): eth5: Assoc 0C:43:F9:0A:BA:75, status: Successful (0), rssi:0
 
Could just be the drivers on your devices or the sensitivity of the cards pulling a stronger signal from the other router.

Windows is a bit stupid when it comes to getting things right. Intel on the other hand lately has been just as dumb with drivers.

0C:43:F9:0A:BA:75 - Amazon
18:4E:CB:78:38:B5 - Samsung
A4:77:33:3F:3E:72 - Google

Jan 28 21:26:57 roamast: sta 18:4E:CB:78:38:B5 ap 04:D9:F5:53:1C:CC rcpi 75
Jan 28 21:26:57 roamast: after rssi -73
Jan 28 21:26:57 roamast: sta 18:4E:CB:78:38:B5 ap D4:5D:64:D8:E7:E4 rcpi 86
Jan 28 21:26:57 roamast: after rssi -67

The "Samsung" looks like it's waffling between which AP to stay connected to.

The "Google" device looks like it's having some issues though.
 
Thanks for the insight.
I dropped the 5ghz power down a little incase they were interfering.
Yet issue still happened again.
All devices are mobile devices so no laptop.
When it happens it seems to affect all devices.

Or at least those on 5ghz.
The only devices on 2.4ghz normally are smart devices. Lightbulbs etc.

The devices listed.
The Google is a Google home and sits on top of the cabinet the router is on.
And the Amazon is a firestick in the TV next to the unit.
So shouldn't even be trying to roam in would have thought.

When it drops it sometimes reconnects to the node and i think it seems to be working ok.
Tuning WiFi on and off again on the device also doesn't seem to resolve it as when it reconnects there is still no network throughput.
 
Hmm.. ok.

The only other thing that comes to mind since this is primarily 5Ghz is DFS for weather radar causing a temporary drop while it looks for clear channels.

I have mine setup as a hidden network and sometimes it takes a bit to connect while waiting to pick up a beacon from the system. Sometimes though the Chromecast flips out and acts like an idiot and won't connect w/o readding the SSID / key to connect.

Sometimes a factory reset will kill a gremlin hiding though. Using a WIFI analyzer and picking the channels might help as well. Set say R! on 40 and R2 for 100+ so the devices don't get confused.
 
Sorry forgot to add. 5ghz is fixed on channel 36. So no DFS.
And 2.4ghz is channel 11.
I don't think I've ever been able to see any other 5ghz channel from within the house.
We are a detached house,
With roughly 5m either side to the next house.
1 is an older lady who has an old bt router which only seems to out 2.4ghz. on channel 1
And other side is using channel 6 and can't see their 5ghz from

I'm only assuming it is only affecting 5ghz,
As all "in use devices" are usually connected to 5ghz.
 
Chanel 36 is not DFS unless it is 180MHz wide

Try the following changes:
- Disable Smart Connect. Smart connect works by dropping clients and hoping they will reconnect
- Disable Rooming Assistant. It also works by dropping clients
- Universal Beamforming - Non standard based game that can cause issues
- Explicit Beamforming - It is not clear what standard is used. Might cause issues.

Good luck,

Morris
 
Thanks.
I currently have it set at 20/40/80

Both beamforming had already been disabled after setting up.

I've tried disabling smart connect and roaming assistant and see how things go from here


Thanks
 
Ok, running with smart connect and roamming assist disabled.
And think had another drop again this evening.
My phone was on 2.4 connected to the main router and didn't seem affected.
Had just put something on the firestick and it stopped, and my partner's phone who was on 5ghz also couldn't get internet.

Not sure if there is maybe an issue with the 5ghz on the ac86u.

When I've got more time I'll try doing another full reset, and fresh start.
 
Ok, running with smart connect and roamming assist disabled.
And think had another drop again this evening.
My phone was on 2.4 connected to the main router and didn't seem affected.
Had just put something on the firestick and it stopped, and my partner's phone who was on 5ghz also couldn't get internet.

Not sure if there is maybe an issue with the 5ghz on the ac86u.

When I've got more time I'll try doing another full reset, and fresh start.

"Could not get Internet" Were the devices still connected to the router?

Have you used a WiFi Scanning tool to see what other networks are using CH 36 and how strong the signal is? You may be dealing with co channel interference from someone near you.

When Internet was not working on the 5-Ghz devices, was it working on wired or 2.4-Ghz devices?
 
Yeah. Using WiFi scanner on my phone.
No other 5ghz networks visible at all.
(Pretty low density area)
Detached property with about 4m either side.
And relatively wide street so neighbors across the road are reasonable distance away

My phone was on 2.4ghz and I never noticed any interruption.

My partner was sitting closer and asked if the WiFi was down as she couldn't get access to anything. And the video playing on the firestick stopped at the same time.
Device was still showing WiFi was connected.

Wired not 100% sure.
As nothing was in use at the time.

Activity arrows on here device were only shown sending, but not receive any data.

Could it be the mesh node is in too close proximity
Would swapping to access point and changing channels help?

Thanks
David
 
Yeah. Using WiFi scanner on my phone.
No other 5ghz networks visible at all.
(Pretty low density area)
Detached property with about 4m either side.
And relatively wide street so neighbors across the road are reasonable distance away

My phone was on 2.4ghz and I never noticed any interruption.

My partner was sitting closer and asked if the WiFi was down as she couldn't get access to anything. And the video playing on the firestick stopped at the same time.
Device was still showing WiFi was connected.

Wired not 100% sure.
As nothing was in use at the time.

Activity arrows on here device were only shown sending, but not receive any data.

Could it be the mesh node is in too close proximity
Would swapping to access point and changing channels help?

Thanks
David

Don't change the second router to AP mode yet unless you are willing to give up guest networks on it. The advantage to using AP mode on the second router is that you can use different channels for each radio avoiding co channel interference and improve performance. If you are OK with the change, its a better network setup.

Why did you chose CH 36 with clear air? The higher channels sometimes pernitrate walls a bit better.

Do your logs indicate which router the devices were connected to? This can help indicate which router you need to look at.
 
Dropping 5Ghz, the first thing that comes to mind is DFS for weather radar.

Though I had a period of time when this seemed to happen more often than it should be and it seems more like a FW bug causing the drop as it went away post update.
 
Dropping 5Ghz, the first thing that comes to mind is DFS for weather radar.

Though I had a period of time when this seemed to happen more often than it should be and it seems more like a FW bug causing the drop as it went away post update.

I suspected this was happening in a much older version and changing channels to the higher ones helped. That was fixed long ago. In my case, it was aircraft radar. With today's firmware, when DFS activates, it's entered in the log or at least it is when things are working properly.

Morris
 
I think it was that to begin with and just set it to that. And keeping away from dfs. I can change it to another channel to see if that helps.
Assume it better to keep away from dfs?

I currently don't use the guest network. So no big deal at the moment.

The firestick is currently bound to the main router ac86u as its in the livingroom. And my partner was sitting in there too so should have been connected to that too.

The node is upstairs, so not used as often,
Usually devices if in bed, but I don't recall it ever happening
Thanks
David
 
I think it was that to begin with and just set it to that. And keeping away from dfs. I can change it to another channel to see if that helps.
Assume it better to keep away from dfs?

I currently don't use the guest network. So no big deal at the moment.

The firestick is currently bound to the main router ac86u as its in the livingroom. And my partner was sitting in there too so should have been connected to that too.

The node is upstairs, so not used as often,
Usually devices if in bed, but I don't recall it ever happening
Thanks
David

If you don't need to use DFS it is best to stay off both for stability and permitted transmit power.

Since you don't mind going to AP mode, do so and set it's 5-Ghz to CH 149. What type of router is the second node? This will eliminate AI Mesh and any bugs it may have with your gear.

Your partners device should have migrated to the closer node yet a lot of devices don't do it when you would expect.

How old are both routers? Asus routers are super configurable and that's why I like them yet they are not the longest lasting. You may be facing a hardware issue. If this change dose not help, try swapping the two routers positions and roles in your network. I suspect you have a hardware issue. We will find out.
 
Certainly nothing in the logs mentioning DFS.
As I've been going in and checking them every so often.

I can't remember the exact time it happened earlier to post the log.
But will take a note if it happens again.

The node is an ac88u and was purchased Dec 19 and was the main router.
Then replaced with the 86cu in August 20
And moved as a node.
 
Certainly nothing in the logs mentioning DFS.
As I've been going in and checking them every so often.

I can't remember the exact time it happened earlier to post the log.
But will take a note if it happens again.

The node is an ac88u and was purchased Dec 19 and was the main router.
Then replaced with the 86cu in August 20
And moved as a node.

The 86u is still under the 2 year warrantee

The main difference between the two is the number of ports. Why did you stop using the 88 as your router?
 
I had an old access point that was getting used upstairs, as the signal was a bit low.
And the ac86u came on offer so took the opportunity to use ai mesh as thought it would be better.

The ac86u is also a little faster isn't it?
 
I had an old access point that was getting used upstairs, as the signal was a bit low.
And the ac86u came on offer so took the opportunity to use ai mesh as thought it would be better.

The ac86u is also a little faster isn't it?

I think they have the same CPU and radios. The only difference is the switch.

Mesh is easy for those that don't have the knowhow. If they put each node on different channels mesh would be super.
 

Similar threads

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