mirror of
https://github.com/amnezia-vpn/amneziawg-linux-kernel-module.git
synced 2026-10-14 05:41:56 +00:00
[GH-ISSUE #132] Latest master fails to establish connection between two peers: Invalid handshake initiation from #83
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
amnezia-vpn/amneziawg-linux-kernel-module#83
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @abashurov on GitHub (Jan 7, 2026).
Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-linux-kernel-module/issues/132
Server A configuration:
Debian 13 6.12.57+deb13-amd64
Kernel module built from tip of the master (problem reproduces using the packages from the PPA as well)
awg1.conf:
dmesg:
Server B configuration:
Debian 13, 6.12.57+deb13-amd64
Kernel module built from tip of the master (problem reproduces using the packages from the PPA as well)
awg0.conf:dmesg from server B:
@abashurov commented on GitHub (Jan 7, 2026):
This does look like the problem that was present in #88, however, as I can see, the from that issue is merged into master.
Unfortunately, I could not bisect the problem, as it is persistent throughout all the commits in master within the last 2 years.
UPD Problem does not reproduce when running on Ubuntu 24.04 with 6.8.0-90-generic kernel
@h1de0x commented on GitHub (Jan 9, 2026):
This may seem strange, but could you try changing the jmin parameter to 10 and jmax to 80?
@ygurov commented on GitHub (Jan 10, 2026):
Hi
As from configuration, you have
for the 1st device
And
for the 2nd one.
So 1st dev is able to transfer correct initial message, and 2nd dev recognizes it and responds with invalid handshake response, which 1st dev cannot handle properly
Please try to use the same padding sizes from both sides, that should resolve the issue