noarter opened a new issue, #9604:
URL: https://github.com/apache/rocketmq/issues/9604

   ### Before Creating the Bug Report
   
   - [x] I found a bug, not just asking a question, which should be created in 
[GitHub Discussions](https://github.com/apache/rocketmq/discussions).
   
   - [x] I have searched the [GitHub 
Issues](https://github.com/apache/rocketmq/issues) and [GitHub 
Discussions](https://github.com/apache/rocketmq/discussions)  of this 
repository and believe that this is not a duplicate.
   
   - [x] I have confirmed that this bug belongs to the current repository, not 
other repositories of RocketMQ.
   
   
   ### Runtime platform environment
   
   centos 7
   
   ### RocketMQ version
   
   4.9.6|5.1.3
   
   ### JDK Version
   
   11
   
   ### Describe the Bug
   
   For a single-node deployment of RocketMQ, both the NameServer and Broker are 
deployed on a machine in the DMZ zone, which has both internal and external 
network IP addresses. Other internal network machines can only recognize the 
internal IP, while external network machines can only access the external IP.  
   
   If the `brokerIP1` in `broker.conf` is configured as the external network 
IP, internal network machines fail to obtain the topic routing information.  
   
   Conversely, if `brokerIP1` is configured as the internal network IP, 
external network machines will similarly report an error of failing to obtain 
the topic routing 
information.(RocketMQ单机部署,namesvr和broker都部署在DMZ区域机器,此机器有内外网两个IP地址,其他内网机器只能识别内网IP,外网机器只能访问外网IP。
 如果将broker.conf中brokerIP1配置为外网IP地址,内网无法获取到topic的路由信息。 
如果是将brokerIP1配置为内网IP地址,外网机器又会同样提示无法获取topic的路由信息。)
   
   ### Steps to Reproduce
   
   For a single-node deployment of RocketMQ, both the NameServer and Broker are 
deployed on a machine in the DMZ zone, which has both internal and external 
network IP addresses. Other internal network machines can only recognize the 
internal IP, while external network machines can only access the external IP.  
   
   If the `brokerIP1` in `broker.conf` is configured as the external network 
IP, internal network machines fail to obtain the topic routing information.  
   
   Conversely, if `brokerIP1` is configured as the internal network IP, 
external network machines will similarly report an error of failing to obtain 
the topic routing 
information.(RocketMQ单机部署,namesvr和broker都部署在DMZ区域机器,此机器有内外网两个IP地址,其他内网机器只能识别内网IP,外网机器只能访问外网IP。
 如果将broker.conf中brokerIP1配置为外网IP地址,内网无法获取到topic的路由信息。 
如果是将brokerIP1配置为内网IP地址,外网机器又会同样提示无法获取topic的路由信息。)
   
   ### What Did You Expect to See?
   
   Internal and external network access
   
   ### What Did You See Instead?
   
   Currently not available.
   
   ### Additional Context
   
   _No response_


-- 
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]

Reply via email to