[GH-ISSUE #330] 内网穿透(dns)无法正常解析dns #244

Closed
opened 2026-02-27 23:16:09 +03:00 by kerem · 0 comments
Owner

Originally created by @pog2g on GitHub (Nov 4, 2019).
Original GitHub issue: https://github.com/snail007/goproxy/issues/330

最新版(v8.5)内网穿透dns使用普通方法,,无法正常解析(完全按照官方教程)

vps上执行
./proxy bridge -p ":33080" -C proxy.crt -K proxy.key
./proxy server --udp -r ":53@:53" -P "127.0.0.1:33080" -C proxy.crt -K proxy.key

在公司机器A上面执行
./proxy client -P "22.22.22.22:33080" -C proxy.crt -K proxy.key
  • server日志
2019/11/04 21:00:04 session[0] created
2019/11/04 21:00:04 udp conn 35962b5355fb0f7d291fed4776bc3f2453001ca1 connected
2019/11/04 21:00:04 udp conn read udp packet fail , err: EOF 
2019/11/04 21:00:04 udp conn 35962b5355fb0f7d291fed4776bc3f2453001ca1 released
2019/11/04 21:00:05 session[6] created
2019/11/04 21:00:05 udp conn 01d4bbb2df938397587e0aadb52be1e06a31f07b connected
2019/11/04 21:00:05 udp conn read udp packet fail , err: EOF 
2019/11/04 21:00:05 udp conn 01d4bbb2df938397587e0aadb52be1e06a31f07b released
  • 公司A机器日志
2019/11/04 21:02:22 udp conn 819a670529d83aaa5f594f31777d0ddf229f554b connected
2019/11/04 21:02:22 udp conn read udp packet fail , err: read udp 127.0.0.1:37393->127.0.0.1:53: read: connection refused 
2019/11/04 21:02:22 udp packet revecived from bridge fail, err: io: read/write on closed pipe
2019/11/04 21:02:22 udp conn 819a670529d83aaa5f594f31777d0ddf229f554b released
2019/11/04 21:02:23 worker[3] signal revecived,server 8ba884a3a2bf497fb413183ed3cca67fcd59db0b stream 8b69a963c46669adfdaeb91335b1bd409ac1e6bd udp:127.0.0.1:53
2019/11/04 21:02:23 udp conn 8b69a963c46669adfdaeb91335b1bd409ac1e6bd connected
2019/11/04 21:02:23 udp conn read udp packet fail , err: read udp 127.0.0.1:44593->127.0.0.1:53: read: connection refused 
2019/11/04 21:02:23 udp conn 8b69a963c46669adfdaeb91335b1bd409ac1e6bd released
2019/11/04 21:02:23 udp packet revecived from bridge fail, err: io: read/write on closed pipe

请问大佬啥子原因,案例不可行吗??就是按照内网穿透UDP普通用法做的,,那个环节有流程(vps服务器应开放了udp53端口的)

Originally created by @pog2g on GitHub (Nov 4, 2019). Original GitHub issue: https://github.com/snail007/goproxy/issues/330 最新版(v8.5)内网穿透dns使用普通方法,,无法正常解析(完全按照官方教程) ``` vps上执行 ./proxy bridge -p ":33080" -C proxy.crt -K proxy.key ./proxy server --udp -r ":53@:53" -P "127.0.0.1:33080" -C proxy.crt -K proxy.key 在公司机器A上面执行 ./proxy client -P "22.22.22.22:33080" -C proxy.crt -K proxy.key ``` * server日志 ``` 2019/11/04 21:00:04 session[0] created 2019/11/04 21:00:04 udp conn 35962b5355fb0f7d291fed4776bc3f2453001ca1 connected 2019/11/04 21:00:04 udp conn read udp packet fail , err: EOF 2019/11/04 21:00:04 udp conn 35962b5355fb0f7d291fed4776bc3f2453001ca1 released 2019/11/04 21:00:05 session[6] created 2019/11/04 21:00:05 udp conn 01d4bbb2df938397587e0aadb52be1e06a31f07b connected 2019/11/04 21:00:05 udp conn read udp packet fail , err: EOF 2019/11/04 21:00:05 udp conn 01d4bbb2df938397587e0aadb52be1e06a31f07b released ``` * 公司A机器日志 ``` 2019/11/04 21:02:22 udp conn 819a670529d83aaa5f594f31777d0ddf229f554b connected 2019/11/04 21:02:22 udp conn read udp packet fail , err: read udp 127.0.0.1:37393->127.0.0.1:53: read: connection refused 2019/11/04 21:02:22 udp packet revecived from bridge fail, err: io: read/write on closed pipe 2019/11/04 21:02:22 udp conn 819a670529d83aaa5f594f31777d0ddf229f554b released 2019/11/04 21:02:23 worker[3] signal revecived,server 8ba884a3a2bf497fb413183ed3cca67fcd59db0b stream 8b69a963c46669adfdaeb91335b1bd409ac1e6bd udp:127.0.0.1:53 2019/11/04 21:02:23 udp conn 8b69a963c46669adfdaeb91335b1bd409ac1e6bd connected 2019/11/04 21:02:23 udp conn read udp packet fail , err: read udp 127.0.0.1:44593->127.0.0.1:53: read: connection refused 2019/11/04 21:02:23 udp conn 8b69a963c46669adfdaeb91335b1bd409ac1e6bd released 2019/11/04 21:02:23 udp packet revecived from bridge fail, err: io: read/write on closed pipe ``` 请问大佬啥子原因,案例不可行吗??就是按照内网穿透UDP普通用法做的,,那个环节有流程(vps服务器应开放了udp53端口的)
kerem closed this issue 2026-02-27 23:16:09 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/goproxy#244
No description provided.