NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
19 Replies
Just got the new nighthawk LTE a few days ago and every morning we have to reboot (or wakeup) the box for the wifi signal to be noticed. I think it is going in sleep mode but dont know what settings to change so computer and gadgets stay locked into the device. Any suggestions? Thanks
I have exact same issue. Can the sleep mode be disabled.
If you are referring to the WiFi sleeping after a given period, this sleep can be disabled using the Netgear app (Android or iOS). The feature is in the Settings section under the WiFi heading - you should find the "Sleep" setting there - set it to "Disabled". This setting isn't included in the browser-based interface for the MR1100 (at least not in my version, which is from the mobile network provider EE in the UK).
However, the Ethernet port also sleeps after a period of no activity. This can be woken up by tapping the power button once - it wakes after a few seconds.
I have my MR1100 set up as my main household router - the Ethernet port is connected to a Gigabit Ethernet switch and I have 2 dual band WiFi access points also connected into the switch. The fact that the Ethernet port goes to sleep is frustrating because devices attempting to connect by WiFi to one of the access points don't get an IP address allocated to them by the DHCP on the MR1100. I have to tap the power button on the MR1100 if it's asleep and then the devices get their IP addresses.
One of the Netgear moderators said there will be a new firmware release in Feb that will allow the Ethernet port to be set permanently on. There will also be the option to turn on the Ethernet port by default after a reboot - at the moment the Ethernet port is turned off by default after a reboot. Here's the post from the Netgear moderator: Nighthawk-M1-Ethernet-Port-Timeout
I have this netgear product trying to connect in Venezuela witn not success. The Company mobile name in Venezuela, trying to connest, is DIGITEL. It works in 3G and 4G bands.
I had reseted my equipment to factory standards, while in Venezuela.
I try to set up the equipment qit DIGITEL APN, but it did not work.
Can you help me or instruct me to set up this equipment to Venezuela local telephone service.?
Medinaaxc
- You might want to check band availability in country. The modem may not support the bands within the country.
I have checked bands used by the DIGITEL Venezuelan tMobile Company, and the bands 3G and 4G, are manged by this company. So, modem can support these bands.
Another recomendation you may add?
So, we absolutely love ours. Connection is amazing and works awesome out here in the country (we have no other internet options in our rural area). The only problem is we run 3 businesses out of our home and we get rejection messages all the time from business recipients on emails because of the ever changing ISP address. Does anyone know if it is possible to get a static IPv4 address from the ISP on these types of devices without either A) changing plans B) being a business customer or C) paying a ridiculous price? So far, I've just been submitting the IP changes to remove from blacklists which works occasionally but, of course, the ip's change again. That's the only issue we're getting with being on this device for both personal and work.
- If you have 3 businesses why aren't you running a G-Suite/O365 solution? IPs could change as little as 1 month to several times daily.
We ARE on 0365. The issue is on the recipients. not our sender accounts even with the DMARC. It never reaches the recipient because even with a whitelisted domain, many firewalls are rejecting the ip source. For instance, our current public IP just changed to 166.137.105.197. You can see from this example, that IP is flagged on blacklists RATS and Spamhaus. Spamhaus exceptions update quickly but we email a lot of vendors all whom have different policies in place. It's tedious and as soon as they whitelist, the IP changes. The rules of mail flow in 0365 on recipient end (for those that are also utilizing it) only allow an IP range for exclusion; there is no defined range with ATT that can currently be provided. https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a166.137.105.197&run=toolpage
