dropbear: fix dropbear startup issue
authorHans Dedecker <dedeckeh@gmail.com>
Tue, 18 Dec 2018 18:40:31 +0000 (19:40 +0100)
committerHans Dedecker <dedeckeh@gmail.com>
Tue, 18 Dec 2018 18:43:22 +0000 (19:43 +0100)
commit83109450ce9119a871efe8efd53b7aa07fecdcac
tree823fd296c351c84ba69c12ad73b7960b5c82d8d6
parent6835c13e5a81a96bd45b016a0013214d4a04286a
dropbear: fix dropbear startup issue

Interface triggers are installed by the dropbear init script in case an
interface is configured for a given dropbear uci section.
As dropbear is started after network the interface trigger event can be
missed during a small window; this is especially the case if lan is
specified as interface.
Fix this by starting dropbear before network so no interface trigger
is missed. As dropbear is started earlier than netifd add a boot function
to avoid the usage of network.sh functions as call to such functions will
fail at boottime.

Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
Acked-by: Jo-Philipp Wich <jo@mein.io>
package/network/services/dropbear/Makefile
package/network/services/dropbear/files/dropbear.init