Nasheayahu 2 Posted ... Not sure if I'm following the instructions correctly for using wireguard on Centos Stream 10 or missing some on the OS itself. The steps taken: 1) sudo dnf config-manager --set-enabled crb 2) sudo dnf install epel-release epel-next-release I don't believe these stops has nothing to do with wireguard, but 3) sudo dnf install wireguard-tools 4) on Config Generator By continents I selected: America 5) sudo wg-quick up /home/nasheayahu/Downloads/wg.conf and I get this output: Warning: `/home/nasheayahu/Downloads/wg.conf' is world accessible [#] ip link add wg type wireguard [#] wg setconf wg /dev/fd/63 [#] ip -4 address add 10.174.198.92/32 dev wg [#] ip -6 address add fd7d:76ee:e68f:a993:13df:1b75:c79c:fcbb/128 dev wg [#] ip link set mtu 1320 up dev wg [#] resolvconf -a wg -m 0 -x Failed to set DNS configuration: Could not activate remote peer 'org.freedesktop.resolve1': activation request failed: unknown unit [#] ip link delete dev wg What else do I need to do to get this working? Quote Share this post Link to post
reversevpn 9 Posted ... Try copying the file to /etc/wireguard and doing sudo systemctl start wg-quick@wg . This should bypass freedesktop and enable you to raise the interface. You can replace "wg" in systemctl start wg-quick@wg with whatever name your config file is. I use wg because your file is named wg.conf, but I do recommend renaming it after the airvpn server you are using, or some other nickname you have for it, like america. So, try copying it as america.conf into /etc/wireguard, then doing systemctl start wg-quick@america. If it fails, do systemctl status wg-quick@america and show the logs here 1 Nasheayahu reacted to this Quote Share this post Link to post
reversevpn 9 Posted ... If the above failed, try installing systemd-resolved using sudo dnf install systemd-resolved, then try raising the interface using the systemctl method again 1 Nasheayahu reacted to this Quote Share this post Link to post
Nasheayahu 2 Posted ... 8 hours ago, reversevpn said: If it fails, do systemctl status wg-quick@america and show the logs here This is what I get from journalctl -xeu wg-quick@America.service: sudo systemctl start wg-quick@America Job for wg-quick@America.service failed because the control process exited with error code. See "systemctl status wg-quick@America.service" and "journalctl -xeu wg-quick@America.service" for details. journalctl -xeu wg-quick@America.service ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit wg-quick@America.service has begun execution. ░░ ░░ The job identifier is 9466. Sep 04 16:41:32 lab-idm wg-quick[16323]: [#] ip link add America type wireguard Sep 04 16:41:32 lab-idm wg-quick[16323]: [#] wg setconf America /dev/fd/63 Sep 04 16:41:33 lab-idm wg-quick[16323]: [#] ip -4 address add 10.174.198.92/32 dev America Sep 04 16:41:33 lab-idm wg-quick[16323]: [#] ip -6 address add fd7d:76ee:e68f:a993:13df:1b75:c79c:fcbb/128 dev America Sep 04 16:41:33 lab-idm wg-quick[16323]: [#] ip link set mtu 1320 up dev America Sep 04 16:41:33 lab-idm wg-quick[16356]: [#] resolvconf -a America -m 0 -x Sep 04 16:41:33 lab-idm resolvconf[16358]: Failed to set DNS configuration: Could not activate remote peer 'org.freedesktop.resolve1': activation request failed: unknown unit Sep 04 16:41:33 lab-idm wg-quick[16323]: [#] ip link delete dev America Sep 04 16:41:33 lab-idm systemd[1]: wg-quick@America.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ An ExecStart= process belonging to unit wg-quick@America.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Sep 04 16:41:33 lab-idm systemd[1]: wg-quick@America.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit wg-quick@America.service has entered the 'failed' state with result 'exit-code'. Sep 04 16:41:33 lab-idm systemd[1]: Failed to start wg-quick@America.service - WireGuard via wg-quick(8) for America. ░░ Subject: A start job for unit wg-quick@America.service has failed ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit wg-quick@America.service has finished with a failure. ░░ ░░ The job identifier is 9466 and the job result is failed. and from the status: × wg-quick@America.service - WireGuard via wg-quick(8) for America Loaded: loaded (/usr/lib/systemd/system/wg-quick@.service; disabled; preset: disabled) Active: failed (Result: exit-code) since Thu 2025-09-04 16:41:33 MDT; 4min 24s ago Invocation: 59de1a1251b343629c1bc5d854920a36 Docs: man:wg-quick(8) man:wg(8) https://www.wireguard.com/ https://www.wireguard.com/quickstart/ https://git.zx2c4.com/wireguard-tools/about/src/man/wg-quick.8 https://git.zx2c4.com/wireguard-tools/about/src/man/wg.8 Process: 16323 ExecStart=/usr/bin/wg-quick up America (code=exited, status=1/FAILURE) Main PID: 16323 (code=exited, status=1/FAILURE) Mem peak: 3.4M CPU: 24ms Sep 04 16:41:32 lab-idm wg-quick[16323]: [#] wg setconf America /dev/fd/63 Sep 04 16:41:33 lab-idm wg-quick[16323]: [#] ip -4 address add 10.174.198.92/32 dev America Sep 04 16:41:33 lab-idm wg-quick[16323]: [#] ip -6 address add fd7d:76ee:e68f:a993:13df:1b75:c79c:fcbb/128 dev America Sep 04 16:41:33 lab-idm wg-quick[16323]: [#] ip link set mtu 1320 up dev America Sep 04 16:41:33 lab-idm wg-quick[16356]: [#] resolvconf -a America -m 0 -x Sep 04 16:41:33 lab-idm resolvconf[16358]: Failed to set DNS configuration: Could not activate remote peer 'org.freedesktop.resolve1': activation request failed: unknown unit Sep 04 16:41:33 lab-idm wg-quick[16323]: [#] ip link delete dev America Sep 04 16:41:33 lab-idm systemd[1]: wg-quick@America.service: Main process exited, code=exited, status=1/FAILURE Sep 04 16:41:33 lab-idm systemd[1]: wg-quick@America.service: Failed with result 'exit-code'. Sep 04 16:41:33 lab-idm systemd[1]: Failed to start wg-quick@America.service - WireGuard via wg-quick(8) for America. Quote Share this post Link to post
reversevpn 9 Posted ... Did you install systemd-resolved yet? If not, do so and try again. If you already have, then just erase the DNS= line from the America.conf file, and manually change /etc/resolv.conf to 10.128.0.1 after the America interface has been raised if you wish to use airvpn's DNS. Alternatively, if you have your own DNS server like dnsmasq and want it to query airvpn's DNS, edit /etc/dnsmasq.conf and add a server=10.128.0.1 directive to it. Quote Share this post Link to post
reversevpn 9 Posted ... It's also possible that systemd-resolved is installed but not enabled. Try sudo systemctl enable --now systemd-resolved before taking the DNS directive from the wireguard file. Source: https://bugzilla.redhat.com/show_bug.cgi?id=1732487 1 Nasheayahu reacted to this Quote Share this post Link to post
Nasheayahu 2 Posted ... 28 minutes ago, reversevpn said: Did you install systemd-resolved yet? Ooops, be right back..... Quote Share this post Link to post
Nasheayahu 2 Posted ... 1 hour ago, reversevpn said: It's also possible that systemd-resolved is installed but not enabled. That was it, up and running. 😂 Thanks for your help!... Quote Share this post Link to post
Staff 10297 Posted ... 10 hours ago, Nasheayahu said: That was it, up and running. 😂 Thanks for your help!... Hello! Have you tested the AirVPN Suite for Linux? It should behave properly when systemd-resolved is installed but disabled, because for DNS management it does not invoke resolvconf (needed by WireGuard for this purpose). Kind regards 1 Nasheayahu reacted to this Quote Share this post Link to post
Nasheayahu 2 Posted ... On 9/5/2025 at 3:51 AM, Staff said: Have you tested the AirVPN Suite for Linux? Evening, not yet, it sounds good that it can run without systemd-resolved, so I will give it a go.... Thanks!.... Quote Share this post Link to post