You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[bug] Prevent changing subnet and IP objects assigned to a VPN Server #1096
There is a need to prevent changes to the subnet and IPAdress objects when they are assigned to a VPN server. Modifying the subnet of the VPN when there are existing VPN clients creates collisions in provisioned IPs, leading to potential network issues.
Steps To Reproduce
Steps to reproduce the behavior:
Create a WireGuard VPN server and assign a subnet and IP to it.
Create a template for this VPN and assign it to a device
Edit the subnet object created in step 1 and change the subnet field
Assign the VPN template to another device
Expected behavior
Prevent changing subnet and IP address objects if there are existing VpnClients
Actual Behavior
Both devices get IP address from different subnets
Activity
nemesifier commentedon Sep 30, 2025
@pandafy this may not be easy because the IPAM models are not aware of VPN servers, so how can we implement this cleanly?
[fix] Rrevent IPAM changes when VPN clients exist #1096
[improvements] Added guards in handlers #1096
[fix] Addressed unused variables #1096
[fix] Added guards and enhanced handler implementation #1096
openwisp-companion commentedon May 8, 2026
This issue has been automatically assigned to @stktyagi who opened PR #1219 to address it. 🎯
openwisp-companion commentedon May 11, 2026
This issue has been automatically assigned to @stktyagi who opened PR #1219 to address it. 🎯
openwisp-companion commentedon Jul 1, 2026
This issue has been automatically assigned to @stktyagi who opened PR #1219 to address it. 🎯