daeuniverse / daeuniverse/dae

[Bug Report] 当通过 HTTP 代理通过 VNC 连接 macOS 时,连接失败

Closed
#673 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
6.2k
Forks
402
Avg merge
57m
Merged PRs (30d)
2

Description

### Checks

- [X] I have searched the existing issues
- [X] I have read the documentation
- [ ] Is it your first time sumbitting an issue

### Current Behavior

当通过 HTTP 代理通过 VNC 连接 macOS 时,连接失败
![屏幕共享 2024-10-10 23 09 10](https://github.com/user-attachments/assets/4bde4a79-3b22-4fbf-a678-fe2533c77f06)
日志
time="Oct 10 23:00:43" level=info msg="192.168.33.102:63035 <-> xxx:5900" dialer=1.work dscp=0 ip="xxx:5900" mac="e0:d5:5e:8c:2f:db" network=tcp4 outbound=work pid=0 pname= policy=min_moving_avg sniffed=

连接普通 HTTP 服务没有问题
time="Oct 10 23:12:14" level=debug msg="Rewrite dial target to domain" from="xxx:9080" to="xxx:9080"
time="Oct 10 23:12:14" level=debug msg="Rewrite dial target to domain" from="xxx:9080" to="xxx:9080"
time="Oct 10 23:12:14" level=info msg="192.168.33.102:50317 <-> xxx:9080" dialer=1.work dscp=0 ip="xxx:9080" mac="e0:d5:5e:8c:2f:db" network=tcp4 outbound=work pid=0 pname= policy=min_moving_avg sniffed=xxx
time="Oct 10 23:12:14" level=debug msg="Rewrite dial target to domain" from="xxx:9080" to="xxx:9080"
time="Oct 10 23:12:14" level=debug msg="Rewrite dial target to domain" from="xxx:9080" to="xxx:9080"
time="Oct 10 23:12:14" level=info msg="192.168.33.102:50318 <-> xxx:9080" dialer=1.work dscp=0 ip="xxx:9080" mac="e0:d5:5e:8c:2f:db" network=tcp4 outbound=work pid=0 pname= policy=min_moving_avg sniffed=xxx

### Expected Behavior

成功连接

### Steps to Reproduce

1. 设置目标服务走代理 dip(xx/24) -> work
2. 通过 macOS 的屏幕共享 app 或者 VNC viewer 连接目标服务器
3. 报错

### Environment

- **Dae version (use `dae --version`)**: daed 0.4.0 以来一直存在
- **OS (e.g `cat /etc/os-release`)**: ImmortalWrt 23.05.1
- **Kernel (e.g. `uname -a`)**: Linux ImmortalWrt 5.15.137 #0 SMP Sun Nov 19 17:02:49 2023 x86_64 GNU/Linux
- **Others**:

### Anything else?

_No response_

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the failure using macOS Screen Sharing or a VNC viewer through the HTTP proxy, following the listed dip(xx/24) -> work route. Compare the VNC connection logs with the successful HTTP-service logs and identify the relevant proxy path. Done means the target macOS VNC service connects successfully through the configured proxy.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, macos
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.