Overview
Background
If an ECS has multiple network interfaces, the primary network interface can communicate with external networks by default, but the extended network interfaces cannot. To enable extended network interfaces to communicate with external works, you need to configure policy-based routes for these network interfaces.
Scenarios
- The primary and extended network interfaces on the source ECS are in different subnets of the same VPC.
- The source and destination ECSs are in different subnets of the same VPC and the two ECSs can communicate with each other through primary network interfaces without configuring policy-based routes.
- After policy-based routes are configured for the two network interfaces of the source ECS, both the primary and extended network interfaces can communicate with the destination ECS.
You can select a destination IP address based on service requirements. Before configuring policy-based routes, ensure that the source ECS can use its primary network interface to communicate with the destination ECS.
Operation Guide
You can follow the following operations to configure policy-based routes for Linux and Windows ECSs. For details, see Table 1.
OS |
IP Address Version |
Description |
---|---|---|
Linux |
IPv4 |
An ECS running CentOS 8.0 (64-bit): An ECS running Ubuntu 22.04 server (64-bit): |
IPv6 |
||
Windows |
IPv4 |
An ECS running Windows Server 2012 (64-bit): Configuring IPv4 and IPv6 Policy-based Routes for a Windows ECS with Multiple Network Interfaces |
IPv6 |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot