#19993: After reboot, WAN SSH fails unless DropBear is restarted
----------------------------+----------------------------------
Reporter: jw0914 | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Chaos Calmer (trunk)
Component: packages | Version: Trunk
Keywords: dropbear , ssh |
----------------------------+----------------------------------
After reboot, remote WAN SSH fails unless DropBear is restarted, whereas
LAN SSH has no issues.
(I'm not sure what information is needed, so please let me know what other
information I need to pull and post.)
K.V.: 3.18.16
F.V.: r46118 / LuCI (git-15.168.50780-bae48b6)
DropBear V.: 2015.67-1
LAN SSH is set to it's own port and set to LAN only
WAN SSH is set to it's own port and set to WAN only
From looking at the running processes, DropBear is starting a process for
the LAN SSH port, but is not starting the subsequent process for the WAN
SSH port. As a workaround, I'll simply add a command to restart DropBear
after a reboot.
--
Ticket URL: <https://dev.openwrt.org/ticket/19993>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
