-
-
Notifications
You must be signed in to change notification settings - Fork 4k
WireGuard connection does not resume after sleep #26665
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
Comments
At first glance, the difference between 252 and 253 system logs is that 253 shows:
|
The log and your comment in the above suggest that you do not use networkd to manage the WireGuard interface, that is, you have no .network or .netdev file for the WireGuard interface. Right? (If so, I guess this is not a bug in networkd, but you also said downgrading systemd to v252 fixes the issue. hmm...) Could you enable to generate debugging logs of networkd by creating the following drop-in:
then, please provide the generated logs. |
Thats was the reason, I reported this to systemd. At first I also thought that the problem was something else. But systemd downgrade solved this problem.
Yes, this is intentional to separate handling of wireguard from systemd-networkd. This allows me to easily toggle the wireguard on and off. |
Still not sure why it does not work, but should be caused by a39a9ac... |
Ah, maybe this one.
I guess, wg service creates routing policy rules, and networkd removes them on after sleep. That should also happen when simply calling So, please use |
Let's close this, at least tentatively, as there is nothing we can do. @andruska Feel free to request to reopen this if |
Works, thanks ! |
Hello. I have a similar problem and I edited the networkd.conf file, but it didn't help. After waking up from sleep mode, I still have to reconnect the VPN. Are there any other tips for fixing this? |
Uh oh!
There was an error while loading. Please reload this page.
systemd version the issue has been seen with
253
Used distribution
Archlinux
Linux kernel version used
6.0.8, 6.1.12, 6.2.1
CPU architectures issue was seen on
x86_64
Component
other
Expected behaviour you didn't see
No response
Unexpected behaviour you saw
After upgrading
systemd
from 252 to 253Wireguard
stopped resuming from sleep (suspend, hibernation) cycle.journalctl -u wg-quick@profile.service
shows exactly same state as it was before sleep.I get
Wireguard
back restartingwg-quick
service bysystemctl restart wg-quick@profile.service
.For networking i use
systemd-networkd
,systemd-resolved
,iwd
,wg-quick
.Tested with kernels 6.0.8, 6.1.12, 6.2.1.
Downgrading to 252 Wireguard works again as expected.
Steps to reproduce the problem
Configurations:
Additional program output to the terminal or log subsystem illustrating the issue
The text was updated successfully, but these errors were encountered: