[Feature]: Optional automatic VPN disconnect when connected to the corporate network
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 技术栈
- rust
- 领域
- mobile-dev, networking
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
- 主要语言
- Rust
- 星标
- 371
- 派生
- 42
- 平均合并
- 1 天 1 小时
- 30 天内合并 PR
- 54
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
DefGuard/client 的其他 Issue
-
enhancement
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
Missing "Other methods" button on MFA methods可能已有人在做 @jakub-tldr 今天认领。 未关闭bug
DefGuard/client#1311 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Change the UX of MFA configuration flow in the Desktop Client可能已有人在做 @Va1ter 今天认领。 未关闭design
DefGuard/client#1310 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 38/100
维护者通常 1 天内回复
相似的 Issue
-
good first issue help wanted r-docs
难度 2/5 1-3 小时 新手友好度 72/100
servo/rust-smallvec#824 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 83/100
维护者通常 1 天内回复
-
priority middle
难度 1/5 1 小时以内 新手友好度 62/100
KATO-Hiro/AtCoderClans#12940 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 83/100
维护者通常 1 天内回复
-
o8 next debug build aborts on Glass to Dark appearance switch (nil identifier messaged before check)未关闭bug
难度 2/5 1-3 小时 新手友好度 78/100
hurttlocker/o8#5112 ·