-
-
Notifications
You must be signed in to change notification settings - Fork 493
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
WireGuard and Lighttpd not working after update to v6.26.3 #3175
Comments
@Joulinar WireGuardThe old module is expected to be removed, since your kernel has been upgraded. But the new module should be build afterwards. LighttpdPlease paste: |
@MichaIng see below as requested WireGuard
looks like
However Lighttpd
|
@Joulinar
|
WireGuard Lighttpd |
@MichaIng sorry I missen to copy Wireguard error messages
As well it seems to be an older version of Wireguard |
Indeed there should be. So since you are on RPi, verify the following: You can test with However, besides running the current WireGuard version makes definitely since (since it is still in heavy development), the actual issue is this:
WireGuard tries to start before the main network interface becomes ready. In case you can either delay the service (e.g. |
So the packages is set to
And yes it's needed to set it to 100 to have it updated by running |
@Joulinar |
@MichaIng |
@MichaIng ok I tried to compare the boot logs between 6.25 and 6.26. For this I reset my DEV system by restoring an 6.25 image (backup from PROD system). Attached the 2 log files. I copied the section between DietPi-Boot boot_6.26.3.txt Next to that, I noticed that WireGuard is updated during 6.26 update process and package Priority is set to Did you already changed something? |
@Joulinar What I will add to
Jep I fixed the patch_file to apply the correct priority now. This simply makes sense, also to have all RPis WireGuard packages migrated to the Raspbian repo, which probably contain some device specific tweaks. |
@MichaIng I set the Attached the 2 logs, with |
@Joulinar What made me think is this part of the log with initial_turbo:
However probably this is intended, e.g. otherwise online target would be never reached if some defined adapter is simply not attached (but another one). But if I understood correctly, the ifup@ services are created via udev rules, so are simply not present for non-attached adapters. But not sure how this is handled exactly from first insight. So regardless of the above, DietPi-Boot does not wait for If you want to check, change that part: https://github.com/MichaIng/DietPi/blob/master/dietpi/boot#L39-L42
Testing a fallback: https://github.com/MichaIng/DietPi/pull/3192/files Finally I think this script we use is generally no good idea but instead network states should be always re-obtained. |
OK i changed the lines within
attached a picture from the screen showing the output during boot. |
@Joulinar To fix it, add the fallback lines to our obtain_network_details script that I linked above. You can revert boot script again then. Result:
|
@MichaIng well done. I adjusted |
@Joulinar |
@MichaIng So probably it's time to setup a fresh install on Buster and migrate all my data from Stretch :) |
@Joulinar |
@MichaIng |
Just to reference here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791920
|
@MichaIng, thx for the fix. |
@sesamzoo |
Required Information
6.26.3
stretch
Linux DietPi_DEV 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
RPi 3 Model B (armv7l)
na
SanDisk Ultra
Additional Information (if applicable)
Wireguard and PiHole
updated from v6.25.3
not tested
Steps to reproduce
Expected behaviour
Actual behaviour
Extra details
I have quite some issues after updating to v6.26.3
I have seen that Wireguard was uninstalled during the update. But it was not reinstalled.
Howerver I see in
journalctl
that the system is still trying to startwg0
during boot.Checking DietPi Software indicates, that Wireguard is still installed.
Question: Do I need to reinstall Wireguard using DietPi Software or is there another way??
+++++++++++++++++++++
May secound issue is with Lighttpd Daemon. It's not coming up after the update.
Checking
journalctl
after reboot is giving the following informationAny idea?
The text was updated successfully, but these errors were encountered: