Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Keep a persistent connection between GUI and interface management daemon

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
grpc, rust

调研方向

首先跟踪 GUI-to-daemon 的 gRPC 边界,以及 daemon 中围绕 wireguard-rs 接口配置和统计信息流的请求处理程序。将当前的连接和生命周期行为与双向流的要求进行比较;完成的标准是两个组件都能观察到对方的断开连接,接口创建与活跃的 GUI 连接绑定,并且统计信息流不再留下悬空线程。

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

描述

optional for release refactoring

Context

The desktop client is split into a GUI and a separate service that runs in the background with elevated privileges to manage network interfaces.

At the moment the daemon is "dumb" and mostly stateless. It just listens for incoming gRPC requests and exposes basic functions from our wireguard-rs library.

When a request to configure a wireguard interface is received there is no notion of this request being related to any previously created interface. Each time we start with a blank slate (that's why we must provide the interface name for each request).
The daemon also has no knowledge of the state of the GUI client.

Proposal

My proposal is to leverage the bidirectional streaming functionality of gRPC to establish a persistent connection between the GUI and interface management daemon.

This would have the following advantages:

  • make both components immediately aware of any issues with the other side
  • prevent any possibility of the background service creating any interfaces unless the GUI is active (no network interface without a Defguard icon in the tray bar)
  • simplify interface stats streaming (no additional issues with dangling threads)
  • prevent constant errors in the background service caused by stats streaming thread not being aware that an interface has been disconnected
主要语言
Rust
星标
371
派生
41
平均合并
18 小时 48 分钟
30 天内合并 PR
41

环境准备

  • 没有 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 摘要。