Introduction to Routing Table
Glossary
Default Routing Table: The routing table which the system creates for VPC by default when creating VPC. The newly established subnet will be bound to the default routing table. The default routing table cannot be deleted or edited, and all the rules in the default routing table are system routes.
Custom Routing Table: The routing table created by users on their own, and can add custom routing rules. Users can create, delete, and edit custom routing tables. Note, system routes in the custom routing table are only visible and cannot be edited.
System Route: The route rule added to the routing table by the system by default. System routes are only visible.
Custom Route: Route rules customized by users. Routing rules include destination address, type of next hop, and next hop. Custom routes can be added, edited, and deleted. The granularity of the routing table is subnet. Each subnet must bind and can only bind one routing table. One routing table can be bound by multiple subnets.
Route Rule Type Routing table rule's next hop type enumeration is as follows:
| Next Hop Type | Next Hop | Explanation |
|---|---|---|
| LOCAL | LOCAL | System Route, every network segment in each VPC will add a LOCAL route, indicating that by default it can circulate within the VPC |
| VPC Peering | vnet id | System Route, added by system by default after VPC is linked |
| Internet Gateway | Internet Gateway | System Route, a designated exit to the public networks. If the cloud resources are bound with EIP, the default exit is EIP; otherwise if the subnet is bound with NAT gateway, the default exit is NAT gateway. |
| Public Services | Public Services | System Route, points to public services provided by SurferCloud, such as DNS, YUM sources, proxy addresses of ULB, health check addresses, etc. |
| CUSTOM | CUSTOM | System route, SPECIAL service within SurferCloud, such as UAEK, etc. business purposes |
| IPSecVPN | vpngw id | Custom Route, after using the IPSec VPN product, the routes added to the VPC pointing to IPSec VPN gateway. The system currently adds it automatically and does not allow customers to add it temporarily |
| Internal VIP | vip id | Custom Route, the next hop is VIP |
| Instance | uhost id (phost id) | Custom Route, the next hop is a cloud host or a physical cloud host |
Usage Restrictions:
-
The destination address segment in the route rules can overlap but cannot be completely identical. If it matches the destination address of multiple route rules at the same time, the priority is determined by the longest prefix matching algorithm.
-
The types of next hop supported by custom route rules are internal VIP and instance (cloud host, physical cloud host).
-
Custom route rules cannot be added to the default routing table. If custom rules are needed, you can create a custom routing table and add custom route rules.
-
Each routing table supports up to 50 custom route rules.
