mirror of
https://github.com/amnezia-vpn/amneziawg-linux-kernel-module.git
synced 2026-10-14 05:41:56 +00:00
[GH-ISSUE #59] It is possible to connect to AmneziaWG server without properly configured extended parameters #33
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#33
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 @WTFThatPerson on GitHub (Dec 4, 2024).
Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-linux-kernel-module/issues/59
I have my own Ubuntu 22 hosted AmneziaWG server. Kernel ver. 6.8.0-1016-oracle
For some unknown reason, standard Wireguard clent or AmneziaWG client with extended parameters fields unset connects to properly configured AmneziaWG server. I mean, that server is successfully configured with extended parameters set, is up and accessible by properly configured AmneziaWG clients, but it’s accessible using Wireguard/unset AmneziaWG client too. I tried different clients for Wireguard and for AmneziaWG both: for Windows, for Android and for Ubuntu 16, and they show no differences. If opposite case, everything works as expected, i.e. AmneziaWG client with extended field set won’t connect to Wireguard server or AmneziaWG server in Wireguard mode.