-
-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPv6 proxy weirdness #4180
Comments
You are not using the same configuration? You need to check the error messages in the frps log. |
I think it was late in night and I pasted wrong logs.. I recreated the scenario again. I also removed ssh proxy so that logs can be simple to look at. Here is config: [common]
bind_port = 2333 ipv6 server bindAddr = "::"
bindPort = 2333
log.level = "debug" local client config serverAddr = "<IPv6_address>"
# serverAddr = "<IPv4_Address>"
serverPort = 2333
log.level = "trace"
[[proxies]]
name = "web"
type = "tcp"
localIp = "127.0.0.1"
localPort = 80
remotePort = 80
Here are logs:
Connecting to ipv6 machine
Corresponding ipv6 server logs:
The service is available locally ❯ curl -I 127.0.0.1
HTTP/1.1 200 OK
Server: openresty
Date: Thu, 25 Apr 2024 17:10:36 GMT
Content-Type: text/html
Content-Length: 1033
Last-Modified: Wed, 28 Feb 2024 22:25:56 GMT
Connection: keep-alive
ETag: "65dfb2f4-409"
Accept-Ranges: bytes |
看起来 frps 所在的服务器,80 端口被其他进程占用 |
另外 bindAddr = "::" 不是必须的 |
@dharapvj You can refer to the comments above to confirm if port 80 has been occupied and try removing bindAddr. |
I just request you to try out such a scenario once. I have given detailed information and logs so that it could be easier for you to try and reproduce. Can you please try reproducing the issue once? |
You cannot expect everyone to have the same environment as you do, there are tests related to IPv6 in end-to-end testing, and obvious errors will be directly detected. If possible, please conduct more tests, try more ports or other configuration adjustments. Otherwise, I won't be able to provide much help. |
Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close. |
Bug Description
If frpc connects to frps server via IPv6 - I cannot connect to local services exposed via container e.g. nginx docker container. But same frpc connects to frps via IPv4, same local service can get connected.
More details can be found in the reproduction steps.
frpc Version
0.57.0
frps Version
0.57.0
System Architecture
linux/amd (client) linux/arm64 (server)
Configurations
Logs
Logs:
Logs when connected to IPv4 Server:
Steps to reproduce
podman run -p 9000:9000 -p 9001:9001 quay.io/minio/minio server /data --console-address ":9001"
But anything else like nginx will also do. I can access service viacurl -v localhost:9000
on the local machine host.Affected area
The text was updated successfully, but these errors were encountered: