[GH-ISSUE #231] 如何让程序强行在ipv4上监听端口 #150

Closed
opened 2026-02-27 23:15:40 +03:00 by kerem · 5 comments
Owner

Originally created by @J-Cod3r on GitHub (Mar 11, 2019).
Original GitHub issue: https://github.com/snail007/goproxy/issues/231

vps上执行netstat查看发现程序只监听在tcp6上

Originally created by @J-Cod3r on GitHub (Mar 11, 2019). Original GitHub issue: https://github.com/snail007/goproxy/issues/231 vps上执行netstat查看发现程序只监听在tcp6上
kerem closed this issue 2026-02-27 23:15:40 +03:00
Author
Owner

@snail007 commented on GitHub (Mar 11, 2019):

那个显示是说明ipv6包含ipv4,你要绑定具体IP就写在参数里面。

<!-- gh-comment-id:471388425 --> @snail007 commented on GitHub (Mar 11, 2019): 那个显示是说明ipv6包含ipv4,你要绑定具体IP就写在参数里面。
Author
Owner

@J-Cod3r commented on GitHub (Mar 11, 2019):

那个显示是说明ipv6包含ipv4,你要绑定具体IP就写在参数里面。

按照你的方法确认绑定上了,但客户端连接报这个错是什么原因?7.1版本 老版本没出过这个问题
[checker] 2019/03/11 11:02:38 check update fail, please check your network

<!-- gh-comment-id:471391389 --> @J-Cod3r commented on GitHub (Mar 11, 2019): > 那个显示是说明ipv6包含ipv4,你要绑定具体IP就写在参数里面。 按照你的方法确认绑定上了,但客户端连接报这个错是什么原因?7.1版本 老版本没出过这个问题 [checker] 2019/03/11 11:02:38 check update fail, please check your network
Author
Owner

@snail007 commented on GitHub (Mar 11, 2019):

proxy必须可以访问网络

<!-- gh-comment-id:471420031 --> @snail007 commented on GitHub (Mar 11, 2019): proxy必须可以访问网络
Author
Owner

@J-Cod3r commented on GitHub (Mar 11, 2019):

网络应该没问题,在没升级到7.1之前都是正常的,而且我在本地是可以telnet上服务器上proxy的端口的,请问这个客户端在连接的过程中是按什么条件判断网络有问题的?

<!-- gh-comment-id:471422485 --> @J-Cod3r commented on GitHub (Mar 11, 2019): 网络应该没问题,在没升级到7.1之前都是正常的,而且我在本地是可以telnet上服务器上proxy的端口的,请问这个客户端在连接的过程中是按什么条件判断网络有问题的?
Author
Owner

@snail007 commented on GitHub (Mar 11, 2019):

proxy必须可以访问互联网

<!-- gh-comment-id:471427454 --> @snail007 commented on GitHub (Mar 11, 2019): proxy必须可以访问互联网
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#150
No description provided.