Wireguard AllowedIPs config option removed for first peer when adding more than one peer
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
When wireguard is configured with one peer, all works as expected. However, when a second peer is added the AllowedIPs config option of the first peer is removed, rendering the peer unable to send/receive traffic.
The config is correctly displayed in the LuCI GUI. Also, uci show network shows the right configuration options (including the AllowedIPs option). However, a wg showconf wireguard shows that the AllowedIPs config option of the first peer is not present.
Restarting the wireguard interface, or the whole router for that matter, does not make a difference.
OpenWrt 24.10.0 r28427-6df0e3d02a / LuCI openwrt-24.10 branch 25.014.55016~7046a1c
kmod-wireguard - 6.6.73-r1
luci-proto-wireguard - 25.037.68331~42f464c
wireguard-tools - 1.0.20210914-r4
Linux OpenWrt 6.6.73 #0 SMP Mon Feb 3 23:09:37 2025 aarch64 GNU/Linux
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by configuring one WireGuard peer, adding a second, and comparing the LuCI configuration and uci show network output with wg showconf wireguard. Trace the package or configuration entry point responsible for applying peers; done means the first peer's AllowedIPs remains present after adding another peer and restarting the interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100