[FS#1286] Network startup happens too late with kernel 4.14

LEDE Bugs lede-bugs at lists.infradead.org
Sun Jan 21 16:12:30 PST 2018


A new Flyspray task has been opened.  Details are below. 

User who did this - Andrey Tikhomirov (vampik) 

Attached to Project - OpenWrt/LEDE Project
Summary - Network startup happens too late with kernel 4.14
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - High
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - 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. 


 

One or more files have been attached.

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



More information about the lede-bugs mailing list