Wireguard issue

bertaga

Hello everyone,
I am trying to use wireguard on Solus.
As I understood, there is no need to install the module since the Solus is currently on Linux56.
I manually installed wireguard-tools from the sources but when I run wg-quick up plop I get a Failed to set DNS configuration: Unit dbus-org.freedesktop.resolve1.service not found.
How can I fix this?

brent

bertaga from the sources

pretty vague. Nonetheless there is this in solus:
snap find wireguard Name Version Publisher Notes Summary wireguard-ammp 0.0.20181218 ammp - WireGuard VPN (userspace)
if you do snap I'd rip out all the stuff you tried to install, first.
but
if you did install the snap package, and getting these errors, then I don't know.

appmath

bertaga If you have a DNS entry in your client conf file, remove it. I had the same problem as you and that seemed to be the consensus solution. After that wg-quick seemed to set up everything (including firewall changes).
Of course I haven't actually got wireguard to work with my OpenBSD VPS quite yet, so take my advice with a grain of salt...

trulyclaw74

appmath Doesn't this open up security issues, such as DNS leaks? I have the same problem and do not want to use systemd-resolved; does Solus use their default 8.8.8.8 for DNS queries? That is my concern with enabling systemd-resolved.

I tried wireguard in Void and Artix (and Windows, of course) and did not have an issue, but systemd does not like when systemd-resloved is not running :/

spacepig

Hi Solus community!
1.post 😁
-> I had the same issue as bertaga, meaning that the resolve1.service was not found, the simple solution is to enable sytemd's resolved.service:

sudo systemctl start systemd-resolved.service
sudo systemctl enable systemd-resolved.service

Then try to wg-quick up...
Maybe this is helpful information.

PS: Unfortunately Snap did not help as it produced some errors. I have not tried to remove the dns entries in my wg-config as appmath suggested, this might help, not sure though...

DataDrake

trulyclaw74 8.8.8.8 is a fallback not the default. It will only get used if your NIC can't negotiate for a nameserver over DHCP or if the negotiated nameserver can't be contacted. This should never happen if the network you are connected to is configured correctly and operating normally.

trulyclaw74

I enabled systemd-resolved with:
systemctl start systemd-resolved.service
and wireguard started, but the DNS did not work. I was able to ping 8.8.8.8 but could not reach google, amazon or any other website by name.

I guess that "fallback" = "default" to me; that means it's hard coded into systemd-resolved at compile and goes there when systemd-resolved figures that it needs to do so; I may run a wireshark to see if it ever contacts 8.8.8.8 with and without just for comfort level

DataDrake

trulyclaw74 If it were default, then it would be the first server that it tries. You can actually configure it that way and override the DHCP provided nameservers.