NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
M6 PRO Wifi Signal Dropping Out
We have a M6 Pro Nighthawk modem which has been great & worked very well the past couple of years. The Nighthawk is connected directly to power with no battery fitted & has a couple of wifi cameras running off them at 2.4g. However in the past week (since the latest firmware update 25/10) it now works for a couple of hours & then stops transmitting a wifi signal, like its gone into standby mode... Yes Wifi standby is switch to Never. We are located in Australia & the modem is recieving Telstra 5G signal on the dashboard, however not transmitting wifi to the devices connected. There are 4 devices showing as connected to the Wifi. When you click on the Data Usage section, normally this shows how much data has been used & how many days left on the plan. After a couple of hours once the Wifi transmission signal drops out, if you go back into the Data Usage section it no longer shows any data information - "Data usage info unavailable at this time" is the messaging on the screen. Anyone had any problems with signal dropping out since the firmware update?? Please help... 👍M6 and IP-passthrough with routable static IP
I have an M6 Pro (MR6550) and a T-Mobile business internet account, and I'm unable to use the M6 in passthrough mode. The M6 (the hotspot) does some pretty inexplicable things. Like ARP my firewall from 192.168.3.1. As I said, my firewall has a public routable (non RFC-1918) address, so 192.168.3.1 is not going to be adjacent on the subnet, and therefore my firewall will drop the ARP request at a minimum, and potentially trigger the IDS as there being misconfiguration of a peer on the network or even someone doing malicious probes. It also sends SSDP packets to my network segment as multicasts. Why? Only hackers use SSDP on a WAN interface: to figure out (1) if you're misconfigured and (2) to know what sort of machines are on your network so they can tailor attacks after fingerprinting the hosts and looking up their attack surfaces and vulnerabilities. But more to the point, it's a modem/bridge. It should be operating at layer 2 on the Ethernet side, and layer 3 on the 4G/5G side. The correct behavior is trivial: (1) When the APN provisioning is received from the 5G carrier, PROXY ARP the default gateway's IP address with your own (M6's) MAC address (or GARP it, that works too if the firewall has been sysctl'd to accept GARP's on a public interface... which is sometimes used for man-in-the-middle attacks on public networks). (2) Then ARP REQUEST the firewall's IP address so you know where to forward the packets. That 2nd step is likely unnecessary, since most IP neighbor implementations cache the address of an ARP requestor in anticipation of their being return traffic (i.e. some sort of answer). You don't need SSDP. Or mDNS. Or to be trying to figure out anything about what's attached to the firewall. That's just suspicious behavior. Also, don't IPv6 SSDP me if I'm not provisioned for IPv6! That just fills my logs with noise. If I do a ping -c 1000 8.8.8.8 then I see spans of 8 or 9 packets being passed, then 20 or so dropped, then 8 or 9 passed, then 20 or so dropped... until the test completes. How did this not turn up during homologation testing? I'm getting 62-70% packet loss!!!M7 Pro (MR7400)... Bridge Mode/IP-Passthrough Only Works After Reboot?
As the topic says... If I reboot the router to which the M7 is attached via eth, then I have to reboot the M7 as well before bridge mode works. Has anyone else experienced this, or the contrary; bridge mode works without having to reboot the M7? Also.... what gives with not being able to register the product for support? Netgear product registration either fails and says try again later, or the contact us link through support says support expired on 1900-01-01... Time travel!!!!! Woo hoo! <grumble>... and these compulsory forum tags that don't include relevant products... <sigh>
NIGHTHAWK M6 & M6 PRO Connectivity Issue Resolved!
Hello NIGHTHAWK Community, A new software update is now available and being pushed over the air to all AT&T M6 Pro and M6 devices to address the recent Ethernet issue. If your device does not show PRI version 4.10 under Device Information, please check for updates manually from your device. We thank you for your continued patronage! Best, NETGEAR TeamMR7500 M7 Blocking VPN clients with MacOS Tahoe 26
Hi, I run a MacBookPro M2 through a MR7500 Nighthawk M7 (on the Telstra network). I use OpenVPN client software to connect to a remote business network, and it has been running fine for years. However after recently upgrading to MacOS Tahoe 26 on my laptop, iPad and iPhone, my M7 is blocking my Open VPN connections. If I run my iPad, iPhone or Macbook Pro directly through a seperate 5G hotspot everything runs as expected. If I run my iPad, iPhone and MackBook Pro through my MR7500 Nighthawk M7 via a Wi-Fi or wired connection, OpenVPN will connect but I cannot access the business network. I have found I need to run OpenVPN through ProtonVPN (tunnel in a tunnel) to access the business network, which effectively hides OpenVPN from the M7. I reset the M7 back to factory default, but still have the issue. I have uninstalled and reinstalled VPN software multiple times. I have the same problem with the Tunnelblick VPN client, so it is not just OpenVPN. Looks like Apple may have removed some legacy IPsec protocols in Tahoe OS which is tripping up the M7. Does anyone have any suggestions?MR7400 (M7 Pro AT&T)
I've got it setup, firmware updated, but I'm unable to change specific settings like WIFI settings, even disabling/enabling wifi is not enabled, either on the device or through http://attwifimanager/. A number of settings are simply greyed out and you're not able to interact with them. After factory resetting, I notice the settings are interactable for a brief time before the device restarts (out of no where) - I was actually able to update the wifi standby setting before the restart happened. Then they return to being disabled, grey options - but the setting that I did change before being disabled persisted as the value that I set. Super weird, could be firmware, or a faulty device because I don't see any other threads discussing the same thing.
