[Bug Report] reality 协议随机断连
- 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
- [x] Is it your first time sumbitting an issue
### Current Behavior
reality 协议会随机“断连”,故障时 curl 的表现如下:
```
❯ curl http://my.microsoftpersonalcontent.com -I
curl: (52) Empty reply from server
```
与此同时日志里会输出
```
level=info msg="192.168.5.3:40322 <-> my.microsoftpersonalcontent.com:80" dialer="xxxxxxx" dscp=0 ip="13.107.137.11:80" mac="xxxxx" network=tcp4 outbound=proxy pid=0 pname= policy=fixed sniffed=my.microsoftpersonalcontent.com
level=warning msg="handleConn: failed to dial 13.107.137.11:80: nil ecdheKey"
```
### Expected Behavior
使用 mihomo party 经过相同节点访问同一站点无此现象,故怀疑与 dae 内部实现有关
### Steps to Reproduce
反复使用 curl 访问被代理站点
### Environment
- **Dae version (use `dae --version`)**: 1.0.0
- **OS (e.g `cat /etc/os-release`)**: ImmortalWrt 24.10.0
- **Kernel (e.g. `uname -a`)**: 6.6.73
- **Others**: x86_64
### Anything else?
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the failure with repeated curl requests to the reported site on dae 1.0.0, and capture the logs around handleConn and the nil ecdheKey warning. Compare the behavior with mihomo party through the same node; done means repeated requests no longer produce an empty reply and the warning is absent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100