You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've built 2 versions - one with default kernel 4.9 and another one with kernel 4.14.
The version with kernel 4.9 works fine. Netifd sets up network interfaces, after that another daemons are started.
The version with kernel 4.14 does not work as expected. Another daemons are started before network interface setup. In my case, this prevents the VPN server from working correctly. I have to manually restart VPN service after every reboot. This may potentially affect another software.
I have attached the log files. Please note the startup order as found in the log files:
vampik:
Software version: r5917-36f1978a70-x86-64, device: x86-64 PC.
I've built 2 versions - one with default kernel 4.9 and another one with kernel 4.14.
The version with kernel 4.9 works fine. Netifd sets up network interfaces, after that another daemons are started.
The version with kernel 4.14 does not work as expected. Another daemons are started before network interface setup. In my case, this prevents the VPN server from working correctly. I have to manually restart VPN service after every reboot. This may potentially affect another software.
I have attached the log files. Please note the startup order as found in the log files:
kernel 4.9: netifd interface setup -> block -> dropbear -> xl2tpd -> openvpn
kernel 4.14: block -> dropbear -> xl2tpd -> openvpn -> netifd interface setup
I have no idea how a kernel version may affect the startup order. Maybe there is a kind of race condition.
The text was updated successfully, but these errors were encountered: