客户端如何看到连接信息
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 15.2k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
/usr/local/bin/brook client -s [2607:f:0:1::7]:12347 -p xxxxxpppp --socks5 127.0.0.1:4080
希望能看到连接信息，例如 ss-libev 的信息如下
2026-09-15 11:52:35 INFO: remote: 0.0.0.0:8964
2026-09-15 11:52:36 INFO: connection from 127.0.0.1:33476
2026-09-15 11:52:36 INFO: connect to www.google.com:443
2026-09-15 11:52:36 INFO: remote: 0.0.0.0:8964
2026-09-15 11:52:36 INFO: connection from 127.0.0.1:33484
2026-09-15 11:52:36 INFO: connect to thumb.wikimedia.org:443
或者像 naive proxy 等
[0915/114551.605564:INFO:277] Connection 18861 to avatars.githubusercontent.com:443
[0915/114552.143243:INFO:185] Connection 18859 closed: OK
[0915/114552.146186:INFO:185] Connection 18861 closed: OK
[0915/114557.132305:INFO:277] Connection 18863 to waa-pa.clients6.google.com:443
[0915/114558.501189:INFO:277] Connection 18865 to discourse.julialang.org:443
很早的版本 有 debug 选项, 不过输出的内容太多太快。 当前的版本有 --log, 但好像 client 下不支持
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the brook client command and its current --log and debug option handling, then trace where client connections are opened and closed. Define the connection events and verbosity expected from the examples, implement the client-side reporting, and verify that normal output remains usable while connection destinations and closures are visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100