Thibor Firmware on WRTSL54GS and telnet

Discussion in 'HyperWRT Firmware' started by Deleted member 11179, Aug 22, 2007.

  1. Hi All,

    I flashed my router with thibor 17rc3 and i have the following issues :

    1- what is the username and password for telnet i used my own admin user name and password didnt work and i used root/admin didnt work.
    2- telnet i accessible internally when i try to telnet externally from my office to my box using dyndns i can not even ping it, what should i do?

    can anyone help me?

  2. ifican

    ifican Network Guru Member

    Now i dont know why and perhaps maybe one of the linux guys can tell us, but poking around i discovered there is no password set by default, so if you log into the gui and open the command line and simply input passwd and depress the enter key, your password will be set to a blank password. You can then use:

    username root
    password <blank>

    again i dont know why this is and i cant seem to change it but it let me log in via telnet.
  3. i tried it and wont work beside i can not telnet or ping the router remotely using my dyndns account. anybody else can help ?

  4. ifican

    ifican Network Guru Member

    I did this on 2 different routers with the thibor firmware so i know it works, once you run the passwd command from the command line in the gui you can then login via telnet. I did not try it remotely besides you should be minimally using ssh if you are trying to connect remotely anyways.
  5. asterger

    asterger Network Guru Member

    username <blank>
    password admin
  6. Toxic

    Toxic Administrator Staff Member

    Use SSH over the WAN. Telnet is unsecure and does not work over the WAN
  7. Thibor

    Thibor Super Moderator Staff Member Member

    1. the telnet password by default is whatever the web admin password is. the required username is "root", whereas the web admin doesn't require a username.
    2. it is not accessible via the wan. this is by design rather than a bug or oversight. if you need command line access from the internet, use SSH as it is more secure. there are obviously ways around this restriction using custom iptables rules, but I can't support such usage.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice