[Feature] Multi-Interface registration issues

[seqwait]

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

In a Docker Swarm overlay network, some services are connected to the ingress network, while others are not. However, all services are connected to a custom overlay network. The issue is that Dubbo sometimes selects the ingress network, causing services that are not part of the ingress network to be unable to find providers.

The ignored and preferred options do not solve the issue because the ingress network might be assigned to eth0 or eth1 at startup, making the interface selection inconsistent.

Does Dubbo provide a way to prefer a specific subnet, such as dubbo.network.interface.address.prefix?

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

• I agree to follow this project's Code of Conduct

[AlbumenJ]

You can use dubbo.network.interface.preferred

FYI org.apache.dubbo.common.utils.NetUtils#findNetworkInterface