[GH-ISSUE #3377] The socks5 plug-in of frp cannot support ipv6 requests

gitea-mirror commented

2026-05-05 13:44:26 -06:00

Owner

Copy link

Originally created by @aa51513 on GitHub (Mar 29, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3377

Bug Description

I use the socks5 plug-in on frpc, after frpc connects to frps, I can't access the ipv6 website through the socks5 proxy port exposed by the server.

A known:
① It is normal to access the ipv4 website through the socks5 proxy;
②The client already supports ipv6 and can successfully access the ipv6 website;

frpc Version

0.46.1

frps Version

0.46.1

System Architecture

linux/amd64

Configurations

[ /etc/frp/frpc.ini]

[common]
server_addr = 127.0.0.1
server_port = 7000

[socks5_proxy_tunnel]
type = tcp
remote_port = 1080
plugin = socks5
use_encryption = false
use_compression = true

[ /etc/frp/frps.ini]

[common]
bind_port = 7000

Logs

exception log not found

Steps to reproduce

The problem can be reproduced by running directly with my configuration file

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @aa51513 on GitHub (Mar 29, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3377 ### Bug Description I use the socks5 plug-in on frpc, after frpc connects to frps, I can't access the ipv6 website through the socks5 proxy port exposed by the server. A known: ① It is normal to access the ipv4 website through the socks5 proxy; ②The client already supports ipv6 and can successfully access the ipv6 website; ### frpc Version 0.46.1 ### frps Version 0.46.1 ### System Architecture linux/amd64 ### Configurations - [ /etc/frp/frpc.ini] `[common]` `server_addr = 127.0.0.1` `server_port = 7000` `[socks5_proxy_tunnel]` `type = tcp` `remote_port = 1080` `plugin = socks5` `use_encryption = false` `use_compression = true` - [ /etc/frp/frps.ini] `[common]` `bind_port = 7000` ### Logs exception log not found ### Steps to reproduce The problem can be reproduced by running directly with my configuration file ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [X] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:44:26 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:44:29 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Apr 29, 2023):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Apr 29, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified