[GH-ISSUE #95] 0.2.12-1 => 0.2.15-1 regression #51

New issue

Open

opened 2026-10-13 21:03:05 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-13 21:03:05 +00:00

Owner

Originally created by @p5n on GitHub (Sep 25, 2025).
Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-go/issues/95

After server update it started drop or damage packets. I can reproduce it by pacman -Syu from msys2 which fails to connect

error: failed retrieving file 'clangarm64.db' from mirror.msys2.org : Connection timed out after 10016 milliseconds
error: failed retrieving file 'mingw32.db' from mirror.msys2.org : Connection timed out after 10011 milliseconds
error: failed retrieving file 'mingw64.db' from mirror.msys2.org : Connection timed out after 10010 milliseconds
warning: too many errors from mirror.msys2.org, skipping for the remainder of this transaction
error: failed retrieving file 'ucrt64.db' from mirror.msys2.org : Connection timed out after 10009 milliseconds
error: failed retrieving file 'clang64.db' from mirror.msys2.org : Connection timed out after 10008 milliseconds
error: failed retrieving file 'clangarm64.db' from repo.msys2.org : Connection timed out after 10004 milliseconds
error: failed retrieving file 'mingw32.db' from repo.msys2.org : Connection timed out after 10000 milliseconds
error: failed retrieving file 'mingw64.db' from repo.msys2.org : Connection timed out after 10013 milliseconds
warning: too many errors from repo.msys2.org, skipping for the remainder of this transaction
error: failed retrieving file 'ucrt64.db' from repo.msys2.org : Connection timed out after 10010 milliseconds
error: failed retrieving file 'clang64.db' from repo.msys2.org : Connection timed out after 10007 milliseconds

other people has other random connectivity issues.

Wireshark shows

79	12.029559	10.193.16.11	88.99.69.85	TCP	60	[TCP Previous segment not captured] 62075 → 443 [FIN, ACK] Seq=1568 Ack=1 Win=65280 Len=0
92	12.083699	88.99.69.85	10.193.16.11	TCP	72	[TCP Dup ACK 38#1] 443 → 62075 [ACK] Seq=1 Ack=1381 Win=67200 Len=0 SLE=1568 SRE=1569
225	27.441139	10.193.16.11	88.99.69.85	TCP	60	62075 → 443 [RST, ACK] Seq=1569 Ack=1 Win=0 Len=0

Downgrading server back to 0.2.12 fixes it

Despite of randomness of connectivity issues it reproduces well, upgrading to 0.2.15 again causes connection timeouts.

Server is latest Archlinux with https://aur.archlinux.org/packages/amneziawg-go

Will try to bisect exact broken version later.

Originally created by @p5n on GitHub (Sep 25, 2025). Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-go/issues/95 After server update it started drop or damage packets. I can reproduce it by `pacman -Syu` from msys2 which fails to connect ``` error: failed retrieving file 'clangarm64.db' from mirror.msys2.org : Connection timed out after 10016 milliseconds error: failed retrieving file 'mingw32.db' from mirror.msys2.org : Connection timed out after 10011 milliseconds error: failed retrieving file 'mingw64.db' from mirror.msys2.org : Connection timed out after 10010 milliseconds warning: too many errors from mirror.msys2.org, skipping for the remainder of this transaction error: failed retrieving file 'ucrt64.db' from mirror.msys2.org : Connection timed out after 10009 milliseconds error: failed retrieving file 'clang64.db' from mirror.msys2.org : Connection timed out after 10008 milliseconds error: failed retrieving file 'clangarm64.db' from repo.msys2.org : Connection timed out after 10004 milliseconds error: failed retrieving file 'mingw32.db' from repo.msys2.org : Connection timed out after 10000 milliseconds error: failed retrieving file 'mingw64.db' from repo.msys2.org : Connection timed out after 10013 milliseconds warning: too many errors from repo.msys2.org, skipping for the remainder of this transaction error: failed retrieving file 'ucrt64.db' from repo.msys2.org : Connection timed out after 10010 milliseconds error: failed retrieving file 'clang64.db' from repo.msys2.org : Connection timed out after 10007 milliseconds ``` other people has other random connectivity issues. Wireshark shows ``` 79 12.029559 10.193.16.11 88.99.69.85 TCP 60 [TCP Previous segment not captured] 62075 → 443 [FIN, ACK] Seq=1568 Ack=1 Win=65280 Len=0 92 12.083699 88.99.69.85 10.193.16.11 TCP 72 [TCP Dup ACK 38#1] 443 → 62075 [ACK] Seq=1 Ack=1381 Win=67200 Len=0 SLE=1568 SRE=1569 225 27.441139 10.193.16.11 88.99.69.85 TCP 60 62075 → 443 [RST, ACK] Seq=1569 Ack=1 Win=0 Len=0 ``` Downgrading server back to 0.2.12 fixes it Despite of randomness of connectivity issues it reproduces well, upgrading to 0.2.15 again causes connection timeouts. Server is latest Archlinux with https://aur.archlinux.org/packages/amneziawg-go Will try to bisect exact broken version later.

bsakaguchi commented

2026-10-13 21:03:06 +00:00

Author

Owner

@ygurov commented on GitHub (Sep 29, 2025):

Hi
Thanks for reporting the issue. Could you provide configuration files used for the connection?

@ygurov commented on GitHub (Sep 29, 2025): Hi Thanks for reporting the issue. Could you provide configuration files used for the connection?

bsakaguchi commented

2026-10-13 21:03:06 +00:00

Author

Owner

@p5n commented on GitHub (Sep 30, 2025):

[Interface]
PrivateKey = ******************************=
Jc = 2
Jmin = 10
Jmax = 50
S1 = 124
S2 = 234
H1 = 138982452
H2 = 5659577
H3 = 802121442
H4 = 316103950

[Peer]
PublicKey = *************************=
AllowedIPs = 0.0.0.0/0
Endpoint = AAAAA.BBB.CCC:XXXXX

@p5n commented on GitHub (Sep 30, 2025): ``` [Interface] PrivateKey = ******************************= Jc = 2 Jmin = 10 Jmax = 50 S1 = 124 S2 = 234 H1 = 138982452 H2 = 5659577 H3 = 802121442 H4 = 316103950 [Peer] PublicKey = *************************= AllowedIPs = 0.0.0.0/0 Endpoint = AAAAA.BBB.CCC:XXXXX ```

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

amnezia-vpn/amneziawg-go#51

No description provided.

Rows
Columns