NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Nighthawk M6 Pro Ethernet port
After recent automatic update, Ethernet port on nighthawk M6 Pro not working. Can toggle it on/off, but has no output signal. Any troubleshooting suggestions?
68 Replies
Replies have been turned off for this discussion
Adding in my details if it helps AT&T or NetGear figure out what in the world they have done.
This is the same as deuxcv listed but different from rcpax data.
Model: MR6500
Firmware Version: NTGX65 12.01.72.00
Firmware Build Date: 2025/07/29
Hardware Version: 1.0
Device Information
Hardware Version: 1.0
PRI Version: 04.09
AT&T
Web App Version: MR6500-1A1NAS_05.00.118.00
Modem Version: MPSS.DE.2.0-00989- OLYMPIC_GENALL_PACK-1.41921.6.45826.2
any tips on getting them to replace your m6 with m7?
do you happen to know if the update at fauld was from att or Netgear?
During my weekend tests of Firmware 1.2.1, I observed that the problem stemmed from the WLAN channel. Speeds were unstable on channels 52-64. Channels 36-48 showed no problems. Until now, I'd been using channels 52-64 because they weren't used in my area. Unfortunately, since I couldn't revert to the old firmware, I started using channels 36-48.
Are you saying the ethernet is fixed on different channels? Pardon my ignorance, but how do you change this exactly?
new m7 works perfect, updated to current firmware. actually works better and better speeds than with the m6. would suggest calling and threaten to cancel your account thats how I got mine.
MR6150 here. Went into Settings/More and Ethernet, was disabled. Enabled it and said MR had to reboot. Continued. After MR was back to ready, ethernet connected PC gets internet from ethernet port on MR. IP Pass thru is not enabled.
Tried to set up as StevenL1 suggested (go to bridge mode and connect Ethernet to WAN on router). No joy for me. Could connect wireless but was unable to actually load any pages.
Installed refurbed MR6500 that came in today and all works as should. If there's ever a fix for this issue, I'll have a spare MR6500.
Sorry to hear it didn’t work for you with the ethernet to router in bridge mode. I just have a cheap TP link router from walmart
Glad to hear you’re back up and running with a new M6 though. Does it have the same firmware as the old? Going to be trying to call again tomorrow to see if I can finally connect to somebody
Not sure the version of firmware on the new M6. Once we had it up and running, didn't want to tink with it anymore.
We tried using a Linksys router that we no longer when we tested bridge mode. Not sure why it didn't work for us.
We'll see if another firmware version gets pushed out on this M6. Fingers crossed.
I use firstnet with this device. MR6110. As of today, the ethernet port failed after the latest firmware update pushed itself through. Firstnet advised netgear is working to resolve the issue. Might consider upgrading to M7. Thoughts?
I also did all troubleshooting including pinhole factory reset and connecting directly to laptop, to no avail. Usual set up is to a mesh network as access points. Speeds went from 170 to 10 to now nothing lol.
You should give us the option to rollback previous firmware, or just roll it back for us and make everybody happy while you guys take God knows how long to get another update out to fix the issue at hand. Thanks
I talked to AT&T again today. They still have no update, but said to check back next week. They said it was a NETGEAR update and NETGEAR is working on a solution. I asked about rolling back and they were told an Ethernet connection is required for a rollback. I don’t understand that, but that’s what ATT tech support was told. Pass through is working for me, with a drop now and then. It’s better than nothing, which is what I had before. Disappointed that NETGEAR lied about who pushed the update in the first place. Take responsibility and fix it.
we got an update yesterday right before I left work,but I was in a hurry to leave so didn't take it out of bridge mode to test.
the firmware was the same number...12.0.1.72.00 from July so was probably another update like last Friday. so I'm hopeful it was fixed.
The update that became available yesterday fixed both of my devices. No other changes or bridge mode settings needed.
