github-starred/frp
2
0
Fork 0
mirror of https://github.com/fatedier/frp.git synced 2026-05-15 08:05:49 -06:00
Code Issues 40 Projects Packages Wiki Activity Actions 1

[GH-ISSUE #452] frps能否强制只监听ipv4端口 #345

New issue
Closed
opened 2026-05-05 12:08:44 -06:00 by gitea-mirror · 16 comments
gitea-mirror commented 2026-05-05 12:08:44 -06:00
Owner
Copy link

Originally created by @iceking2001 on GitHub (Sep 4, 2017).
Original GitHub issue: https://github.com/fatedier/frp/issues/452

Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly.
(为了节约时间，提高处理问题的效率，不按照格式填写的 issue 将会直接关闭。)

Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST

What version of frp are you using (./frpc -v or ./frps -v)?
./frps

What operating system and processor architecture are you using (go env)?
centos 7.3 x64

Configures you used:
frps_full.ini 默认配置

Steps to reproduce the issue:

  1. 启动 ./frps -c ./frps_full.ini
  2. 无法访问 http://[server_ip]:7500
  3. netstat -nap|grep frps 发现监听的是ipv6：
    tcp6 0 0 :::7500 :::* LISTEN 2311/./frps
    tcp6 0 0 :::8080 :::* LISTEN 2311/./frps
    tcp6 0 0 :::7000 :::* LISTEN 2311/./frps
    tcp6 0 0 :::443 :::* LISTEN 2311/./frps
    udp6 0 0 :::7000 :::* 2311/./frps
  4. 配置aliyun主机的ipv6支持也无效。所以，能否强制只监听ipv4端口

Describe the results you received:
无法访问dashboard

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):

Can you point out what caused this issue (optional)

Originally created by @iceking2001 on GitHub (Sep 4, 2017). Original GitHub issue: https://github.com/fatedier/frp/issues/452 Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly. (为了节约时间，提高处理问题的效率，不按照格式填写的 issue 将会直接关闭。) Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST **What version of frp are you using (./frpc -v or ./frps -v)?** ./frps **What operating system and processor architecture are you using (`go env`)?** centos 7.3 x64 **Configures you used:** frps_full.ini 默认配置 **Steps to reproduce the issue:** 1. 启动 ./frps -c ./frps_full.ini 2. 无法访问 http://[server_ip]:7500 3. netstat -nap|grep frps 发现监听的是ipv6： tcp6 0 0 :::7500 :::* LISTEN 2311/./frps tcp6 0 0 :::8080 :::* LISTEN 2311/./frps tcp6 0 0 :::7000 :::* LISTEN 2311/./frps tcp6 0 0 :::443 :::* LISTEN 2311/./frps udp6 0 0 :::7000 :::* 2311/./frps 4. 配置aliyun主机的ipv6支持也无效。所以，能否强制只监听ipv4端口 **Describe the results you received:** 无法访问dashboard **Describe the results you expected:** **Additional information you deem important (e.g. issue happens only occasionally):** **Can you point out what caused this issue (optional)**
gitea-mirror commented 2026-05-05 12:08:48 -06:00
Author
Owner
Copy link

@fatedier commented on GitHub (Sep 4, 2017):

首先你要确定是否是由于这个原因造成的，还是说是因为其他原因。你要提供推理和分析的结果。

<!-- gh-comment-id:326945950 --> @fatedier commented on GitHub (Sep 4, 2017): 首先你要确定是否是由于这个原因造成的，还是说是因为其他原因。你要提供推理和分析的结果。
gitea-mirror commented 2026-05-05 12:08:50 -06:00
Author
Owner
Copy link

@qingyuan0o0 commented on GitHub (Nov 29, 2017):

我也碰到类似的问题，在ubuntu本地是有ipv6的网络，但是在客户端连接后，在Ubuntu中使用
netstat -an|grep : 发现显示的都是tcp6 udp6，呈现出客户端的连接
frps.ini的设置
[common]
local_ip = 0.0.0.0
bind_port = 7000
客户端配置大致是下图
image
但是显示
image

