[Bug]: Predefined traffic sets default route on macOS

未关闭
#1,331 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
52/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
networking

调研方向

Start by tracing how the macOS client configures routes when connecting with predefined traffic; the issue identifies netstat -rn as the way to observe the result but names no source files or tests. Compare the routes before and after connecting and investigate why a default route appears. Done when predefined traffic installs only the location’s configured routes and leaves the default route unchanged.

由索引模型根据 Issue 内容生成。

描述

bug
Summary

When choosing predefined traffic and connecting to the VPN, a default route is set (visible via netstat -rn).
We assumed that predefined traffic only routes the subnets defined in our location. A customer who relies on Defguard can't work properly, because his other active WireGuard tunnels can't function while Defguard hijacks the traffic.

Steps to reproduce
  1. Check routes via netstat -rn (especially default routes).
  2. Connect via predefined traffic.
  3. Check routes via netstat -rn again.
  4. There is now a default route on the Defguard interface.
Expected behavior

No default route is set, only the routes defined in the location for predefined traffic.

Workaround by a customer: Create a VM on macOS, install the Defguard client in it and use the VM as a router. Only allow the routes that are required for using Defguard.

Actual behavior

A default route is set, which prevents customers and potentially colleagues from using multiple VPNs at the same time as Defguard.

Defguard version

All version on the latest 2.1 stable build

Environment details

macOS (any tested version after 2024)

Deployment / install method

Docker / Docker Compose

Relevant logs / output

Relevant configuration (redacted)

主要语言
Rust
星标
373
派生
42
平均合并
20 小时 54 分钟
30 天内合并 PR
51

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

DefGuard/client 的其他 Issue

查看 DefGuard/client 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。