- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Permissions Management
- Enterprise Routers
- Attachments
- Route Tables
- Associations
- Propagations
- Routes
-
Routing Control
-
Route Policies
- Route Policy Overview
- Creating a Route Policy
- Associating a Route Policy with an Enterprise Router
- Changing the Route Policy Associated with an Enterprise Router
- Disassociating a Route Policy from an Enterprise Router
- Modifying a Route Policy
- Viewing a Route Policy
- Deleting a Route Policy
- Adding a Policy Node to a Route Policy
- Modifying a Policy Node in a Route Policy
- Exporting Policy Nodes in a Route Policy
- Viewing a Policy Node in a Route Policy
- Deleting a Policy Node from a Route Policy
-
IP Prefix Lists
- IP Prefix List Overview
- Creating an IP Prefix List
- Modifying the Name of an IP Prefix List
- Viewing an IP Prefix List
- Deleting an IP Prefix List
- Adding a Prefix Rule to an IP Address Prefix List
- Modifying an IP Prefix Rule in an IP Prefix List
- Exporting Prefix Rules in an IP Prefix List
- Viewing a Prefix Rule in an IP Prefix List
- Deleting a Prefix Rule from an IP Prefix List
-
AS_Path Lists
- AS_Path List Overview
- Creating an AS_Path List
- Modifying the Name of an AS_Path List
- Viewing an AS_Path List
- Deleting an AS_Path List
- Adding an AS_Path Filter to an AS_Path List
- Exporting AS_Path Filters in an AS_Path List
- Viewing an AS_Path Filter in an AS_Path List
- Deleting an AS_Path Filter from an AS_Path List
-
Route Policies
- Sharing
- Flow Logs
- Monitoring and Auditing
- Tags
- Quotas
-
Best Practices
- Summary on Enterprise Router Best Practices
- Connecting VPCs Across Regions Using Enterprise Router and Central Network
- Using Enterprise Router to Isolate VPCs in the Same Region
- Using a Third-Party Firewall to Protect VPCs Connected by Enterprise Routers
- Enabling an On-Premises Data Center to Access Service VPCs Using an Enterprise Router and Transit VPC
- Setting Up a Hybrid Cloud Network Using Enterprise Router and Direct Connect Global DC Gateway
-
Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Global DC Gateway)
- Overview
- Network and Resource Planning
- Process of Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Global DC Gateway)
- Procedure for Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Global DC Gateway)
-
Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Active/Standby Direct Connect Connections (Global DC Gateway)
- Overview
- Network and Resource Planning
- Process of Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Active/Standby Direct Connect Connections (Global DC Gateway)
- Procedure for Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Active/Standby Direct Connect Connections (Global DC Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router, VPN, and Direct Connect (Global DC Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router and Direct Connect (Virtual Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Virtual Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router, VPN, and Direct Connect (Virtual Gateway)
- Allowing VPCs to Share an EIP to Access the Internet Using Enterprise Router and NAT Gateway
- Using Enterprise Router to Migrate the Network Set Up Through VPC Peering
- Using Enterprise Router to Migrate the Network Set Up Through Direct Connect (Global DC Gateway)
- Using Enterprise Router and Central Network to Migrate the Network Set Up Through a Cloud Connection
- API Reference
- FAQs
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Getting Started
- Enterprise Routers
- Attachments
- Route Tables
- Associations
- Propagations
- Routes
- Sharing
- Flow Logs
- Monitoring
- Interconnecting with CTS
- Permissions Management
- Tags
- Quotas
- FAQ
- Change History
-
User Guide (Ankara Region)
- Service Overview
- Getting Started
- Permissions Management
- Enterprise Routers
- Attachments
- Route Tables
- Associations
- Propagations
- Routes
- Sharing
- Flow Logs
- Monitoring
- Quotas
- FAQ
- Change History
- API Reference (Ankara Region)
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Copied.
Configuring Kernel Parameters and Routes for ECS 3
Scenarios
ECS 3 has two NICs, eth0 and eth1. You need to configure kernel parameters and add routes for ECS 3 to allow communications between eth0 and eth1.
ECS 3 runs CentOS 8.0 64-bit. The configuration commands may vary by the OS.
Procedure
- Log in to an ECS.
Multiple methods are available for logging in to an ECS. For details, see Logging In to an ECS.
In this example, use VNC provided on the management console to log in to an ECS.
- Disable the verification of data packet source addresses:
- Run the following command to open the /etc/sysctl.conf file:
vim /etc/sysctl.conf
- Press i to enter the editing mode.
- Add the following content to the end of the file:
net.ipv4.conf.default.rp_filter = 0 net.ipv4.conf.all.rp_filter = 0
- Press Esc to exit and enter :wq! to save the configuration.
- Run the following command for the configuration to take effect:
- Run the following command to check whether verification of data packet source addresses is disabled:
If the value of net.ipv4.conf.all.rp_filter and net.ipv4.conf.default.rp_filter is 0, verification of data packet source addresses is disabled.
- Run the following command to open the /etc/sysctl.conf file:
- Enable the forwarding function.
- Run the following command to open the /etc/sysctl.conf file:
vim /etc/sysctl.conf
- Press i to enter the editing mode.
- Add the following content to the end of the file:
net.ipv4.ip_forward = 1
- Press Esc to exit and enter :wq! to save the configuration.
- Run the following command for the configuration to take effect:
- Run the following command to verify that the forwarding function is enabled.
If the value of net.ipv4.ip_forward is 1, the forwarding function is enabled.
- Run the following command to open the /etc/sysctl.conf file:
- Add routes.
The routes are for forwarding scrubbed traffic from eth1 to VPC 1 and VPC 2.
To add routes for ECSs running CentOS 8.0 or CentOS 7.4, perform the following:
- CentOS 8.0:
- Run the following command to open the NIC configuration file:
- Press i to enter the editing mode.
- Add the following content to the end of the file:
10.1.0.0/16 via 192.168.1.1 10.2.0.0/16 via 192.168.1.1
10.1.0.0/16 is the CIDR block of VPC 1, 10.2.0.0/16 is that of VPC 2, and 192.168.1.1 is the gateway address of eth1.
- Press Esc to exit and enter :wq! to save the configuration.
- Restart ECS 3 for the routes to take effect.
- After the restart is complete, run the following command to verify that the routes are added successfully:
If information similar to the following is displayed, the two routes have been added.
- CentOS 7.4:
- Run the following command to open the NIC configuration file:
- Press i to enter the editing mode.
- Add the following content to the end of the file:
any net 10.1.0.0/16 gw 192.168.1.1 any net 10.2.0.0/16 gw 192.168.1.1
10.1.0.0/16 is the CIDR block of VPC 1, 10.2.0.0/16 is that of VPC 2, and 192.168.1.1 is the gateway address of eth1.
- Press Esc to exit and enter :wq! to save the configuration.
- Run the following command to restart the network service for the configuration to take effect:
- After the restart is complete, run the following command to verify that the routes are added successfully:
If information similar to the following is displayed, the two routes have been added.
- CentOS 8.0:
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