[FS#660] Dropbear stops working after issuing /etc/init.d/network restart.

LEDE Bugs lede-bugs at lists.infradead.org
Sun May 14 05:25:53 PDT 2017


The following task has a new comment added:

FS#660 - Dropbear stops working after issuing /etc/init.d/network restart.
User who did this - Yousong Zhou (yousong)

----------
I also cannot reproduce this with LEDE-17.01 on HC6361 (ar71xx) and current HEAD of lede-17.01 branch on malta.

To debug this further, please consider opening another simple dropbear instance which will not be affected by the network restart action so that you can login and check the scene.

A few lines of snippet that may help


. /lib/functions/procd.sh
procd_open_service dbtest
procd_open_instance
procd_set_param command /usr/sbin/dropbear -F -p 2222
procd_set_param respawn 3600 5 0
procd_close_instance
procd_close_service

ubus call service list '{"name": "dbtest", "verbose": true }'
ubus call service list '{"name": "dropbear", "verbose": true }'
ubus call service delete '{"name": "dbtest" }'



----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=660#comment2625



More information about the lede-bugs mailing list