Deze pagina is nog niet beschikbaar in uw eigen taal. We werken er hard aan om meer taalversies toe te voegen. Bedankt voor uw steun.
- What's New
- Function Overview
- Service Overview
-
Getting Started
- Allowing a Private Network to Access the Internet Using SNAT
- Allowing Internet Users to Access a Service in a Private Network Using DNAT
- Allowing On-Premises Servers to Communicate with the Internet
- Using Private NAT Gateways to Enable Communications Between Cloud and On-premises Networks
- Using Multiple Public NAT Gateways Together in Performance-Demanding Scenarios
- Change History
-
User Guide
- Public NAT Gateways
- Private NAT Gateways
- Managing NAT Gateway Tags
- Monitoring
- Auditing
- Change History
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- V2 APIs of Public NAT Gateways
- API v2.0
- Private Nat API
- Permissions Policies and Supported Actions
- Common Parameters
- Change History
-
FAQs
-
Public NAT Gateways
- What Is the Relationship Between a VPC, Public NAT Gateway, EIP Bandwidth, and ECS?
- How Does a Public NAT Gateway Offer High Availability?
- Which Ports Cannot Be Accessed?
- What Are the Differences Between Using a Public NAT Gateway and Using an EIP for an ECS?
- What Should I Do If I Fail to Access the Internet Through a Public NAT Gateway?
- Can I Change the VPC for a Public NAT Gateway?
- Does Public NAT Gateway Support IPv6 Addresses?
- What Security Policies Can I Configure to Implement Access Control If I Use a Public NAT Gateway?
- What Can I Do If Connection Between My Servers and the Internet Fails After I Add SNAT and DNAT Rules?
-
Private NAT Gateways
- How Do I Troubleshoot a Network Failure After a Private NAT Gateway Is Configured?
- How Many Private NAT Gateways Can I Create in a VPC?
- Can I Increase the Numbers of SNAT and DNAT Rules Supported by a Private NAT Gateway?
- Can an SNAT and DNAT Rule of a Private NAT Gateway Share the Same Transit IP Address?
- Can Private NAT Gateways Translate On-premises IP Addresses Connected to the Cloud Through Direct Connect?
- What Are the Differences Between Private NAT Gateways and Public NAT Gateways?
- How Is Private NAT Gateway Billed?
- Can a Private NAT Gateway Be Used Across Accounts?
-
SNAT Rules
- Why Do I Need SNAT?
- What Are SNAT Connections?
- What Is the Bandwidth of a Public NAT Gateway Used by a Server to Access the Internet? How Do I Configure the Bandwidth?
- How Do I Resolve Packet Loss or Connection Failure Issues When Using a NAT Gateway?
- What Should I Do If My ECS Fails to Access a Server on the Public Network Through a Public NAT Gateway?
- What Are the Relationships and Differences Between the CIDR Blocks in a NAT Gateway and in an SNAT Rule?
- DNAT Rules
-
Public NAT Gateways
- SDK Reference
Show all
Step 4: Create a Route Table
Scenarios
Each public NAT gateway requires its unique route table. Create the second route table for the VPC.
Prerequisites
A route table can be created in the VPC.
Procedure
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project.
- Click Service List in the upper left corner. Under Networking, select Virtual Private Cloud.
- In the navigation pane on the left, choose Route Tables.
- In the upper right corner, click Create Route Table. On the displayed page, configure required parameters.
Table 1 Parameter descriptions Parameter
Description
Example Value
Name
(Mandatory) The name of the route table
Enter up to 64 characters. Only letters, digits, underscores (_), hyphens (-), and periods (.) are allowed. Spaces are not allowed.
rtb-001
VPC
(Mandatory) The VPC that the route table belongs to
vpc-001
Description
(Optional) Supplementary information about the route table
Enter up to 255 characters. Angle brackets (< or >) are not allowed.
N/A
Route Settings
Routes contained in the route table
You can add a route when creating the route table or after the route table is created.
You can click + to add more routes.
N/A
- Click OK.
A message indicating that subnets can now be associated with the created route table is displayed. Perform the following steps to associate the other subnet of the VPC with the route table:
- Click Associate Subnet.
The Associated Subnets tab is displayed.
- Click Associate Subnet and select the second subnet created in Step 1: Create a VPC and Two Subnets.
- Click OK.
- Click Associate Subnet.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.