NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Nighthawk m1 4g+ only
Hi, My Nighthawk M1 (EE UK, not US) is currently connecting to a mast with 5 bars of signal on 4g, and gets 10mb/s speeds. There is an other local mast with 3 bars of signal on 4g+, and can get u...
Srennie837, I'm also an EE customer and have had a similar experience to you - I managed to get through to the technical support team and it was clear they knew very little about the M1. They told me to contact Netgear as explained in this post. Surprisingly, it seems they don't know when the M1 will auto-update and they are not informed of the changes in new firmware releases, even though it seems that firmware is customised for specific countries/carriers (hence our model being referred to as MR1100EE). I find this amazingly incompetent - carriers supplying modem/routers as part of a mobile internet package should insist that they are made fully aware of the status of the equipment (firmware, software, etc.) by Netgear so that they can properly support their customers.
By the way, how did you access the basic AT command data - did you have to connect to the M1 directly via tethering with the USB-C port? I've tried via Ethernet without success.
Also, how did you get the second status data for the weaker mast - was this trial and error positioning of the M1 or did you have to move closer to the mast?
Hi Luminary,
I'm glad I'm not the only person pulling my hair out.
To get into the CLI I used putty over the usb tethering on port 5510, it blocks it otherwise. To get the better mast I didn't do anything, the mast that's closer cuts out sometimes for a few minutes at a time and I happened to be in looking at settings when it did. It's annoying knowing that high speed 4g+ is so close but I can't use it.
At this rate I'm just going to solder a pair of yagi arrays together and be done with it.
I'm glad I'm not the only person pulling my hair out.
To get into the CLI I used putty over the usb tethering on port 5510, it blocks it otherwise. To get the better mast I didn't do anything, the mast that's closer cuts out sometimes for a few minutes at a time and I happened to be in looking at settings when it did. It's annoying knowing that high speed 4g+ is so close but I can't use it.
At this rate I'm just going to solder a pair of yagi arrays together and be done with it.
Sometimes "more is less". Having 2CA active sometimes can give lower performance compared to single cell from different tower. Let me explain what I mean.Sometime ago I had a experience with MR1100, I was close to single cell(distance several hundreds of meters) with SINR 30, full 256-QAM effect and DL throughput 200 Mbps+ with Huawei Mate 10 Pro cell phone. In this same place MR1100 preferred practically always 2CA from far away towers with bad signal values. It was pure struggle, "more is less"- situation. I wish MR1100 would have webgui single band lock feature for handling special situations like this. I reported this experience to Netgear system engineer. Hopefully he reports it to developers.
- Just having more options on a supposedly high-end dongle would be nice.
The issue with the mast closest to me is due to the remote location its back bearer is a sat link. The latency is terrible but the connection also drops out all the time. I'd live with it even if it was slower.
Netgear just seem very unhelpful. JasonNThe theme of band selection and performance is appearing across posts. The automatic switching back and forth between "good" and "bad" bands is confusing. It is the wrong way to communicate this information to end users who are misinterpreting it. At the end of the day, these users are trying to dial in their Nighthawk performance. These performance metrics are what Netgear needs to show instead. Further, while allowing Nighthawk owners to permanently select their cellular band likely not work for Netgear or carriers (like AT&T) it may make sense to give Nighthawk owners temporary control over cellular band that times out after 30 minutes. For example, if a Nighthawk owner is debugging performance/antenna/etc they could temporarily force band 4. Band 4 would remain for 30 minutes. After 30 minutes expires, then Nighthawk resumes normal band autoselection.
