[GH-ISSUE #1384] Wireguard interface address is "Network address" #564

New issue

Open

opened 2026-10-13 20:24:11 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-13 20:24:11 +00:00

Owner

Originally created by @pgalonza on GitHub (Jan 29, 2025).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1384

Describe
By default, the Amnezia client creates a WireGuard configuration with the "Address" parameter set to "10.8.1.0" (github.com/amnezia-vpn/amnezia-client@b9ee600fa8/client/protocols/protocols_defs.h (L144)), but the documentation states that this address should be assigned to an interface, as it can cause problems during operation, because it is "Special Addresses"

To Reproduce
Steps to reproduce the behavior:

Install Wireguard
Connect to container
Open wg0.conf

Expected behavior
"Address" parameter set to "10.8.0.1"

Desktop (please complete the following information):

OS: Manjaro

Server (please complete the following information):

OS: Almalinux 9

Additional context
https://git.zx2c4.com/wireguard-tools/about/src/man/wg-quick.8
https://www.ietf.org/rfc/rfc950.txt
https://www.ietf.org/rfc/rfc943.txt

"In certain contexts, it is useful to have fixed addresses
with functional significance rather than as identifiers of
specific hosts. When such usage is called for, the address
zero is to be interpreted as meaning "this", as in "this
network". The address of all ones are to be interpreted as
meaning "all", as in "all hosts". For example, the address
128.9.255.255 could be interpreted as meaning all hosts on
the network 128.9. Or, the address 0.0.0.37 could be
interpreted as meaning host 37 on this network."

 It is useful to preserve and extend the interpretation of these
 special addresses in subnetted networks.  This means the values
 of all zeros and all ones in the subnet field should not be
 assigned to actual (physical) subnets.

https://www.ietf.org/rfc/rfc1878.txt

Originally created by @pgalonza on GitHub (Jan 29, 2025). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1384 **Describe** By default, the Amnezia client creates a WireGuard configuration with the "Address" parameter set to "10.8.1.0" (https://github.com/amnezia-vpn/amnezia-client/blob/b9ee600fa878db65edcb44efb98198a7742b5937/client/protocols/protocols_defs.h#L144), but the documentation states that this address should be assigned to an interface, as it can cause problems during operation, because it is "Special Addresses" **To Reproduce** Steps to reproduce the behavior: 1. Install Wireguard 2. Connect to container 3. Open wg0.conf **Expected behavior** "Address" parameter set to "10.8.0.1" **Desktop (please complete the following information):** - OS: Manjaro **Server (please complete the following information):** - OS: Almalinux 9 **Additional context** https://git.zx2c4.com/wireguard-tools/about/src/man/wg-quick.8 https://www.ietf.org/rfc/rfc950.txt https://www.ietf.org/rfc/rfc943.txt > "In certain contexts, it is useful to have fixed addresses with functional significance rather than as identifiers of specific hosts. When such usage is called for, the address zero is to be interpreted as meaning "this", as in "this network". The address of all ones are to be interpreted as meaning "all", as in "all hosts". For example, the address 128.9.255.255 could be interpreted as meaning all hosts on the network 128.9. Or, the address 0.0.0.37 could be interpreted as meaning host 37 on this network." It is useful to preserve and extend the interpretation of these special addresses in subnetted networks. This means the values of all zeros and all ones in the subnet field should not be assigned to actual (physical) subnets. https://www.ietf.org/rfc/rfc1878.txt

bsakaguchi referenced this issue

2026-10-13 21:16:46 +00:00

[PR #564] [MERGED] Improve pipeline #1921