NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

repharm's avatar
repharm
Tutor
Aug 14, 2020

Netgear MR2100 command line access, telnet port

I have new MR2100 (f/w NTGX24_10.17.01.00 - no newer available) and want to establish connection to CLI in order to make band lock selections available. - Router is out from the package - 192.168.1.1 is the address - USB-C connection established and works towards internet - Charge + tether selected - telnet 192.168.1.1 5510/5511 (and others tested) gives Connection refused. No other port works either. How to access CLI for AT commands in MR2100? Thanks!

4 Replies

  • if you are able to access the Internet via USB-C connection toward MR2100, then Telnet to its IP at port 5510 should work. What you can do is to make sure you can login to MR2100 with browser first, then try with telnet at that specific port.

    • repharm's avatar
      repharm
      Tutor

      Thanks! got it working and logging to admin interface was ok. I also changed telnet client (using Mac) to Telnet Lite (Appstore) and works just fine now.

       

      • repharm's avatar
        repharm
        Tutor

        Hi all,

        Telnetting to MR2100 M2 works well with like Telnet Lite (Mac OSX) to 5510 through USB with no problem.

        Yesterday I was playing with band locks again to see if there's anything to do to increase throughput at my location. Well, at the end, no change to better compared to "LTE All" or "Auto". 

         

        But decided to document here one trivial thing I was struggling with a bit. 

         

        You can find basic principles of AT-commands and using them for M1 at https://mt-tech.fi/netgear-mr1100-1gbit-s-4g-reititin/ - don't worry, it looks to be in Finnish but scrolling it down AT CLI is a common language. And for some of us earliy adopters let us dive back to our '80's and '90s with 2400/2400 etc life.

         

        Other points to those AT commands in MR2100 M2 compared to M1:

        1. You need a <space> between the AT and the command, ie. "AT !GSTATUS=?" instead of "AT!GSTATUS=?"

        2. When programming I couldn't have more that three (04 the highest) band locks (is there a way to do more?)

        3. You need to add ",0" at the end of commands compared to M1, ie "AT !BAND=04,"LTE B28",0,8000000,0" and

        4. Sometimes for me at least it didn't pick correctly the text in " .... " lik" "LTE B28" sometimes came out as "LTE B" etc. But trying it couple of times it worked.

         

        With these changes and notes the original article works with MR2100 M2. 

         

        Happy locking.