Bugzilla – Bug 11922
Can't enable SSH access
Last modified: 2009-09-08 09:30:43 UTC
With r5511 and r5529, I'm unable to enable ssh access. I can check the box, but the setting doesn't stick.
For me the checkbox does stick, but dropbear never starts. "start-stop-daemon: not found" is the error from: /etc/init.d/dropbear start running "dropbear" from the command line seems to work ok. Richard: this isn't related to the new kernel is it?
From Campfire: Mark M. I'll add this to the bug, but I just discovered that on my old (PB1?) unit, the box stays checked and ssh works. On my newer (PB3?) unit, the checkmark won't stick and ssh won't work. Richard T. it's only the very latest firmware that'll have this problem. Mark M. Both are 5529 Apr 29 12:20 PM Richard T. ok, maybe the PB1 had it enabled before you updated. Richard T. it probably can't change state. Mark M. Richard, that's likely the case if I recall how/when I updated each unit Richard T. that'll make much more sense than the hardware rev. Mark M. Hmm. I was just able to confirm on the PB1 that I could turn off ssh, the box would stick, and port 22 was closed. I then reenabled it, and ssh works again
Is change 5537 to fix this? Maybe I'm just doing something stupid - I admit that I have an unnecessarily complex home LAN, but... After updating to r5543, my newer unit (it's really a PB2) still had the problem where the ssh checkbox wouldn't stick. ssh continues to work fine on the PB1. After a factory reset of the PB2, the checkbox now sticks, but it still won't let me ssh in.
please do a factory reset and verify that it's still broken. nb: the dropbear issue was a red herring, that init.d script never worked. ssh is enabled by the lua applet directly editing the inetd config file.
(In reply to comment #4) > please do a factory reset and verify that it's still broken. Yeah, as per comment 3, I did a factory reset. Maybe it's my network, but I haven't changed anything from when it worked pre-5511. I'll test more tomorrow.
Hmm... nmap reported: PORT STATE SERVICE 22/tcp closed ssh Then, after a non-factory reset (short button press), ssh now works fine and nmap reports the port as open. So, it works now and I have no idea how to reproduce...
Still working on r5578. I still think there's an obscure bug that caused me to reset twice before it worked, but I have no idea how to reproduce it. Closing.