For the complete documentation index, see llms.txt. This page is also available as Markdown.

Bind an Elastic IPv4 Address

You can bind up to 4 elastic IPv4 addresses to a private IPv4.

Procedures

  1. Click the instance name to go to instance Details > Information > Network interface.

  2. Select the private IPv4 you want to bind elastic IPv4 and go to Actions > Bind Elastic IPv4.

  3. Select a desired elastic IPv4 and click Confirm to bind. If no desired elastic IPv4, click New Elastic IPv4 to create a new IPv4. See Create an Elastic IPv4 for detailed steps.

Note

You can also go to Elastic IPv4 > Actions > Bind Private IPv4 to bind the elastic IPv4.

Bypass Mode Configuration Guide

1. Scope and Prerequisites

1.1 Applicable Scenarios

  • Single network interface (NIC) only

  • Supports multiple IPs (up to 254)

  • All IPs must be in Bypass mode

1.2 Supported Operating Systems

  • Ubuntu: 20.04 / 22.04 / 24.04

  • Debian: 10 / 11 / 12

  • CentOS: 7 / 9

  • Rocky Linux: 8.10 / 9.6

1.3 Important Notes

  • A reboot is required after running the script, otherwise the configuration will not take effect

  • Mixed modes are not supported (Bypass Mode + NAT Mode)

2. Operation Steps

  1. Create Command:

Path:

Console → Orchestration Service → Commands → Create Commands

copy and add the following script and create command.

  1. Run Command:

Path:

Console → Elastic Compute → Elastic Compute Instance List → Actions → Operations → Run command → Select the command→ Confirm

Run the created command.

  1. Reboot the Instance

After execution, you must manually reboot the instance.

  1. Add Additional IPs (Optional)

To attach more IPs, repeat:

  • Bind IP

  • Run command

  • Reboot instance

3. Troubleshooting

3.1 Configuration Not Taking Effect

  • Cause: Instance not rebooted

  • Solution: Reboot the instance

3.2 Configuration Failure

  • Ensure all IPs are in Bypass mode

  • Verify the OS is within the supported list

Last updated