mirror of
https://github.com/amnezia-vpn/amneziawg-linux-kernel-module.git
synced 2026-10-14 05:41:56 +00:00
[GH-ISSUE #131] It listening on a random port; Why? #81
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#81
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 @lucker999 on GitHub (Jan 1, 2026).
Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-linux-kernel-module/issues/131
Hi there,
I installed the module on a debian server to test it as a client for wireguards, and noticed that it's listening to on a random port (a new port after restart). Could you please briefly explain why it's listening and how to disable this?
Thanks.
@ygurov commented on GitHub (Jan 7, 2026):
Hi
That's the wireguard original feature, when device is being initialized its port is being set to 0. So it picks any available port on a startup.
I agreed it could be confusing, but it is as it is.
Do you think it's a potential hole/fingerprint/etc for AWG protocol?