Factory reset – locked me out

Home Forums Conduit: AEP Model Factory reset – locked me out

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #30227
    Lucian Corduneanu
    Participant

    Hi guys,

    I recently upgraded to 5.1.2 from web UI. I performed a factory reset (first from web UI, then from button, holding more than 30 sec).

    Now I’m locked out of the system. It seems like the default credentials are not working anymore. I tried:

    1. admin / admin
    2. admin / root
    3. root / admin
    4. mtadm / root
    5. mtcdt / root

    Please help!

    
         _        _____     ____
        / \      | ____|   |  _ \
       / _ \     |  _|     | |_) |
      / ___ \  _ | |___  _ |  __/_
     /_/   \_\(_)|_____|(_)|_|  (_)
    
    MultiTech Systems Application Enablement Platform with mLinux GNU/Linux
    
    mLinux 5.1.6 mtcdt /dev/ttyGS0
    
    Version: 5.1.2
    Date: 2019-12-03T11:22:53
    mtcdt login:
    

    EDIT> I’m trying to connect via USB debug cable. Seems like the network interfaces are not well configured, and I don’t have access to web UI.

    #30229
    Lucian Corduneanu
    Participant

    I read the following pages:

    http://www.multitech.net/developer/software/mlinux/getting-started-with-conduit-mlinux/

    http://www.multitech.net/developer/software/aep/reset-button-behavior-for-aep/

    Hmm, this is interesting.

    http://www.multitech.net/developer/software/aep/aep-firmware-changelog/

    A Hard Reset (or Factory Default) will force 5.0.1 firmware into Commissioning
    Mode to create a new Administrative Username and Password.

    Eliminate Default Username and Password. User prompted to set up a Username and secure Password upon Factory Default/Hard Reset, Commissioning Mode.

    https://www.multitech.net/developer/software/mtr-software/mtr-api-reference/rcell_api_requests/commissioning/

    How to create a user in Commissioning mode please?

    #30231
    Lucian Corduneanu
    Participant

    Alright. I figured it out.

    There is no user at first, only through Web UI, you can create one.

    I properly connected and configured the network interfaces so that the default 192.168.2.1 – address of the Conduit AEP is used, only after that I was able to first create the user, then login.

    #30233
    Jason Reiss
    Keymaster

    Thanks for the topic and follow-up.

    #30234
    Lucian Corduneanu
    Participant

    Well, it remains one question though:

    How can I have ssh access with root privileges?

    Seems like the users I created through the commissioning mode, is not among sudoers.

    Any help is appreciated. Thanks 🙂

    #30235
    Jason Reiss
    Keymaster

    The user created through commissioning mode should be able to elevate to sudo.

    Try after login through ssh.
    $ sudo -s

    #30236
    Lucian Corduneanu
    Participant

    Well, I tried many things.

    admin@mtcdt:~$ sudo -s
    Password:
    admin is not in the sudoers file.  This incident will be reported.

    However, I think it’s worth mentioning, right before the first factory reset I edited with sudo visudo and maybe I messed up something there, in my attempt to gain root access.

    Isn’t the factory reset, fixing this as well?
    If not, is there a way for me to gain root access somehow from Web UI?

    Thank you.

    #30237
    Lucian Corduneanu
    Participant

    Damn it, yeah it could be that this is the case.
    I remember I commented out a line and enable another. Don’t know which, but I think I enabled the:

    # Allow members of group sudo to execute any command
    %sudo ALL=(ALL:ALL) ALL

    #30239
    Jason Reiss
    Keymaster

    You will need to do the firmware upgrade with 5.1.2 to restore the suders file. Factory reset only affects the config partition.

    #30240
    Lucian Corduneanu
    Participant

    Excellent! Thank you.

    That was enough to restore it. I now have root access with sudo -s.

    #30412
    Ben Ward
    Participant

    There is no user at first, only through Web UI, you can create one.

    Thanks for spotting this, Lucian. I struggled to diagnose this because the factory reset AEP took on my router’s IP address (192.168.2.1) so http didn’t work. Resorting to USB debugging I then struggled to find any username/password combination that worked, so thought I’d lost my mind. Thanks for saving the AEP from the bin.

    Also worth mentioning to save 20 minutes of messing about. The PATH is pretty useless, and ifconfig is here:

    /sbin/ifconfig

    Ben

    • This reply was modified 4 years, 1 month ago by Ben Ward. Reason: messing about finding your IP address
Viewing 11 posts - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.