Enabling Internet Connectivity for an ECS Without an EIP¶
Scenarios¶
To ensure platform security and conserve EIPs, EIPs are assigned only to specified ECSs. ECSs without EIPs cannot access the Internet directly. If these ECSs need to access the Internet (for example, to perform a software upgrade or install a patch), you can select an ECS with an EIP bound to function as a proxy ECS, providing an access channel for these ECSs.
Note
NAT Gateway is recommended, which provides both the SNAT and DNAT functions for your ECSs in a VPC and allows the ECSs to access or provide services accessible from the Internet. For details, see NAT Gateway User Guide.
Prerequisites¶
A proxy ECS with an EIP bound is available.
The IP address of the proxy ECS is in the same network and same security group as the ECSs that need to access the Internet.
Linux Proxy ECS¶
In this example, the proxy ECS runs CentOS 6.5.
Log in to the management console.
Click
in the upper left corner and select your region and project.Under Computing, click Elastic Cloud Server.
In the search box above the upper right corner of the ECS list, enter the proxy ECS name for search.
Click the name of the proxy ECS. The page providing details about the ECS is displayed.
On the Network Interfaces tab, click
. Then, disable Source/Destination Check.By default, the source/destination check function is enabled. When this function is enabled, the system checks whether source IP addresses contained in the packets sent by ECSs are correct. If the IP addresses are incorrect, the system does not allow the ECSs to send the packets. This mechanism prevents packet spoofing, thereby improving system security. However, this mechanism prevents the packet sender from receiving returned packets. Therefore, disable the source/destination check.
Log in to the proxy ECS.
For more details, see Login Overview.
Run the following command to check whether the proxy ECS can access the Internet:
ping www.google.com
The proxy ECS can access the Internet if information similar to the following is displayed:
64 bytes from 220.181.111.148: icmp_seq=1 ttl=51 time=9.34 ms 64 bytes from 220.181.111.148: icmp_seq=2 ttl=51 time=9.11 ms 64 bytes from 220.181.111.148: icmp_seq=3 ttl=51 time=8.99 ms
Run the following command to check whether IP forwarding is enabled on the proxy ECS:
cat /proc/sys/net/ipv4/ip_forward
Run the following command to open the IP forwarding configuration file in the vi editor:
vi /etc/sysctl.conf
Press i to enter editing mode.
Set the net.ipv4.ip_forward value to 1.
Set the net.ipv4.ip_forward value to 1.
Note
If the sysctl.conf file does not contain the net.ipv4.ip_forward parameter, run the following command to add it:
echo net.ipv4.ip_forward=1 >> /etc/sysctl.conf
Press Esc, type :wq, and press Enter.
The system saves the configurations and exits the vi editor.
Run the following command to make the modification take effect:
sysctl -p /etc/sysctl.conf
Run the following commands to configure default iptables rules:
iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT
Caution
Running iptables -P INPUT ACCEPT will set default INPUT policy to ACCEPT, which poses security risks. You are advised to set security group rules to restrict inbound access.
Run the following command to configure source network address translation (SNAT) to enable ECSs in the same network segment to access the Internet through the proxy ECS:
iptables -t nat -A POSTROUTING -o eth0 -s subnet/netmask-bits -j SNAT --to nat-instance-ip
For example, if the proxy ECS is in network 192.168.125.0, the subnet mask has 24 bits, and the private IP address is 192.168.125.4, run the following command:
iptables -t nat -A POSTROUTING -o eth0 -s 192.168.125.0/24 -j SNAT --to 192.168.125.4
Note
To retain the preceding configuration even after the ECS is restarted, run the vi /etc/rc.local command to edit the rc.local file. Specifically, copy the rule described in step 16 into rc.local, press Esc to exit Insert mode, and enter :wq to save the settings and exit.
Run the following commands to save the iptables configuration and make it start up automatically upon ECS startup:
service iptables save
chkconfig iptables on
Run the following command to check whether SNAT has been configured:
iptables -t nat --list
SNAT has been configured if information similar to Figure 1 is displayed.
Figure 1 Successful SNAT configuration¶
Add a route.
Log in to the management console.
Click
in the upper left corner and select your region and project.Under Network, click Virtual Private Cloud.
Choose Route Tables in the left navigation pane. In the route table list, click a target route table. On the displayed page, click Add Route.
Set route information on the displayed page.
Destination: indicates the destination network segment. The default value is 0.0.0.0/0.
Next Hop: indicates the private IP address of the proxy ECS.
You can obtain the private IP address of the ECS on the Elastic Cloud Server page.
To delete the added iptables rules, run the following command:
iptables -t nat -D POSTROUTING -o eth0 -s subnet/netmask-bits -j SNAT --to nat-instance-ip
For example, if the proxy ECS is in network segment 192.168.125.0, the subnet mask has 24 bits, and the private IP address is 192.168.125.4, run the following command:
iptables -t nat -D POSTROUTING -o eth0 -s 192.168.125.0/24 -j SNAT --to 192.168.125.4