<!-- gh-comment-id:347767292 --> @qingyuan0o0 commented on GitHub (Nov 29, 2017): 我也碰到类似的问题，在ubuntu本地是有ipv6的网络，但是在客户端连接后，在Ubuntu中使用 netstat -an|grep : 发现显示的都是tcp6 udp6，呈现出客户端的连接 frps.ini的设置 [common] local_ip = 0.0.0.0 bind_port = 7000 客户端配置大致是下图 ![image](https://user-images.githubusercontent.com/18437931/33361360-b95d0b8a-d512-11e7-9d07-c6bfa61af7b9.png) 但是显示 ![image](https://user-images.githubusercontent.com/18437931/33361394-dee67af8-d512-11e7-9913-b7bdb25ce878.png)
gitea-mirror commented 2026-05-05 12:08:52 -06:00
Author
Owner
Copy link

@qingyuan0o0 commented on GitHub (Nov 29, 2017):

额，虽然显示是这样，但是后续测试中发现，居然可以正常访问。。。ipv4的

<!-- gh-comment-id:347768342 --> @qingyuan0o0 commented on GitHub (Nov 29, 2017): 额，虽然显示是这样，但是后续测试中发现，居然可以正常访问。。。ipv4的
gitea-mirror commented 2026-05-05 12:08:53 -06:00
Author
Owner
Copy link

@xiahuaijia commented on GitHub (Jun 21, 2018):

遇到同样问题 ,阿里云主机突然监听ipv6 无法访问

<!-- gh-comment-id:398987903 --> @xiahuaijia commented on GitHub (Jun 21, 2018): 遇到同样问题 ,阿里云主机突然监听ipv6 无法访问
gitea-mirror commented 2026-05-05 12:08:55 -06:00
Author
Owner
Copy link

@LiuGaoyong commented on GitHub (Jul 22, 2019):

所以，这个问题怎么解决？？

<!-- gh-comment-id:513649623 --> @LiuGaoyong commented on GitHub (Jul 22, 2019): 所以，这个问题怎么解决？？
gitea-mirror commented 2026-05-05 12:08:56 -06:00
Author
Owner
Copy link

@hao222 commented on GitHub (Aug 27, 2020):

腾讯云监听了ipv6，但是我设置放在同一个安全组下的，其他大部分是ipv4 只有mysql是ipv6， 然后本地客户端访问不了，connected refused

<!-- gh-comment-id:681889621 --> @hao222 commented on GitHub (Aug 27, 2020): 腾讯云监听了ipv6，但是我设置放在同一个安全组下的，其他大部分是ipv4 只有mysql是ipv6， 然后本地客户端访问不了，connected refused
gitea-mirror commented 2026-05-05 12:08:57 -06:00
Author
Owner
Copy link

@RenJunFeng commented on GitHub (Oct 12, 2020):

如何解决？我本地运行也是这样，设置了
[common]
bind_addr = 0.0.0.0 也是不行

<!-- gh-comment-id:706887418 --> @RenJunFeng commented on GitHub (Oct 12, 2020): 如何解决？我本地运行也是这样，设置了 [common] bind_addr = 0.0.0.0 也是不行
gitea-mirror commented 2026-05-05 12:09:01 -06:00
Author
Owner
Copy link

@marcuswang6 commented on GitHub (Apr 5, 2022):

同无法解决 2022

<!-- gh-comment-id:1088228493 --> @marcuswang6 commented on GitHub (Apr 5, 2022): 同无法解决 2022
gitea-mirror commented 2026-05-05 12:09:04 -06:00
Author
Owner
Copy link

@zhjou commented on GitHub (May 1, 2022):

ubuntu 20.04 LTS, bind_addr = 0.0.0.0 还是不行

<!-- gh-comment-id:1114282775 --> @zhjou commented on GitHub (May 1, 2022): ubuntu 20.04 LTS, bind_addr = 0.0.0.0 还是不行
gitea-mirror commented 2026-05-05 12:09:06 -06:00
Author
Owner
Copy link

@gldsly commented on GitHub (Nov 29, 2022):

腾讯云服务器也发现这个问题了。不知道为啥在云服务器上访问 127 + frps 监听的端口 全是无数据，然后就 502 错误了

[root@VM-xVO5pN310rIk ~]# netstat -anp | grep frps
tcp6       0      0 :::57709                :::*                    LISTEN      23200/./frps        
tcp6       0      0 :::58096                :::*                    LISTEN      23200/./frps        
tcp6       0      0 :::7000                 :::*                    LISTEN      23200/./frps        
tcp6       0      0 :::50022                :::*                    LISTEN      23200/./frps        
tcp6       0      0 103.175.14.37:50022     101.229.151.233:61677   ESTABLISHED 23200/./frps        
tcp6       0      0 103.175.14.37:7000      223.166.231.179:15322   ESTABLISHED 23200/./frps        
[root@VM-xVO5pN310rIk ~]# 
[root@VM-xVO5pN310rIk ~]# 
[root@VM-xVO5pN310rIk ~]# wget http://127.0.0.1:50022
--2022-11-29 05:29:27--  http://127.0.0.1:50022/
Connecting to 127.0.0.1:50022... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

--2022-11-29 05:29:28--  (try: 2)  http://127.0.0.1:50022/
Connecting to 127.0.0.1:50022... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

--2022-11-29 05:29:30--  (try: 3)  http://127.0.0.1:50022/
Connecting to 127.0.0.1:50022... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

No data received.
Retrying.

^C
[root@VM-xVO5pN310rIk ~]#

客户端是正常的，配置测试信息如下

local_ip = 127.0.0.1
local_port = 7709
remote_port = 57709
➜  Downloads 
➜  Downloads 
➜  Downloads 
➜  Downloads wget http://127.0.0.1:7709
--2022-11-29 13:31:26--  http://127.0.0.1:7709/
正在连接 127.0.0.1:7709... 已连接。
已发出 HTTP 请求，正在等待回应... 404 Not Found
2022-11-29 13:31:26 错误 404：Not Found。

➜  Downloads
<!-- gh-comment-id:1330102465 --> @gldsly commented on GitHub (Nov 29, 2022): 腾讯云服务器也发现这个问题了。不知道为啥在云服务器上访问 127 + frps 监听的端口 全是无数据，然后就 502 错误了 ```bash [root@VM-xVO5pN310rIk ~]# netstat -anp | grep frps tcp6 0 0 :::57709 :::* LISTEN 23200/./frps tcp6 0 0 :::58096 :::* LISTEN 23200/./frps tcp6 0 0 :::7000 :::* LISTEN 23200/./frps tcp6 0 0 :::50022 :::* LISTEN 23200/./frps tcp6 0 0 103.175.14.37:50022 101.229.151.233:61677 ESTABLISHED 23200/./frps tcp6 0 0 103.175.14.37:7000 223.166.231.179:15322 ESTABLISHED 23200/./frps [root@VM-xVO5pN310rIk ~]# [root@VM-xVO5pN310rIk ~]# [root@VM-xVO5pN310rIk ~]# wget http://127.0.0.1:50022 --2022-11-29 05:29:27-- http://127.0.0.1:50022/ Connecting to 127.0.0.1:50022... connected. HTTP request sent, awaiting response... No data received. Retrying. --2022-11-29 05:29:28-- (try: 2) http://127.0.0.1:50022/ Connecting to 127.0.0.1:50022... connected. HTTP request sent, awaiting response... No data received. Retrying. --2022-11-29 05:29:30-- (try: 3) http://127.0.0.1:50022/ Connecting to 127.0.0.1:50022... connected. HTTP request sent, awaiting response... No data received. Retrying. No data received. Retrying. ^C [root@VM-xVO5pN310rIk ~]# ``` 客户端是正常的，配置测试信息如下 ```bash local_ip = 127.0.0.1 local_port = 7709 remote_port = 57709 ➜ Downloads ➜ Downloads ➜ Downloads ➜ Downloads wget http://127.0.0.1:7709 --2022-11-29 13:31:26-- http://127.0.0.1:7709/ 正在连接 127.0.0.1:7709... 已连接。 已发出 HTTP 请求，正在等待回应... 404 Not Found 2022-11-29 13:31:26 错误 404：Not Found。 ➜ Downloads ```
gitea-mirror commented 2026-05-05 12:09:06 -06:00
Author
Owner
Copy link

@netfun2000 commented on GitHub (Apr 5, 2023):

今天用阿里云安装frps，同样出现了这个问题。frps显示ipv6
本机可以访问frps端口，外网无法访问。

<!-- gh-comment-id:1497180764 --> @netfun2000 commented on GitHub (Apr 5, 2023): 今天用阿里云安装frps，同样出现了这个问题。frps显示ipv6 本机可以访问frps端口，外网无法访问。
gitea-mirror commented 2026-05-05 12:09:08 -06:00
Author
Owner
Copy link

@VCE1 commented on GitHub (Jul 19, 2023):

我在Ubuntu 20上也遇到了这个问题，尽管我已经在/etc/sysctl.conf中设置了以下内容：

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1

并且在frps.ini中填写了bind_addr = 0.0.0.0，但是frps仍然监听IPv6地址，

tcp6       0      0 :::25565                :::*                    LISTEN      1626612/frps

不知道具体的原因，但是能正常访问。

<!-- gh-comment-id:1642452589 --> @VCE1 commented on GitHub (Jul 19, 2023): 我在Ubuntu 20上也遇到了这个问题，尽管我已经在/etc/sysctl.conf中设置了以下内容： ```conf net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 ``` 并且在frps.ini中填写了bind_addr = 0.0.0.0，但是frps仍然监听IPv6地址， ```conf tcp6 0 0 :::25565 :::* LISTEN 1626612/frps ``` 不知道具体的原因，但是能正常访问。
gitea-mirror commented 2026-05-05 12:09:11 -06:00
Author
Owner
Copy link

@shuguang101 commented on GitHub (May 7, 2024):

刚刚也遇到了这个问题，调查了一下，是golang的问题。 golang 0.0.0.0 确实会监听ipv6, 这与nginx，apache等软件的行为并不相同。从直观上来说当用户指定一个ipv4地址时不应该去监听ipv6， 但golang无论是使用0.0.0.0或[::] 都会同时监听ipv4和ipv6, 并且为了backwards compatibility不会对这个行为进行修改。。。。。
https://github.com/golang/go/issues/48723
https://github.com/golang/go/issues/17615

<!-- gh-comment-id:2098224628 --> @shuguang101 commented on GitHub (May 7, 2024): 刚刚也遇到了这个问题，调查了一下，是golang的问题。 golang 0.0.0.0 确实会监听ipv6, 这与nginx，apache等软件的行为并不相同。从直观上来说当用户指定一个ipv4地址时不应该去监听ipv6， 但golang无论是使用0.0.0.0或[::] 都会同时监听ipv4和ipv6, 并且为了backwards compatibility不会对这个行为进行修改。。。。。 https://github.com/golang/go/issues/48723 https://github.com/golang/go/issues/17615
gitea-mirror commented 2026-05-05 12:09:12 -06:00
Author
Owner
Copy link

@xingon commented on GitHub (Jun 30, 2024):

同样的问题啊，Fasttunnel也是这样的，其实就是配置0.0.0.0的时候他默认使用的TCP，应该显式使用TCP4才行，

<!-- gh-comment-id:2198528513 --> @xingon commented on GitHub (Jun 30, 2024): 同样的问题啊，Fasttunnel也是这样的，其实就是配置0.0.0.0的时候他默认使用的TCP，应该显式使用TCP4才行，
gitea-mirror commented 2026-05-05 12:09:13 -06:00
Author
Owner
Copy link

@zasray commented on GitHub (Oct 29, 2024):

腾讯云 2024-10-29，还是这样子！无法解决

<!-- gh-comment-id:2443020971 --> @zasray commented on GitHub (Oct 29, 2024): 腾讯云 2024-10-29，还是这样子！无法解决
gitea-mirror commented 2026-05-05 12:09:14 -06:00
Author
Owner
Copy link

@tomjerrygood commented on GitHub (Feb 18, 2025):

me too。远端fprs服务端在ipv4环境。我在的客户端frpc.ini 配置了
server_addr = Ipv4域名(a.b.c)
bind_address = 0.0.0.0，
本地frpc 运行优先解析ipv6，所以总是不能连接到服务器。
执行
/system/etc/frpc$ /system/etc/frpc/frpc -c /system/etc/frpc/frpc.ini
显示错误
2025/02/18 05:35:48 [W] [service.go:128] login to server failed: dial tcp: lookup a.b.c on [::1]:53: read udp [::1]:42425->[::1]:53: read: connection refused
dial tcp: lookup green86.asuscomm.com on [::1]:53: read udp [::1]:42425->[::1]:53: read: connection refused

服务器域名改为固定ipv4 地址就能连接成功。但是域名是动态的，不能固定IP地址。
希望大佬能否给出强制IPv4的选项

<!-- gh-comment-id:2664656509 --> @tomjerrygood commented on GitHub (Feb 18, 2025): me too。远端fprs服务端在ipv4环境。我在的客户端frpc.ini 配置了 server_addr = Ipv4域名(a.b.c) bind_address = 0.0.0.0， 本地frpc 运行优先解析ipv6，所以总是不能连接到服务器。 执行 /system/etc/frpc$ /system/etc/frpc/frpc -c /system/etc/frpc/frpc.ini 显示错误 2025/02/18 05:35:48 [W] [service.go:128] login to server failed: dial tcp: lookup a.b.c on [::1]:53: read udp [::1]:42425->[::1]:53: read: connection refused dial tcp: lookup green86.asuscomm.com on [::1]:53: read udp [::1]:42425->[::1]:53: read: connection refused 服务器域名改为固定ipv4 地址就能连接成功。但是域名是动态的，不能固定IP地址。 希望大佬能否给出强制IPv4的选项
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
dev
new
master
copilot/review-pull-request-5198
v0.68.1
v0.68.0
v0.67.0
v0.66.0
v0.65.0
v0.64.0
v0.63.0
v0.62.1
v0.62.0
v0.61.2
v0.61.1
v0.61.0
v0.60.0
v0.59.0
v0.58.1
v0.58.0
v0.57.0
v0.56.0
v0.55.1
v0.55.0
v0.54.0
v0.53.2
v0.53.1
v0.53.0
v0.52.3
v0.52.2
v0.52.1
v0.52.0
v0.51.3
v0.51.2
v0.51.1
v0.51.0
v0.50.0
v0.49.0
v0.48.0
v0.47.0
v0.46.1
v0.46.0
v0.45.0
v0.44.0
v0.43.0
v0.42.0
v0.41.0
v0.40.0
v0.39.1
v0.39.0
v0.38.0
v0.37.1
v0.37.0
v0.36.2
v0.36.1
v0.36.0
v0.35.1
v0.35.0
v0.34.3
v0.34.2
v0.34.1
v0.34.0
v0.33.0
v0.32.1
v0.32.0
v0.31.2
v0.31.1
v0.31.0
v0.30.0
v0.29.1
v0.29.0
v0.28.2
v0.28.1
v0.28.0
v0.27.1
v0.27.0
v0.26.0
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.1
v0.24.0
v0.23.3
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.0
v0.19.1
v0.19.0
v0.18.0
v0.17.0
v0.16.1
v0.16.0
v0.15.1
v0.15.0
v0.14.1
v0.14.0
v0.13.0
v0.12.0
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.1
v0.8.0
v0.7.0
v0.6.0
v0.5.0
v0.3.0
v0.2.0
v0.1.0
Labels
Clear labels   
In Progress

   
WIP

   
WaitingForInfo

   
bug

   
doc

   
duplicate

   
easy

   
enhancement

   
future

   
help wanted

   
invalid

   
lifecycle/stale

   
need-issue-template

   
need-usage-help

   
no plan

   
proposal

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
todo
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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: github-starred/frp#345
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?