- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Public NAT Gateway Operation Guide
- Private NAT Gateway Operation Guide
- Practical Tutorial
- Enabling Cross-VPC Access to Public Network via Standard NAT Gateway
- Enabling Mutual Access between a Specified VPC Subnet and Public Network Resources via Private NAT Gateway
- Enabling Secure Mutual Access with Public Network via Public CLB and NAT Gateway
- Adjusting the Priorities of NAT Gateways and EIPs
- API Documentation
- FAQ
- Service Level Agreement
- Contact Us
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Public NAT Gateway Operation Guide
- Private NAT Gateway Operation Guide
- Practical Tutorial
- Enabling Cross-VPC Access to Public Network via Standard NAT Gateway
- Enabling Mutual Access between a Specified VPC Subnet and Public Network Resources via Private NAT Gateway
- Enabling Secure Mutual Access with Public Network via Public CLB and NAT Gateway
- Adjusting the Priorities of NAT Gateways and EIPs
- API Documentation
- FAQ
- Service Level Agreement
- Contact Us
- Glossary
Adjusting the Priorities of NAT Gateways and EIPs
Last updated: 2024-08-01 14:13:54
Description of NAT Gateway and EIP Priorities
When a subnet is associated with a NAT gateway, the CVMs having public IPs (or EIPs) in the subnet will access the Internet through the NAT gateway by default, because the priority of the exact match route is higher than that of the public IP. However, you can set a routing policy to allow the CVMs to access the Internet through their public IPs.
Directions
1. View the route table associated with the subnet where the CVM is located. Make sure that there is a routing policy pointing to the NAT gateway, to ensure that the CVMs having no public IPs in the subnet can still access the Internet through the NAT gateway.
2. Add a routing policy with the next hop type set to Public IP of the CVM and enter the destination.
Destination: Enter the specific public network IP range to be accessed by the business or the default route (0.0.0.0/0, indicating that the destination is not in the route table and all data packets are transmitted using the default route).
Next hop type: Public IP of the CVM.
Note
When this routing policy is configured with the same destination as the routing rules pointing to the NAT gateway, the CVM, and the public gateway, this route will be matched first.
This routing policy affects all subnets associated with the route table (please confirm the impact of the operation). In other words, the CVMs having public IPs (or EIPs) in these subnets will access the Internet through their respective public IP instead of the NAT gateway.
In the subnets associated with the route table, the CVMs having no public IPs can still access the Internet through the NAT gateway, without being affected.
Yes
No
Was this page helpful?