xuxiaowei-com-cn opened a new issue, #8089: URL: https://github.com/apache/incubator-seata/issues/8089
### Check Ahead - [x] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate. - [x] I am willing to try to implement this feature myself. ### Why you need it? **English:** In environments with multiple network interfaces (especially when virtual machine software like VMware, VirtualBox, or Docker is installed), Seata may incorrectly select a virtual network interface instead of the actual physical network interface. This causes service registration and communication issues. **Problem scenarios:** - Developers running VMware or VirtualBox on their machines have virtual network adapters (e.g., VMware Network Adapter, VirtualBox Host-Only Network) - Docker creates bridge and veth interfaces that may be selected incorrectly - Seata server or client registers with the wrong IP address, making it unreachable by other services - Existing `preferredNetworks` configuration is not sufficient when virtual interfaces match the preferred network pattern Similar to Spring Cloud's `spring.cloud.inetutils.ignored-interfaces` configuration, Seata needs a way to explicitly exclude unwanted network interfaces. **中文：** 在具有多个网络接口的环境中（特别是安装了 VMware、VirtualBox 或 Docker 等虚拟机软件时），Seata 可能会错误地选择虚拟网络接口而不是实际的物理网络接口。这会导致服务注册和通信问题。 **问题场景：** - 开发人员在机器上运行 VMware 或 VirtualBox 时会有虚拟网络适配器（例如 VMware Network Adapter、VirtualBox Host-Only Network） - Docker 创建的 bridge 和 veth 接口可能被错误选择 - Seata 服务端或客户端使用错误的 IP 地址注册，导致其他服务无法访问 - 现有的 `preferredNetworks` 配置不足以解决问题，因为虚拟接口可能也匹配首选网络模式 类似于 Spring Cloud 的 `spring.cloud.inetutils.ignored-interfaces` 配置，Seata 需要一种方式来明确排除不需要的网络接口。 ### How it could be? _No response_ ### Other related information **English:** **Inspired by:** Spring Cloud Commons `spring.cloud.inetutils.ignored-interfaces` configuration, which provides similar functionality for Spring Cloud applications. **Common ignored interface patterns:** - `VMware.*` - VMware virtual network adapters - `VirtualBox.*` - VirtualBox host-only and NAT adapters - `docker.*` - Docker bridge interfaces - `veth.*` - Docker container virtual ethernet interfaces - `bridge.*` - Linux bridge interfaces - `virbr.*` - libvirt virtual bridge interfaces **Benefits:** - Solves IP address selection issues in development environments with VM software - Provides fine-grained control over network interface selection - Works seamlessly with existing `preferredNetworks` configuration - Regex support allows flexible pattern matching - No breaking changes to existing deployments --- **中文：** **灵感来源：** Spring Cloud Commons 的 `spring.cloud.inetutils.ignored-interfaces` 配置，为 Spring Cloud 应用程序提供了类似的功能。 **常见的忽略接口模式：** - `VMware.*` - VMware 虚拟网络适配器 - `VirtualBox.*` - VirtualBox 仅主机和 NAT 适配器 - `docker.*` - Docker 桥接接口 - `veth.*` - Docker 容器虚拟以太网接口 - `bridge.*` - Linux 桥接接口 - `virbr.*` - libvirt 虚拟桥接接口 **优势：** - 解决了在安装虚拟机软件的开发环境中的 IP 地址选择问题 - 提供对网络接口选择的细粒度控制 - 与现有的 `preferredNetworks` 配置无缝协作 - 正则表达式支持允许灵活的模式匹配 - 对现有部署没有破坏性变更 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
