[Feature]: Optional automatic VPN disconnect when connected to the corporate network

Abierto
  • ¿Algo no está bien?
#1,309 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@teon ya está trabajando en esto.

Desde el 30/10/2026.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
rust
Área
mobile-dev, networking

Línea de trabajo

Start by locating the desktop client's VPN connection management and network detection entry points. The issue proposes several possible trust signals but does not choose a detection method or define configuration and completion criteria; clarify those design decisions with maintainers before implementation.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

feature
Problem description

We are using the Defguard Desktop Client as a WireGuard client and no Defguard Core deployment.

A common scenario in our environment is that users connect to the VPN while working from home and later return to the office with the same notebook. Once connected to the corporate network via Ethernet, docking station, or Wi-Fi, the VPN tunnel remains active.

While this is expected behavior, the VPN connection is typically no longer needed at that point. Many users do not notice that the tunnel is still connected, which can lead to unnecessary VPN usage, routing overhead, and additional support requests.

Proposed solution

Add an optional feature that automatically disconnects an active VPN tunnel when the client detects that the device is connected directly to the corporate network.

The detection method could be user-configurable and based on characteristics such as:

Trusted network definitions
Local subnet(s)
Default gateway
DNS servers or DNS suffixes
Wi-Fi SSID

The goal is simply to allow Defguard to recognize that the device has returned to a trusted local network where the VPN connection is no longer required.

Alternatives considered

Users can manually disconnect the VPN after returning to the office.

However, this relies entirely on user awareness and is easy to forget, especially for users who frequently move between home office and corporate locations.

Automatic detection would provide a more seamless experience and reduce the need for user intervention.

Impact

Important

Lenguaje dominante
Rust
Estrellas
371
Forks
42
Merge medio
1 d 1 h
PR fusionados (30 d)
55

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DefGuard/client

Todos los issues de DefGuard/client

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.