Comment 3 for bug 1992491

Revision history for this message
Martin Vysny (vyzivus) wrote :

Hello, thank you so much for your response and for your kind investigation!

The issue gets really weird. I have two laptops, both upgraded to Ubuntu 22.10; wg-quick works on one while fails on another. On both devices I can see that resolv.conf is a symlink:

~> ls -la /etc/resolv.conf
lrwxrwxrwx 1 root root 39 loka 11 19:52 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

The systemd-resolved is running correctly on both laptops:

~> systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
     Active: active (running) since Fri 2022-10-14 08:33:22 EEST; 6min ago

Both laptops are running the original kernel from Ubuntu - I haven't compiled kernel from sources in ages :-) . Both laptops have been upgraded from Ubuntu 22.04, however the upgrade was performed at different times. Both machines are running 5.19.0-19-generic kernel.

I just noticed a difference though: one laptop reports that there is a residual config for resolvconf. Let me try to purge the config & reboot.