#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
Resolution: | Keywords: dropbear , ssh
-----------------------+----------------------------------
Comment (by m+openwrt@…):
Following the situation for barrier breaker which - at least to my
knowledge - is still the same for trunk:
Well, it is only possible to bind dropbear to IP-Adresses and not to
interfaces. Because of that, the interface config option is a bit
misleading. It has to be read as "bind to ip-addresses of interface".
I assume your openWRT device get its WAN IP-Adress via pppoe/dhcp and that
happens '''after''' dropbear is started in the openwrt boot process. The
logical consequence: The WAN interface has no IP-Adress which dropbear can
listen on.
You have to add a hotplug script that restarts dropbear when the WAN
interface comes up as illustrated by
http://wiki.openwrt.org/doc/uci/dropbear to fix your issue. Maybe it's
possible to add an interface specific dropbear reload trigger via netifd
or procd. I guess the later one would be accepted for inclusion into the
openwrt source.
Furthermore, without such a hotplug script, dropbear would listen infinite
on the IP-Address which the WAN interface has at the time dropbear was
started and doesn't rebind to a possible new assigned WAN IP-Address.
I guess the situation is the same for changing IP-Addresses on LAN (new
IPv6 prefix for example) so it should be safe to restart dropbear if any
interface is brought up.
--
Ticket URL: <https://dev.openwrt.org/ticket/19993#comment:1>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
