NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
HannuKop
Mar 29, 2018Aspirant
Nighthawk M1 - Data offloading won't work
Nighthawk M1 LTE Mobile Router, latest firmware (of March 2018), latest Netgeat Mobile App installed. I'm trying to get the data offloading feature to work, with little success. Tested it with two s...
UK-based
Mar 29, 2018Luminary
Is it possible that the router you are connecting to, via WiFi or Ethernet data offloading, has the same IP address as your M1 (192.168.1.1 by default)? If so, you could try changing the Gateway IP address of the M1. I'm not sure what happens when you enable data offloading - I guess the M1 could pick up an address via DHCP from the other router, or perhaps it retains its own IP address.
HannuKop
Mar 29, 2018Aspirant
This happens with two separate WiFi routers I'm trying to offload to, but could be. What would be workable alternate gateway IP?
- HannuKopMar 29, 2018Aspirant
Tiny addition: with wired connection the data offloading works perfectly. I plugged the network cable in and everything worked great right away. WiFi offloading on the other hand....
- UK-basedMar 29, 2018Luminary
Sorry, I didn't see your "tiny addition" before sending my reply. If it works with the wired connection, I have my doubts about a clash with the other router's IP address but you could always check this. There are other more experienced contributors than me who may be able to help you further, such as MicW
- HannuKopMar 29, 2018Aspirant
Hi,
The router indeed has that IP:
- IP Address: 192.168.1.1
- IP Subnet Mask: 255.255.255.0
- DHCP: ServerAnd I presume the other has as well.
But when connected to this router with ethernet cable offloading works, when trying WiFi with the same router I get the error mentioned. But I will try changing the IP.
Thanks!
- UK-basedMar 29, 2018Luminary
Before making any changes, can you log into the other router and find out if it's IP address is indeed 192.168.1.1? If this isn't the case, the problem must be something else. If it's the same as the M1, you could try changing the M1 IP to 192.168.1.2, assuming that's not included in the DHCP address range of the other router, in which case you could still have an IP address clash. Remember that if you change the M1 IP address, you'll have to use that new address if you want to access its interface via a browser. If this doesn't work out, you can always do a factory reset on the M1 to get the default gateway IP address back - you'll of course lose any other setting changes from default that you've made.