[GH-ISSUE #53] Stopped working with latest AUR version

bsakaguchi commented

2026-10-13 21:02:29 +00:00

Owner

Originally created by @ksergey on GitHub (Jun 19, 2026).
Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-tools/issues/53

Latest version (1.0.20260618-1) of amneziawg-tools from AUR not working for me.
Downgraded to 1.0.20260223-1

❯ yay -Qm | grep amnezia
amneziawg-dkms 1.0.20260611-1
amneziawg-tools 1.0.20260223-1

Thanks

Originally created by @ksergey on GitHub (Jun 19, 2026). Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-tools/issues/53 Latest version (`1.0.20260618-1`) of `amneziawg-tools` from AUR not working for me. Downgraded to `1.0.20260223-1` ```sh ❯ yay -Qm | grep amnezia amneziawg-dkms 1.0.20260611-1 amneziawg-tools 1.0.20260223-1 ``` Thanks

bsakaguchi commented

2026-10-13 21:02:30 +00:00

Author

Owner

@sokdnv commented on GitHub (Jun 20, 2026):

thanks for the info, had the same issue

@sokdnv commented on GitHub (Jun 20, 2026): thanks for the info, had the same issue

bsakaguchi commented

2026-10-13 21:02:31 +00:00

Author

Owner

@d1mk0 commented on GitHub (Jun 20, 2026):

it seems parser is broken on Address and MTU values. As soon as I commented it, it parses config correctly. If don't comment it, it skips some options and nothing works.
amneziawg-tools v1.0.20260618 - broken.
Previously working version for me is 1.0.20260223-1

UPD:
It seems 07b7a93 fixes the issue. At least v1.0.20260618-2 works fine for me.

As w/a AUR user may slightly change PKGBUILD:

--- ./PKGBUILD  2026-06-20 19:04:56.190065855 +0300
+++ ../../amneziawg-tools/PKGBUILD      2026-06-20 18:58:53.705676548 +0300
@@ -5,20 +5,20 @@
 url="https://github.com/amnezia-vpn/amneziawg-tools"
 arch=("x86_64")
 pkgver=1.0.20260618
-pkgrel=1
+pkgrel=2
 license=('GPL-2.0')
 depends=('bash')
 optdepends=('amneziawg-go: go implementation of amneziawg'
             'resolvconf: if you are controling DNS via AmneziaWG')
-source=("$pkgname-$pkgver.tar.gz::https://github.com/amnezia-vpn/amneziawg-tools/archive/refs/tags/v${pkgver}.tar.gz")
-sha512sums=('b4e74e2427cec827ea2349cf972ee24a2e7457df5a19b6b5129ed34f48a2481648d36fa915e00fc31a89930b1b9de18a032dd1431f8d51576e4a001a8cebe76d')
+source=("$pkgname-$pkgver-2.tar.gz::https://github.com/amnezia-vpn/amneziawg-tools/archive/refs/tags/v${pkgver}-2.tar.gz")
+sha512sums=('5f75260e9de307b1e20f403b5acaf044e0930557adfc1556d9fa04f96e776d73be261658d9aee21aec518c09fa98d4405ef663c8eb908ea76c84d184bf77ec53')
 
 build(){
-       cd ${pkgname}-${pkgver}/src
+       cd ${pkgname}-${pkgver}-2/src
        make
 }
 
 package() {
-       cd ${pkgname}-${pkgver}/src
+       cd ${pkgname}-${pkgver}-2/src
        make DESTDIR="$pkgdir/" install
 }

@d1mk0 commented on GitHub (Jun 20, 2026): it seems parser is broken on Address and MTU values. As soon as I commented it, it parses config correctly. If don't comment it, it skips some options and nothing works. amneziawg-tools v1.0.20260618 - broken. Previously working version for me is 1.0.20260223-1 UPD: It seems 07b7a93 fixes the issue. At least v1.0.20260618-2 works fine for me. As w/a AUR user may slightly change PKGBUILD: ``` --- ./PKGBUILD 2026-06-20 19:04:56.190065855 +0300 +++ ../../amneziawg-tools/PKGBUILD 2026-06-20 18:58:53.705676548 +0300 @@ -5,20 +5,20 @@ url="https://github.com/amnezia-vpn/amneziawg-tools" arch=("x86_64") pkgver=1.0.20260618 -pkgrel=1 +pkgrel=2 license=('GPL-2.0') depends=('bash') optdepends=('amneziawg-go: go implementation of amneziawg' 'resolvconf: if you are controling DNS via AmneziaWG') -source=("$pkgname-$pkgver.tar.gz::https://github.com/amnezia-vpn/amneziawg-tools/archive/refs/tags/v${pkgver}.tar.gz") -sha512sums=('b4e74e2427cec827ea2349cf972ee24a2e7457df5a19b6b5129ed34f48a2481648d36fa915e00fc31a89930b1b9de18a032dd1431f8d51576e4a001a8cebe76d') +source=("$pkgname-$pkgver-2.tar.gz::https://github.com/amnezia-vpn/amneziawg-tools/archive/refs/tags/v${pkgver}-2.tar.gz") +sha512sums=('5f75260e9de307b1e20f403b5acaf044e0930557adfc1556d9fa04f96e776d73be261658d9aee21aec518c09fa98d4405ef663c8eb908ea76c84d184bf77ec53') build(){ - cd ${pkgname}-${pkgver}/src + cd ${pkgname}-${pkgver}-2/src make } package() { - cd ${pkgname}-${pkgver}/src + cd ${pkgname}-${pkgver}-2/src make DESTDIR="$pkgdir/" install } ```

bsakaguchi commented

2026-10-13 21:02:31 +00:00

Author

Owner

@Afmer commented on GitHub (Jun 25, 2026):

I can confirm this issue. I experienced the exact same problem on Arch Linux. Downgrading amneziawg-tools fixes it immediately.

Environment:

Client OS: Arch Linux
Server: wg-easy version 15.3.0
Broken version: amneziawg-tools 1.0.20260618-1 (from AUR)
Working version: amneziawg-tools 1.0.20260223-1 (from AUR)

Symptoms:
When using the broken version, running awg-quick up creates the interface without any syntax errors, but the connection suffers from 100% packet loss (0 bytes received). The handshake never completes.

The core issue seems to be a regression in how the configuration parser reads or applies obfuscation parameters. When running sudo awg show with the broken version, some of the Magic Header parameters (specifically h1 and h2) are completely missing from the output, even though they are explicitly defined in the client's .conf file.

Because h1 and h2 are missing, the client sends packets with incorrect headers, and the server silently drops them (which is the expected behavior for unmatched obfuscation parameters, but it's caused by the client ignoring the config).

Troubleshooting performed:
To rule out other causes, I tested the following:

It is not a kernel module issue. The exact same silent handshake failure occurs when using the userspace implementation (amneziawg-go).
It is not a network or ISP blocking issue. Connecting from a mobile device on the exact same Wi-Fi network works perfectly.
Downgrading only amneziawg-tools to 1.0.20260223-1 (while keeping the latest kernel and amneziawg-dkms) instantly restored the handshake and fixed the connection without changing a single line in the config file.

Hope this information helps locate the regression in the parser!

@Afmer commented on GitHub (Jun 25, 2026): I can confirm this issue. I experienced the exact same problem on Arch Linux. Downgrading `amneziawg-tools` fixes it immediately. **Environment:** * **Client OS:** Arch Linux * **Server:** `wg-easy` version 15.3.0 * **Broken version:** `amneziawg-tools` 1.0.20260618-1 (from AUR) * **Working version:** `amneziawg-tools` 1.0.20260223-1 (from AUR) **Symptoms:** When using the broken version, running `awg-quick up` creates the interface without any syntax errors, but the connection suffers from 100% packet loss (0 bytes received). The handshake never completes. The core issue seems to be a regression in how the configuration parser reads or applies obfuscation parameters. When running `sudo awg show` with the broken version, some of the Magic Header parameters (specifically `h1` and `h2`) are **completely missing** from the output, even though they are explicitly defined in the client's `.conf` file. Because `h1` and `h2` are missing, the client sends packets with incorrect headers, and the server silently drops them (which is the expected behavior for unmatched obfuscation parameters, but it's caused by the client ignoring the config). **Troubleshooting performed:** To rule out other causes, I tested the following: 1. It is **not** a kernel module issue. The exact same silent handshake failure occurs when using the userspace implementation (`amneziawg-go`). 2. It is **not** a network or ISP blocking issue. Connecting from a mobile device on the exact same Wi-Fi network works perfectly. 3. Downgrading **only** `amneziawg-tools` to `1.0.20260223-1` (while keeping the latest kernel and `amneziawg-dkms`) instantly restored the handshake and fixed the connection without changing a single line in the config file. Hope this information helps locate the regression in the parser!

bsakaguchi commented

2026-10-13 21:02:31 +00:00

Author

Owner

@orange-banal-pole commented on GitHub (Jun 26, 2026):

Why would you report this here? Report it to the maintainer of the AUR package. The Amnezia Team has nothing to do with Arch Linux. They only provide official Ubuntu packages.

Anyway, this issue has been already fixed in 1.0.20260618-2.

@orange-banal-pole commented on GitHub (Jun 26, 2026): Why would you report this here? Report it to the maintainer of the AUR package. The Amnezia Team has nothing to do with Arch Linux. They only provide official Ubuntu packages. Anyway, this issue has been already fixed in 1.0.20260618-2.

bsakaguchi commented

2026-10-13 21:02:31 +00:00

Author

Owner

@gentoosys commented on GitHub (Jul 2, 2026):

this issue persist in official arch packages too, version there is still *-1. only amneziawg-tools-git package work. can you bump version to new date for faster update?

@gentoosys commented on GitHub (Jul 2, 2026): this issue persist in official arch packages too, version there is still *-1. only amneziawg-tools-git package work. can you bump version to new date for faster update?

bsakaguchi commented

2026-10-13 21:02:31 +00:00

Author

Owner

@Afmer commented on GitHub (Jul 6, 2026):

The problem was discussed here and resolved. https://github.com/amnezia-vpn/amneziawg-tools/issues/51

@Afmer commented on GitHub (Jul 6, 2026): The problem was discussed here and resolved. https://github.com/amnezia-vpn/amneziawg-tools/issues/51

Rows
Columns

[GH-ISSUE #53] Stopped working with latest AUR version #23