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

[LEDE Bugs]

The following task has a new comment added:

FS#660 - Dropbear stops working after issuing /etc/init.d/network restart.
User who did this - Marco Vedovati (marcov)

----------
I have about the same dropbear config as Adrian (pub key authentication, listen on 'lan' i/f only) and I have also the same problem connecting after network restart. 

Before /etc/init.d/network restart:
root at LEDE:~# netstat -ltn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:53              0.0.0.0:*               LISTEN
tcp        0      0 10.0.0.1:22             0.0.0.0:*               LISTEN
tcp        0      0 :::80                   :::*                    LISTEN
tcp        0      0 :::53                   :::*                    LISTEN
tcp        0      0 fdb7:f874:89ce::1:22    :::*                    LISTEN

After:
root at LEDE:~# netstat -ltn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:53              0.0.0.0:*               LISTEN
tcp        0      0 :::80                   :::*                    LISTEN
tcp        0      0 :::53                   :::*                    LISTEN



Dropbear command line from 'ps w':

/usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -g -p 10.0.0.1:22 -p dead:b0d1:face::1:22 -K 300


Interestingly enough **if dropbear is invoked from command line** instead of using init.d, then **connection after restart is fine.**
----------

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