Vultr购买并配置额外IPv4地址教程

Last update at ：2024-03-18，Edit by888u

Vultr supports purchasing additional IPv4 addresses for VPS instances. Whether purchasing IPv4 addresses for the IPv6 Only plan or purchasing additional IPs for the regular plan, it can be achieved through the tutorial in this article. After completing the purchase, we need to modify the relevant configuration file to make the new IPv4 address take effect.

1. Purchase IPv4 address with Vultr

Vultr official website: https://www.vultr.com

Log in to the Vultr official website backend, click "Add Another IPv4 Address" under "Settings" to apply for adding an additional IPv4 address:

The price of additional IPv4 in Vultr is $0.003/hour. After confirming it is correct, click "Add IPv4 Address" to start adding:

After the purchase is completed, you can also see under "Settings" that this Vultr VPS has an additional IPv4 in addition to the main IP address (Main IP). We need to manually configure this new IPv4 to take effect. :

2. Vultr configure IPv4 address

Click on the network configuration link in the picture above. This is the official tutorial provided by Vultr for you to configure additional IPv4. Different systems have different configuration methods, which are introduced one by one below.

The following IPv4 configuration file is based on this site's own Vultr instance. You need to make corresponding modifications, or directly open the network configuration link in the picture above.

How to modify files on Linux can refer to "Using vim to edit and create new files under Linux"

CentOS 6, CentOS 7

Modify the file /etc/sysconfig/network-scripts/ifcfg-eth0, the new content is as follows:

DEVICE=eth0 ONBOOT=yes BOOTPROTO=static IPADDR=202.182.119.52 NETMASK=255.255.254.0 GATEWAY=202.182.118.1 DNS1=108.61.10.10 IPV6INIT=yes IPV6ADDR="2001:19f0:7001:1737:5400:03ff:fe5d:15d5/64" IPV6_AUTOCONF="yes" DNS2=2001:19f0:300:1704::6

Modify the file /etc/sysconfig/network-scripts/route-eth0, the new content is as follows:

169.254.0.0/16deveth0

Modify the file /etc/sysconfig/network-scripts/ifcfg-eth0:1, the new content is as follows:

DEVICE=eth0:1 BOOTPROTO=static IPADDR=198.13.46.231 NETMASK=255.255.255.255 ONBOOT=yes

Restart neural network:

service network restart

CentOS 8

Modify the file /etc/sysconfig/network-scripts/ifcfg-ens3, the new content is as follows:

TYPE="Ethernet" DEVICE="ens3" ONBOOT="yes" BOOTPROTO="none" IPADDR=202.182.119.52 PREFIX=23 GATEWAY=202.182.118.1 DNS1=108.61.10.10 IPADDR1=198.13.46.231 PREFIX1=32 IPV6INIT="yes" IPV6_AUTOCONF="yes"

Restart the connection:

nmcli con load /etc/sysconfig/network-scripts/ifcfg-ens3 nmcli con up 'System ens3'

Debian 7, Debian 8

Modify the file /etc/network/interfaces, the new content is as follows:

auto lo iface lo inet loopback autoeth0 iface eth0 inet static address 202.182.119.52 netmask 255.255.254.0 gateway 202.182.118.1 dns-nameservers 108.61.10.10 post-up ip route add 169.254.0.0/16 dev eth0 iface eth0 inet6 static address 2001:19f0:7001:1737:5400:03ff:fe5d:15d5 netmask 64 dns-nameservers 2001:19f0:300:1704::6 autoeth0:1 iface eth0:1 inet static address 198.13.46.231 netmask 255.255.255.255

Restart neural network:

systemctl restart networking.service

Debian 9, Debian 10

Modify the file /etc/network/interfaces, the new content is as follows:

auto lo iface lo inet loopback auto ens3 iface ens3 inet static address 202.182.119.52 netmask 255.255.254.0 gateway 202.182.118.1 dns-nameservers 108.61.10.10 post-up ip route add 169.254.0.0/16 dev ens3 iface ens3 inet6 static address 2001:19f0:7001:1737:5400:03ff:fe5d:15d5 netmask 64 dns-nameservers 2001:19f0:300:1704::6 auto ens3:1 iface ens3:1 inet static address 198.13.46.231 netmask 255.255.255.255

Restart neural network:

systemctl restart networking.service

Ubuntu 12.xx – Ubuntu 15.xx

Modify the file /etc/network/interfaces, the new content is as follows:

Restart the service:

ifup eth0

Ubuntu 16.xx, Ubuntu 17.04

Modify the file /etc/network/interfaces, the new content is as follows:

Restart the service:

ifup ens3

Ubuntu 17.10, Ubuntu 18.xx, Ubuntu 19.xx, Ubuntu 20.xx

Modify the file /etc/netplan/10-ens3.yaml, the new content is as follows:

network: version: 2 renderer: networkd ethernets: ens3: dhcp4: no addresses: [202.182.119.52/23,198.13.46.231/32,'2001:19f0:7001:1737:5400:03ff:fe5d:15d5/64'] gateway4: 202.182.118.1 nameservers: addresses: [108.61.10.10] routes: - to: 169.254.0.0/16 via: 202.182.118.1 metric: 100

Restart the service:

netplan apply

3. Restart Vultr

Finally, we need to restart Vultr in the control panel for this new IPv4 address configuration to take effect:

The above is the tutorial shared by this site on how to purchase additional IPv4 addresses and complete the configuration for Vultr. Generally speaking, it is quite complicated and requires us to manually modify the relevant files. If you have not registered a Vultr account, you can participate in the Vultr new user discount (sign up to get 50 US dollars): https://www.vultr.com/promo/try50/. For more Vultr tutorials, please refer to "Vultr VPS Special Topic: Vultr Discounts" Code sorting, speed test address sharing, data center recommendation."

Recommended site search: US unlimited content hosting, site group server rental, free overseas server, US server, Hong Kong hosting, European server, high-defense IP rental, Korean cheap server, domain name registration query, expired registered domain name ,

Tutorial on purchasing and configuring additional IPv4 addresses with Vultr

Tutorial on purchasing and configuring additional IPv4 addresses with Vultr

1. Purchase IPv4 address with Vultr

2. Vultr configure IPv4 address

3. Restart Vultr

Related

888uV

Populare

Random Tags