NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Spydrjon
Feb 08, 2020Follower
Nighthawk mesh slow speed
I have installed a new nighthawk WiFi 6 mesh router with 1 satellite. I am getting great speed on speed test from the fiber, but the WiFi speeds SUCK. when I look at the network map, everything seems ...
Christian_R
Jun 08, 2021NETGEAR Employee Retired
Hi markber,
I have notified our support team and have requested that they follow up with you as soon as possible.
Regards,
Christian
markber
Jun 17, 2021Tutor
Christian_R wrote:Hi markber,
I have notified our support team and have requested that they follow up with you as soon as possible.
Regards,Christian
Christian_R , thanks, a couple more frustrating weeks have passed, case has now been "escalated" to the 3rd person, and I have yet to receive any feedback about my issue.
In the meantime, in the past 24 hours, it looks like firmware 1.0.6.110 has finally been re-released. This has resolved some issues and not others.
Resolved
1. My devices (laptop and Galaxy S20) will now connect to the MS60 at speeds greater than 173.3 Mbps.
2. The 2.4 Ghz channel and 5 Ghz channel are now in sync on both the MR60 and MS60, even after a reboot.
Issues
1. After my Galaxy S20 connects to the MS60 at 1.1 Gbps, this speed is not maintained, and after a couple of mins it drops down to ~600 Mbps, and will not connect any higher.
2. The http://<MS60IP>/WLG_wireless_dual_band_r10.htm on the MS60 is still out of sync with the start.htm page ... the 5 Ghz "Mode" is showing as "Up to 600 Mbps" on the WLG_wireless_dual_band_r10.htm whereas it's showing as "Up to 1200 Mbps" on the start.htm page.
3. The internet speed on the MR60 is showing at over 250 Mbps, yet devices on my network will not get more than 80 Mbps.
Can't help be frustrated by the experience ... support typically takes ~3 days to respond, doesn't seem to be aware of documented bugs, let alone bugs which are being addressed in upcoming firmware release.
- guitarman3001Jun 22, 2021Star
My firmware is still at 1.0.6.102, when I go to update it it says no updates are available and my DL speeds are still capping out at around 80mbps, this is running directly from the MR60's interface, not independently from my laptop or PC.
Very frustrating.
- markberJul 05, 2021Tutor
markber wrote:
Christian_R wrote:Hi markber,
I have notified our support team and have requested that they follow up with you as soon as possible.
Regards,Christian
Christian_R , thanks, a couple more frustrating weeks have passed, case has now been "escalated" to the 3rd person, and I have yet to receive any feedback about my issue.
In the meantime, in the past 24 hours, it looks like firmware 1.0.6.110 has finally been re-released. This has resolved some issues and not others.
Resolved
1. My devices (laptop and Galaxy S20) will now connect to the MS60 at speeds greater than 173.3 Mbps.
2. The 2.4 Ghz channel and 5 Ghz channel are now in sync on both the MR60 and MS60, even after a reboot.Issues
1. After my Galaxy S20 connects to the MS60 at 1.1 Gbps, this speed is not maintained, and after a couple of mins it drops down to ~600 Mbps, and will not connect any higher.
2. The http://<MS60IP>/WLG_wireless_dual_band_r10.htm on the MS60 is still out of sync with the start.htm page ... the 5 Ghz "Mode" is showing as "Up to 600 Mbps" on the WLG_wireless_dual_band_r10.htm whereas it's showing as "Up to 1200 Mbps" on the start.htm page.
3. The internet speed on the MR60 is showing at over 250 Mbps, yet devices on my network will not get more than 80 Mbps.Can't help be frustrated by the experience ... support typically takes ~3 days to respond, doesn't seem to be aware of documented bugs, let alone bugs which are being addressed in upcoming firmware release.
Christian_R, still no feedback from support re the escalation of this issue, after providing debug logs etc to level 2 support.
I can confirm that the latest firmware version "1.0.6.112 - Hot Fix" does not resolve the above MS60 issues.
It also appears that an old bug has now returned on the MS60s: device list is not populated in the Nighthawk app, per case #44420755 :(
- markberJul 24, 2021Tutor
Christian_R, more weeks have passed .. case is now onto the 4th "escalation" person, and I've yet to receive any update.
4th person told me the case didn't even appear to be escalated to engineering by the 3rd person, even though I was assured they had all the info to escalate :(
This clearly isn't an isolated issue - just look at how many people on this thread are having issues, in addition to https://community.netgear.com/t5/Nighthawk-Mesh-System/ATTN-Netgear-Support-MR60-MS60-slow-connection-speeds/td-p/2108563 and https://community.netgear.com/t5/Nighthawk-WiFi-Routers/Netgear-router-throttling-speeds/td-p/1963498 to provide additional examples.
And as others have mentioned, 90 day support isn't very helpful, considering how many months things drag on with support .. and the general lack of urgency:(
- markberAug 21, 2021Tutor
@Christian_R, more weeks have passed, we're now many months into this. I've lost track of how many support folks have been involved in the case.
Feedback from a few weeks back was that the debug logs I provided didn't capture what the dev team is looking for. So they created a custom debug firmware. After a couple of weeks since I provided the most recent logs, using the custom debug firmware, it has now been revealed that it too didn't capture what they're looking for. So I'm now waiting for another debug firmware to capture the next round of logs.
Can't help be baffled why the dev team aren't able to reproduce this issue themselves, let alone why this is taking so long.
I can confirm that the latest firmware version 1.0.6.116 does not resolve the above MS60 issues .. WiFi connections are still being throttled at around 70 Mbps.
I can also confirm that the old bug, where the MS60 device list is not populated in the Nighthawk app, is also not resolved.
- AsitAgarwalSep 15, 2021Aspirant
markber I have the exact same issue with exact same model.. Netgear support is pathetic and there is no resolution even after 2 hours into a call
- markberSep 15, 2021Tutor
Don't even get me started re support experience :(
Assuming you're on wired backhaul, try remove the network cable to force WiFi backhaul, as there appears to be an issue with wired backhaul between the MR60 and MS60.
I was unable to get WiFi backhaul to work just by unplugging the network cable from the MS60 and rebooting (pulling the power cable), and ended up performing multiple factory resets, and 30:30:30 resets (using a paperclip, press the reset button and hold it for 30 secs, while still pressing the reset button with the paperclip, remove the power for 30 secs, while still holding the reset button with the paperclip plug the power back in and wait for 30 secs, then release paperclip) on the MR60 and MS60 to get them to connect via WiFi backhaul. Another bug.
This has resolved the MS60 device list not populating issue in the Nighthawk App.
All signs point to wired backhaul :(
Good luck getting Netgear to recognize this, let alone reproduce it on their own, let alone fix it. I've sent countless debug logs, each time I'm told the logs don't capture the info they're looking for. Another bug.
- FURRYe38Sep 15, 2021Guru
Are your MS directly connected to the MR or is there a LAN switch in between? If so, what is the Brand and model# of this switch?
What CAT version LAN cables are you using? CAT6 is recommended.
markber wrote:
Don't even get me started re support experience :(
Assuming you're on wired backhaul, try remove the network cable to force WiFi backhaul, as there appears to be an issue with wired backhaul between the MR60 and MS60.
I was unable to get WiFi backhaul to work just by unplugging the network cable from the MS60 and rebooting (pulling the power cable), and ended up performing multiple factory resets, and 30:30:30 resets (using a paperclip, press the reset button and hold it for 30 secs, while still pressing the reset button with the paperclip, remove the power for 30 secs, while still holding the reset button with the paperclip plug the power back in and wait for 30 secs, then release paperclip) on the MR60 and MS60 to get them to connect via WiFi backhaul. Another bug.
This has resolved the MS60 device list not populating issue in the Nighthawk App.
All signs point to wired backhaul :(
Good luck getting Netgear to recognize this, let alone reproduce it on their own, let alone fix it. I've sent countless debug logs, each time I'm told the logs don't capture the info they're looking for. Another bug.
- markberSep 15, 2021Tutor
FURRYe38 wrote:Are your MS directly connected to the MR or is there a LAN switch in between? If so, what is the Brand and model# of this switch?
What CAT version LAN cables are you using? CAT6 is recommended.
A better question would have been .. did your current setup ever work with wired backhaul?
My answer would have been: It sure did!
Something changed in a firmware update some versions back, that broke this. I have rolled back to versions up to and including V1.0.6.110, but that did not solve the problem .. so I'm guessing it was a firmware version prior to that.
To answer your question:
MS60 has been connected to the MR60 via Netgear gigabit switch (GS305) using Cat 5e UTP cables. I have also tried connecting the MS60 directly to the MR60 via both Cat 5e and Cat 6 UTP .. makes no difference.
- FURRYe38Sep 16, 2021Guru
So ff the configuration worked before, what changed? FW update?
What version of FW had it been working on?
- markberSep 16, 2021Tutor
FURRYe38 wrote:So ff the configuration worked before, what changed? FW update?
What version of FW had it been working on?
Was none of this clear with my previous response?
All worked fine before a firmware update. Nothing changed on my side other than firmware updates.
As previously mentioned, I rolled back to versions up to and including V1.0.6.110, but didn't go back further .. so I'm guessing it was prior to that.
- FURRYe38Sep 16, 2021Guru
Try going back prior to that?
markber wrote:
Was none of this clear with my previous response?
All worked fine before a firmware update. Nothing changed on my side other than firmware updates.
As previously mentioned, I rolled back to versions up to and including V1.0.6.110, but didn't go back further .. so I'm guessing it was prior to that.
- markberOct 15, 2021Tutor
More weeks have passed, more support folks involved, more custom debug firmwares, and debug logs provided, and yet Netgear are still unable to confirm whether or not they've been able to identify the root cause, let alone provide a fix.
It does seem like there's something amiss with the underlying MS60 network stack.
After battling to get the MS60 to connect via WiFi backhaul - see prior messages about 30:30:30 resets and factory resets - once this finally worked, plugging in a network cable (Cat 5e vs Cat 6 UTP does not make a difference) to enable wired backhaul, the issue mysteriously appears to be solved i.e. 5Ghz devices that are connected to the MS60 are now connecting at full speed.
It did require a reboot of the MS60 and switch, to get wired backhaul to work, as the switchover from WiFi backhaul to wired backhaul didn't work automatically by just plugging in the network cable.
This was performed using the latest firmware 1.0.6.116.
The MS60 attached devices list in the Nighthawk app is still not populating when connected via wired backhaul.
And the most recent version of the Nighthawk app is broken i.e. won't connect to the MR60. One needs to reinstall the app, and only then does connecting to the MR60 work the first time, but fails to connect on subsequent attempts. How this passed any formal QA testing is baffling.
One shouldn't have to go through this much effort to get these devices to work, let alone the ridiculous amount of hours going around and around in circles troubleshooting with Netgear support folks and engineering team, with no clear path in sight to a resolution.
- markberNov 03, 2021Tutor
I asked for an update from the Netgear Engineering team re these issues:
1. MS60 network stack issues that prevents the MS60 from switching from wired to WiFI backhaul, and allowing devices to connect at speeds greater than 70 Mbps when connected via wired backhaul
2. MS60 not showing the list of attached devices in the NH app while connected to the MR60 via wired backhaul
3. NH app not connecting to the MR60 following initial setup of the NH appThe response I received is:
" This seems to be just a physical connection problem and has nothing to do with the firmware."
Can't help be flabbergasted :(
After spending over 100 hours troubleshooting the wired vs. WiFi backhaul issues, installing debug firmware, capturing debug logs etc .. it seems like this was all for nothing :(
The fact that so many other cutomers on this thread and others have experienced the exact same issue as #1, can't all be because of "physical connection problems". Seems like a copout from the Engineering team :(
And issues #2 and #3 also can't be due to "physical connection problems"
None of these issues occured around a year ago .. and as previously mentioned .. nothing has changed in my setup. The only thing that has changed is firmware.
I'm sad to this, but I give up trying to help Netgear on these issues ... since it's clear that they don't care about customers.
- FURRYe38Nov 03, 2021Guru
What happens if you go back to v1.0.0.56 on both MS and MR. Factory reset and setup from scratch using a wired PC and web browser to do all this?
- edriosNov 20, 2021Star
- edriosNov 20, 2021Star
I currently have a cable modem providing 1 Gig down and 40 Mbps up. I get 760 Mbps down and 42 Mbps up wirelessly on the MK60 router. I used the settings below, but also be aware that this speed test was done with a Wi-Fi 6 capable (802.11ax) cell phone. Results can vary with your client device.
Here are my settings:
SETUP > WIRELESS SETUP > WIRELESS SETTINGS:5 Ghz Channel: 36
ADVANCED SETUP > WIRELESS SETTINGS
Enable 20/40 MHz Coexistance: checked
Enable Implicit BEAMFORMING: checked
Enable AX: checked
- JrelsonNov 23, 2021AspirantIf its any consolation, the MR80 is just as crappy. Im returning it as soon as I can. I guess the Nighthawk side of the house forgot how to make networking gear. Pretty bad when xfinity speeds are better. Netgear...do better. Loosing customers right and left.
- FURRYe38Nov 23, 2021Guru
Thanks for posting this. Yes, client side HW will define how wireless speed test results do. Normally 2x2 MIMO devices top out at around 500-700Mbps. 4x4 devices can up up to 1000Mpbs and beyond.
edrios wrote:
I currently have a cable modem providing 1 Gig down and 40 Mbps up. I get 760 Mbps down and 42 Mbps up wirelessly on the MK60 router. I used the settings below, but also be aware that this speed test was done with a Wi-Fi 6 capable (802.11ax) cell phone. Results can vary with your client device.
Here are my settings:
SETUP > WIRELESS SETUP > WIRELESS SETTINGS:5 Ghz Channel: 36
ADVANCED SETUP > WIRELESS SETTINGS
Enable 20/40 MHz Coexistance: checked
Enable Implicit BEAMFORMING: checked
Enable AX: checked
- markberMay 09, 2022Tutor
"2. MS60 not showing the list of attached devices in the NH app while connected to the MR60 via wired backhaul"
This issue has finally been resolved in firmware 1.1.6.124
Nuts that it's taken 6 months 😞
- FURRYe38May 09, 2022Guru
Glad you got it working. Please mark your thread as solved so others will know. Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/24231/How-do-I-back-up-the-router-configuration-settings-on-my-Nighthawk-router
Enjoy. 📡 - Sablagh61May 09, 2022TutorMy slow speed has not improved. I have a Gig service and I still don’t get more than 400mbps 5 feet away