Skip to content

[bug] Prevent changing subnet and IP objects assigned to a VPN Server #1096

Description

@pandafy

Description

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:

  1. Create a WireGuard VPN server and assign a subnet and IP to it.
  2. Create a template for this VPN and assign it to a device
  3. Edit the subnet object created in step 1 and change the subnet field
  4. 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

Image

The second peer has an IP address from

System Information:

  • OS: Ubuntu 24.04 LTS
  • Python Version: Python 3.11.2
  • Django Version: Django 5.2.x

Activity

  1. added theissue type on Jul 24, 2025
  2. nemesifier commented on Sep 30, 2025

    @nemesifier
    Member

    @pandafy this may not be easy because the IPAM models are not aware of VPN servers, so how can we implement this cleanly?

  3. openwisp-companion commented on May 8, 2026

    @openwisp-companion

    This issue has been automatically assigned to @stktyagi who opened PR #1219 to address it. 🎯

  4. openwisp-companion commented on May 11, 2026

    @openwisp-companion

    This issue has been automatically assigned to @stktyagi who opened PR #1219 to address it. 🎯

  5. openwisp-companion commented on Jul 1, 2026

    @openwisp-companion

    This issue has been automatically assigned to @stktyagi who opened PR #1219 to address it. 🎯

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions