Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#1286 - Network startup happens too late with kernel 4.14 #6220

Open
openwrt-bot opened this issue Jan 22, 2018 · 0 comments
Open

FS#1286 - Network startup happens too late with kernel 4.14 #6220

openwrt-bot opened this issue Jan 22, 2018 · 0 comments
Labels

Comments

@openwrt-bot
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant