Opened 8 years ago

Closed 7 years ago

#7047 closed defect (worksforme)

dropbear doesn't start after changing the password

Reported by: pyther@… Owned by: developers
Priority: response-needed Milestone: Backfire 10.03.1
Component: base system Version: Backfire 10.03
Keywords: Cc:


After flashing my router with 10.03 RC2 I telnet'd in and issued passwd to change the root password. Then I attempted to login via ssh using the command ssh root@ without any luck. Restarting the dropbear service via /etc/rc.d/dropbear seemed to resolve the issue.

However, if you do not restart the dropbear service upon reboot ssh is still disabled. This results in not being able to login since telnet is disabled and ssh appears to also be disabled. The web interface crashes whenever I attempt to login (this might be a separate issue).

Router: WZR-HP-G300NH

Attachments (0)

Change History (9)

comment:1 Changed 8 years ago by thepeople

  • Milestone changed from Backfire 10.03-rc3 to Backfire 10.03

comment:2 Changed 8 years ago by Matthew <pyther@…>

ps aux shows the following process

/bin/sh /etc/rc.common /etc/rc.d/S50dropbear start

It appears that this process is taking a while to exit, at least 30 seconds if not more. I also believe that the command that adds dropbear to the startup also takes a little while.

comment:3 Changed 8 years ago by nico

  • Resolution set to duplicate
  • Status changed from new to closed

See #7046

comment:4 Changed 8 years ago by pyther@…

  • Resolution duplicate deleted
  • Status changed from closed to reopened

This issue is still present with 10.03 (final).
Ticket #7046 is different and as noted on that ticket, it does not seem to be a problem anymore.

comment:5 Changed 8 years ago by nico

  • Version changed from Backfire 10.03 RC2 to Backfire 10.03

comment:6 Changed 7 years ago by nico

  • Priority changed from high to response-needed

Can you confirm this issue is still present in 10.03.1-rc1 ?

comment:7 Changed 7 years ago by anonymous

i'm not sure if this is the same result, but using trunk i installed dropbear via opkg (self-built, no other modification though). i set my root password and "/etc/init.d/dropbear start" to test my ssh setup. i ssh'd in without any issue, so i restarted the router. telnet attempts fail as expected, but ssh connection attempts are refused. i can only assume dropbear isn't running. this is an otherwise virgin/vanilla installation.

comment:8 Changed 7 years ago by cshore

You may not have enough flash space left after flashing the image for
jffs2 partition, so you may be running only off ramdisk, and thus have
not permanent settings. do df to see how much space on /overlay.

comment:9 Changed 7 years ago by nbd

  • Resolution set to worksforme
  • Status changed from reopened to closed

If you install dropbear into an image that doesn't have it already, you need to run /etc/init.d/dropbear enable

Add Comment

Modify Ticket

as closed .
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.