NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Nighthawk M1 IP addresses - allow both dynamic and static
The Nighthawk M1 network IP address setup currently allows either dynamic DHCP address assignment within a specified range or fully manual assignment of static IP addresses to wired or WiFi connected devices. However, it's not currently possible to enable DHCP addressing within a specified range together with some additional manually specified static IP addresses. This is a problem where some devices in the network need static addresses, such as printers, but where automated dynamic addressing is needed for "visiting" devices on the network. I currently have DHCP enabled in my M1 but this means that when my networked printer is powered up it's often allocated a different IP address, so to print from a networked PC I first have to access the browser interface to the M1 to find the IP address and then go into the PC's control panel to modify the address in the printer port setting. Could the firmware / interface be modified so that DHCP can be enabled but at the same time allow some static IP addresses to be specified for printers, etc. so that they can always be located by other networked devices? If anyone else feels this would be a beneficial feature, please add your comments. The mobile network provider that supplied the M1 to me is EE in the UK (there's no option to specify MR1100EE¦Nighthawk LTE Mobile Hotspot Router (UK) in this post) but I guess that the US and Australian firmware also has this "either/or" limitation with the dynamic and static IP addressing.MR1100 + 2 access points - DHCP address problems
My Nighthawk MR1100 (M1) is connected via Ethernet to an unmanaged switch, into which 2 access points are connected to distribute dual band WiFi around the house. Since the most recent firmware update (NTG9X50C_10.22.03.00 build date 22nd Nov 2017) the Ethernet port is staying awake but I'm having problems when I move a WiFi-connected device from one end of the house to the other: if the device is connected via one of the access points (rather than directly to the M1's WiFi) and I then attempt to connect via the other access point, it states (Obtaining IP address...) but never connects. One way I've found to solve this is to connect directly to the M1 WiFi first and then connect to the 2nd access point. It's like the M1's DHCP isn't issuing a new IP address to the device, or at least allowing the device to keep the same IP address but move to a new access point. I've allocated the 2 access points IP addresses that are outside the DHCP range of the M1 (changed from the default range to 192.168.1.80 to 192.168.1.149) and they are not the same as the M1's address (left on the default). The DHCP service is disabled on both access points (they are actually modem/routers converted to access points). Is this a fault with the M1's DHCP functionality or does this Ethernet switch + 2 access points configuration cause similar WiFi connectivity/IP address allocation problems with other routers?