NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ChristineT
Dec 07, 2021Administrator
Nighthawk MR5200 (M5) - We need your feedback!
Good day Nighthawk Community,
I'm reaching out to you today in hopes of soliciting your help. If anyone is experiencing any issues with the Nighthawk MR5200 (M5) Mobile Hotspot we want to hear ...
- Nov 03, 2022
Hi,
maybe it is possible to also help with the issue we experience.
We own two MR5200, let's call one "old" and the other one "new".
We use to run "old" with a Vodafone (Germany) SIM which originally came from a "Vodafone GigaCube", some kind of relabeled HUAWEI 5G Router. This setup was running fine for about 12 Month or so, but recently we started to experience interruptions of LTE connections after 12 to 24 hours. Only a reebot of "old" would help getting reconnected.
So we bought "new", used the very same SIM card with it. We experienced, that "new" wouldn't even connect to LTE nor any other band.
So we ordered a fresh SIM card and used in "new" but experienced the very same behaviour. "new" wouldn't connect to any band.
When using the fresh SIM card in "old", we were back to a connect time of about 12 to 24 hours, but then again interruptions of the connection.
JohnPengcould you take a look at the model.json stats if we upload them?
Many thanks in advance!
steveXXX
Apr 29, 2022Apprentice
I've had this issue since I bought my M5 several months back. I wrote a program to monitor
it once per minute. Summarized output from lat 24 hours:
$ grep considered log
##### cell 97602709 is considered good
##### cell 97602568 is considered good
##### cell 97602709 is considered good
##### cell 97602568 is considered good
##### cell 97602709 is considered good
##### cell 97602568 is considered good
##### cell 97602709 is considered good
##### cell 97602568 is considered good
##### cell 97602709 is considered good
##### cell 97602568 is considered good
##### cell 97602709 is considered good
##### cell 97602568 is considered good
##### cell 97602577 is considered bad
It will stay on this bad cell indefinitely, until I reboot:
07:22 > cell changed from 97602577 to 97602568
##### cell 97602568 is considered good
##### reboot detected @ April 29 2022, 7:23:04am MDT
Speedtest, before reboot:
After reboot (ie good cell again):
dpcheng
Apr 30, 2022Star
Although the login and password for the APN are blank, setting the APN authentication to PAP or CHAP seemed to have solved the problem of frequent disconnection and unable to reconnect.
The M5 automatically showed asterisks for the password which was blank when the setting was NONE.
The M5 automatically showed asterisks for the password which was blank when the setting was NONE.
- steveXXXMay 02, 2022Apprentice
dpcheng wrote:
Although the login and password for the APN are blank, setting the APN authentication to PAP or CHAP seemed to have solved the problem of frequent disconnection and unable to reconnect.
The M5 automatically showed asterisks for the password which was blank when the setting was NONE.Tried this, no joy..
------
rylos,
By "script", are you referring to my posted outputs 2 posts back?
It's straight C, compiled for a PI3. It makes use of this web URL:
Punch that into your web browser and you'll get a rather detailed JSON dump of
the devices current state.
I could bundle the code together into a tarball if there is any interest.
- steveXXXMay 02, 2022Apprentice
This might be useful for some:
It is possible to use AT commands on the Mx series over a telnet session to port 5510. Instructions are here:
https://mt-tech.fi/en/enable-manual-band-selection-on-netgear-mr1100/
These are for an MR1100, but setup of telnet is the important part to understand.
You can get a list of supported AT commands from the command AT+CLAC
$ telnet 192.168.1.1 5510
Trying 192.168.1.1...
Connected to 192.168.1.1.
Escape character is '^]'.
AT+CLAC
AT+CLAC
&C...
!gstatus
!gstatus5g
...
------------
AT!gstatus
at!gstatusCurrent Time: 54248 Mode: Online
System Mode: LTE B30 PS State: 5GSUB6
EMM state: Registered
RRC state: ConnectedPCC:
LTE band: LTE B30
LTE bw: 10 MHz
LTE Rx chan: 9820
RSSI (dBm): -76.4
RSRP (dBm): -105.5
RSRQ (dBm): -13.3
Tx Power (dBm): 22
LTE Cell ID: xxxx2709
Physical Cell ID: 94
TAC: 38417OK
---------------
AT!gstatus5g
at!gstatus5gCurrent Time: 54330
Power Mode: Online
PS State: 5GSUB6SIGNAL INFO:
LTE RSSI (dBm): -76
LTE RSRP (dBm): -105
LTE RSRQ (dB): -14
LTE SNR (dB): 13.8BAND INFO (Total 1 lists):
BAND LIST 1:
LTE band: 30
LTE channel: 9820
LTE bandwidth: 10 MHzOK
- dpchengMay 02, 2022StarAPN or Access Point Name is a gateway between the mobile network and computer network.
Username and Password – Username and Password is used to validate the point-to-point connection between the mobile network provider and the modem (the M5 or mobile device) that is using its network.
Authentication Type – The authentication type specifies the security protocol to be used for sending your username and password to the server to establish a network connection. The supported protocols are PAP(Password Authentication Protocol) and CHAP(Challenge Handshake Authentication Protocol). Incorrect values will result in failed connection and network searching.
Here are the APN settings of the more common carriers:
Verizon APN settings
APN: internet
Proxy: <Not Set>
Port: <Not Set>
Username: <Not Set>
Password: <Not Set>
Server: <Not Set>
MMSC: http://mms.vtext.com/servlets/mms
MMS proxy: <Not Set>
MMS port: 80
MCC: 310
MNC: Will differ in different regions, for instance 012
Authentication type: <Not Set>
APN type: <Not Set> or Internet + MMS
APN Protocol: <Default>
Bearer: <Not Set>
T-Mobile APN settings
APN: epc.tmobile.com, or fast.tmobile.com (LTE)
Proxy: <Not Set>
Port: <Not Set>
Username: <Not Set>
Password: <Not Set>
Server: wap.voicestream.com
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS proxy: 216.155.165.50
MMS port: <Not Set>
MCC: 310
MNC: Will differ in different regions, for instance 260
Authentication type: <Not Set>
APN type: <Not Set> or Internet + MMS
APN Protocol: IPv4
Bearer: <Not Set>
Boost Mobile APN settings
APN: Boost_Mobile
Proxy: <Not Set>
Port: <Not Set>
User Name: Boost_Mobile
Password:
Server:
MMSC: http://mm.myboostmobile.com
MMS Proxy: 68.28.31.7
MMS Port: 80
MCC: 311
MNC: Will differ in different regions, for instance 870
Authentication type: <Not Set>
APN type: default,admin,fota,mms,supl,hipri
APN Protocol: <Not Set>
Bearer: <Not Set>
US Cellular APN settings
APN: internet
Proxy: <Not Set>
Port: <Not Set>
Username: yourMSID@uscc.net
Password: your MSID
Server: wap.voicestream.com
MMSC: http://mmsc1.uscc.net/mmsc/mms
MMS proxy: blank
MMS port: 80
MCC: 310
MNC: Will differ in different regions, for instance 120
Authentication type: <Not Set>
APN type: <Not Set> or Internet + MMS
APN Protocol: iPv4
Bearer: <Not Set>
AT&T APN Settings Name: ATT
APN: phone
Proxy: <Not Set>
Port: <Not Set>
Username: <Not Set>
Password: <Not Set>
Server: <Not Set>
MMSC: http://mmsc.mobile.att.net
MMS proxy: proxy.mobile.att.net
MMS port: 80
MCC: 310
MNC: Will differ in different regions,for instance 410
Authentication type: <Not Set>
APN type: default,supl,mms,hipri
APN Protocol: IPv4
Bearer: <Not Set>
Sprint APN settings
APN: cinet.spcs
Proxy: <Not Set>
Port: <Not Set>
Username: yourMSID@uscc.net
Password: your MSID
Server: wap.voicestream.com
MMSC: http://mmsc1.uscc.net/mmsc/mms
MMS proxy: 68.28.31.7
MMS port: <Not Set>
MCC: 234
MNC: Will differ in different regions,for instance 15
Authentication type: <Not Set>
APN type: <Not Set>
APN Protocol: iPv4
Bearer: <Not Set>
Virgin Mobile APN settings
APN: Sprint
Proxy: <Not Set>
Port: <Not Set>
Username: <Not Set>
Password: <Not Set>
Server: <Not Set>
MMSC: http://mmsc.vmobl.com:8080/mms?
MMS proxy: 205.239.233.136
MMS port: 81
MCC: 310
MNC: <Not Set>
Authentication type: <Not Set>
APN type: default,supl,mms
APN Protocol: iPv4
Bearer: <Not Set>
In my case, the mobile carrier is 3
Username: <Not Set> (blank)
Password: <Not Set> (blank)
Authentication: PAP
Although both username and password is blank, setting Authentication to NONE resulted in mobile network disconnection, failed dial-up reconnection and network searching.