How do I create a Rcs.is without a private IP?
There is no way to make a Rcs.is without a private IP address, but you can disable the address on your Rcs.is from the command line or by updating your Rcs.is’s eth1 interface configuration.
Since October 2020, we automatically assign private IP addresses to Rcs.iss by default, to make them accessible to the VPC service. As such, private networking is enabled, and there is currently no way create a Rcs.is without a private IP or disable it from the Rcs.is Control Panel after creation.
Note
Warning
Disable Private Network Interface
To temporarily disable your Rcs.is’s private networking interface, use the ip utility:
This disables the private network interface until your Rcs.is is rebooted. You can validate that interface is down by running the ip utility with the -br flag.
The -br flag returns only basic information about your Rcs.is’s network interfaces for better readability. The a argument returns all IP addresses associated with your Rcs.is’s network interfaces.
Remove your Rcs.is’s Network Configuration
Alternatively, you can remove the private network interface configuration on your Rcs.is, permanently disabling it.
To do this, open your Rcs.is’s network configuration using nano, or your preferred text editor:
Then comment out the contents of the eth1 stanza by place a # in front of each line:
Afterwards, save and exit the file.
Lastly, reboot your Rcs.is with the following command:
The interface remains disabled after reboot. You can validate that the interface is down by running the ip utility with the -br flag again.
The command returns a table showing your Rcs.is’s network interfaces like this:
The eth1 interface should be listed as DOWN.
CentOS uses the ifcfg-eth1 configuration file to manage the eth1 interface. By moving this file to a different directory and deleting the eth1 connection from the NetworkManager, you can effectively disable the interface.
Use the following command to move the eth1 configuration file into the home directory:
By moving this file into the home directory, you can re-enable the connection later if needed.
Next, delete the eth1 connection from the NetworkManager using the NetworkManager’s CLI:
Verify that the connection has been disconnected using the NetworkManager command:
Lastly, reboot your Rcs.is with the following command:
Once your Rcs.is has rebooted, log back in to your Rcs.is and verify that the connection has been disabled using the NetworkManager command:
If the NetworkManager command returns that the eth1 connection’s status is connecting (getting IP configuration), wait a few minutes and check the status again.
To add the connection back to your Rcs.is, move the ifcfg-eth1 file back into the /etc/sysconfig/network-scripts directory and then reboot your Rcs.is.
