1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

telnet to rv082 with firmware 1.3.2?

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by rcptx, Jul 1, 2006.

  1. rcptx

    rcptx LI Guru Member

    Hi,

    I recently updated to firmware 1.3.2 and can no longer telnet to the rv082.

    Is there a way to enable telnet?
    Should I have stayed with previous firmware (1.1.6)?
    Is it safe to reinstall 1.1.6 over 1.3.2?

    Thanks,
    Bob
     
  2. perak

    perak Network Guru Member

    Hi Bob,

    I have reinstalled the old fw 1.1.6.14 back from 1.3.2 on
    two RV082:s. I had problem with a VPN tunnel
    which was stable with the old fw but not with the new.

    The reinstallation worked fine.

    You will lose all your settings so it might be a good idea
    to make a backup of them before reinstalling the old fw.

    I have not used telnet on the RV082 at all.

    perak
     
  3. Toxic

    Toxic Administrator Staff Member

    The rv042 I was able to do this,

    http://192.168.1.1/sysinfo123.htm?ConsoleSimulation=1

    telnet 192.168.1.1

    Username:admin
    Password:admin

    rg_conf_set /nk/telnetd_enabled 1
    flash_commit
    reboot

    then telnet is enabled. I dont know if tit will work on the RV082 but maybe worth a try.
     
  4. rcptx

    rcptx LI Guru Member

    Thanks!

    This worked like a champ! Where do you find this kind of info?

    Bob
     
  5. Toxic

    Toxic Administrator Staff Member

    in my brain :doh:

    nah it was in the RV042 information thread.

    glad it helped.
     
  6. rcptx

    rcptx LI Guru Member

    I should add that I didn't need to do this part:

    [hr:ba07ca3430]rg_conf_set /nk/telnetd_enabled 1
    flash_commit
    reboot
    [hr:ba07ca3430]
    When I did "rg_conf_print /nk" nothing with "telnet" in it showed up so that item may or may not apply to the RV082 firmware.

    I was able to log off and telnet back in again OK.

    But I will keep this in mind -- if I ever reboot the system and telnet stops working something like the above *might* be needed.
     
  7. Toxic

    Toxic Administrator Staff Member

    were you in shell (busybox) or the cli?

    can you so me the commands listed in the cli?

    press TAB and it list all commands
     
  8. rcptx

    rcptx LI Guru Member

    I explored both the initial CLI and the busybox shell. Looked much as it did with earlier firmware.

    Here are CLI commands:

    exit
    die
    ps
    rg_conf_print
    rg_conf_set
    rg_conf_set_obscure
    rg_conf_del
    rg_conf_ram_set
    rg_conf_ram_print
    reconf
    entity_close
    host
    rgpf_config
    rgpf_info
    rgpf_info2
    fw_set_age
    flash_commit
    restore_default
    reboot
    log_lev_on
    log_lev_off
    exec
    rmt_upd
    rmt_upd_wget_close
    rg_ifconfig
    cat
    shell
    cat_log
    bridge_info
    flash_layout
    flash_erase
    flash_dump
    bset
    ifconfig
    ping
    nk_ip
    monlink
    monlinkend
    wandown
    wanup
    lbtrafficup
    lbtrafficdown
    setequalize
    delequalize
    addinf
    delinf
    activewaninf
    teravpn
    addvpn
    addvpn_ip_fqdn
    switch_reset_set
    switch_stat_get
    read_sw_reent
    mem_alloc
    mem_alloc_free
    nk_tag_vlan
    nk_vlan_all
    boot
    load
    8021x_open
    8021x_close
    8021x_status
    8021x_set_mode
    8021x_mac_auth
    nk_factory_print
    nk_factory_set
    ver
    help
    etask_list_dump
     
  9. Toxic

    Toxic Administrator Staff Member

    looks very simialr to mine, though you say

    rg_conf_set /nk/telnetd_enabled 1

    in CLI does not work?
     
  10. rcptx

    rcptx LI Guru Member

    I didn't say it didn't work. I just said telent seems to be working fine without doing that.

    I also tried to point out that that particular configuration option may not even exist on RV082 firmware since rg_config_print doesn't show it. Could be that it will come into existence if I run those commands. Could be that they are what is needed to keep telnet enabled across reboots. But I don't want to reboot unless I need to and so far everything is working OK without it. Next time I need to reboot I'll find out!

    Bob
     
  11. Toxic

    Toxic Administrator Staff Member

    yes the command makes telnet last after rebooting
     

Share This Page