openwisp / openwisp/openwisp-controller
[feature] Allow defining Wireguard peers in the server to reserve IP addresses
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 773
- Forks
- 315
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 14
Description
Right now to allow non OpenWISP peers to connect to a Wireguard server managed by OpenWISP, the user needs to create fake devices which act as placeholders and reserve the IP addresses needed by these clients.
We could make this easier in the following way:
- when peers are defined in the server configuration automatically create the IP address entries in IPAM
- we have to find a way to remove the IPAM entries if the peers are removed
- we need to make sure peers defined in the server config gets passed to the resulting configuration installed on the server
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
Start by tracing how Wireguard server peers are represented in the server configuration, how IPAM entries are created and removed, and how the resulting server configuration is generated. Confirm the existing configuration and IPAM tests before changing behavior. Done means configured peers reserve IP addresses, removed peers no longer leave entries behind, and all configured peers reach the installed server configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100