apache/dubbo

Support SOCKS5 proxy for tri protocol in NettyConnectionClient

Open

#16276 opened on May 18, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (41,524 stars) (26,453 forks)batch import
help wanted

Description

Pre-check

  • I am sure that all the content I provide is in English.

Search before asking

  • I had searched in the issues and found no similar feature requirement.

Apache Dubbo Component

Java SDK (apache/dubbo)

Descriptions

Body: Hello maintainers,

We are currently using Dubbo 3.3.6 with the tri (Triple) protocol. While reviewing the source code, I noticed that org.apache.dubbo.remoting.transport.netty4.NettyConnectionClient still contains the following TODO:

// set null but do not close this client, it will be reconnecting in the future
ch.closeFuture().addListener(channelFuture -> clearNettyChannel());
// TODO support Socks5

From our current testing, it seems that tri protocol does not yet support SOCKS5 proxying on the client side. JVM-level proxy settings such as:

-DsocksProxyHost=...
-DsocksProxyPort=...

do not appear to work for tri connections, which is understandable since the client is based on Netty rather than plain JDK sockets.

We have a real use case for this feature, such as:

  • local development environments accessing remote Dubbo services through a SOCKS5 proxy
  • cross-network or restricted-network scenarios where direct connectivity is not available

Could you please clarify:

  1. Is SOCKS5 support for tri protocol already on the roadmap?
  2. If yes, is there any planned version or milestone for it?
  3. If not, what would be the recommended extension point or workaround for now? For example, is it expected to support something like Netty's Socks5ProxyHandler in the client pipeline in the future?

Environment:

  • Dubbo version: 3.3.6
  • Protocol: tri / Triple
  • Transport: Netty

Thanks in advance.

Related issues

No response

Are you willing to submit a pull request to fix on your own?

  • Yes I am willing to submit a pull request on my own!

Code of Conduct

Contributor guide

Tech stack
java
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaNetty frameworkSOCKS5 protocol
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Examine the TODO in `org.apache.dubbo.remoting.transport.netty4.NettyConnectionClient` (likely line with `// TODO support Socks5`). Research how to integrate Netty's `Socks5ProxyHandler` into the client's channel pipeline, possibly by adding it conditionally based on JVM proxy properties like `socksProxyHost` and `socksProxyPort`. Review how other Netty based clients in Dubbo handle proxy settings. Since the author is willing to submit a PR, the implementation should be a localized change to the channel initializer.