Package Details: amneziawg-tools 1.0.20250903-1

Git Clone URL: https://aur.archlinux.org/amneziawg-tools.git (read-only, click to copy)
Package Base: amneziawg-tools
Description: AmneziaWG is a contemporary version of the popular VPN protocol, WireGuard.
Upstream URL: https://github.com/amnezia-vpn/amneziawg-tools
Licenses: GPL-2.0
Submitter: VVL
Maintainer: VVL
Last Packager: VVL
Votes: 10
Popularity: 0.196359
First Submitted: 2024-06-04 16:08 (UTC)
Last Updated: 2025-09-03 14:28 (UTC)

Dependencies (3)

Required by (2)

Sources (1)

Latest Comments

1 2 3 Next › Last »

e_Irbis commented on 2025-09-13 08:50 (UTC) (edited on 2025-09-13 09:34 (UTC) by e_Irbis)

Did anyone receive a similar mistake?

==> Build () ... 
 LD   wg
Collect2: Fatal Error: Cannot Find "ld"
The compilation is interrupted.
Make: *** [<built -in>: wg] error 1
==> Error: There was a failure in Build (). 
    Interrupt...

UPD I was found a problem LDFLAGS in makepkg.cfg contains the -fuse-ld=mold flag, but the mold package was not installed on the system.

marek22k commented on 2025-09-06 19:29 (UTC)

Is AWG 2.0 config compatible with the vanilla parameters and with the Wireguard servers themselves? Jc, Jmin, Jmax, S1-2, H1-4...

I'm struggling to understand Amnezia's documentation. It vaguely claims to be Wireguard compatible even with the 1.5 release, but that's simply not true AFAIK.

Unfortunately, the documentation does not provide detailed information about the parameters. Zane (developer of WG Tunnel) has provided a configuration that is backward compatible with Vanilla WireGuard: https://zaneschepke.com/wgtunnel-docs/features.html#how-to-convert-an-existing-wireguard-config-to-amnezia

Alternatively - self-promotion - I have also written about AmneziaWG and the meaning of the parameters on my website. https://mk16.de/blog/amneziawg-en/

wilkins commented on 2025-09-06 14:22 (UTC)

I was asking whether this update broke compatibility with the previous amnezia release, i.e with the 1.5 awg params

VVL commented on 2025-09-05 18:46 (UTC)

If you're not using awg params (Jc, Jmin, Jmax, S1-2, H1-4...), then it support vanilla wireguard. If you start using it, then you're using awg.

wilkins commented on 2025-09-02 09:46 (UTC)

1.0.20250901

Is AWG 2.0 config compatible with the vanilla parameters and with the Wireguard servers themselves? Jc, Jmin, Jmax, S1-2, H1-4...

I'm struggling to understand Amnezia's documentation. It vaguely claims to be Wireguard compatible even with the 1.5 release, but that's simply not true AFAIK.

And why did they update amnezia-tools to 2.0 when amnezia-go (f6542209f40f3f8f9e3dc9403d331ad2881fd7e3) is still untagged?

basul commented on 2025-07-12 13:27 (UTC)

Yea, it looks like the latest changes were reverted in 1.0.20250706 since they were causing issues. Upgraded to that version and "Invalid argument" error is gone.

Arsikk commented on 2025-07-06 03:12 (UTC)

Seems like 1.0.20250704-1 breaks awg-quick? My known good config broke after this with unable to resolve IP address and invalid argument errors, downgrading solved it.

Gallifreyan commented on 2025-01-14 04:54 (UTC)

I'm not sure whether this should go here or elsewhere, but it appears that updating the kernel breaks this package - trying the awg-quick command complains about an unknown connection type, which is only solved by reinstalling this package and amneziawg-linux. Maybe add a pacman hook to reinstall this package after a kernel update?

marek22k commented on 2024-09-02 20:09 (UTC)

@VVL Thanks for the quick fix!

marek22k commented on 2024-09-02 19:13 (UTC) (edited on 2024-09-02 19:14 (UTC) by marek22k)

@VVL resolvconf should be optional, as it is not necessary if you do not control the DNS via Amnezia! (After settings it to optional please increase pkgrel again)

1 2 3 Next › Last »