Article

Table of Contents
Theme:
Was this article helpful?
Try Vultr Today with

$50 Free on Us!

Want to contribute?

You could earn up to $300 by adding new articles!

How to Configure a Private Network on Fedora CoreOS

Last Updated: Tue, Oct 6, 2020
FAQ Fedora CoreOS Networking

Introduction

When deploying a Vultr cloud server with a private network, you need to manually configure the private adapter. The examples in this guide are for IPv4, however private network interfaces on Vultr VMs support both IPv4 and IPv6. Vultr supports multiple VLANs over a single private network interface with 802.1q tags.

Private Networking Notes

  • When you enable private networking, you may use any RFC1918 private address as long as there are no conflicts with your other instances. Valid addresses include:
    • 10.0.0.0/8
    • 172.16.0.0/12
    • 192.168.0.0/16
  • Private IP addresses in the customer portal are suggestions. You are not required to use the suggested private IP addresses.
  • Private networks can not communicate between locations, regardless of IP addressing. For example, server instances in Miami can not see private networks in Dallas.
  • Private networks do not have DHCP, and you must manually manage your IP address space or install a DHCP server on your private network.
  • For optimal performance, set the private network adapter MTU to 1450 when configuring the NIC at the OS level.
  • We also have guides to configure multiple private networks.

Fedora CoreOS

Use Ignition to configure the VPS for private networking. Before proceeding, make sure you understand how to use private networking at Vultr and create a private network at the deployment location. For more information, refer to our private networking documentation:

To configure a private network, include a YAML stanza in your FCC file that writes your network information. Replace the example IP address with your address.

storage:
  files:
    - path: /etc/NetworkManager/system-connections/ens7.nmconnection
      mode: 0600
      overwrite: true
      contents:
        inline: |
          [connection]
          type=ethernet
          interface-name=ens7

          [ipv4]
          method=manual
          addresses=10.10.10.10/20

The deployed VPS will have two adapters:

  • ens3 on the public network, configured by DHCP.
  • ens7 on the private network, with the static IP address set by Ignition.

See a complete example in our Ignition documentation.

Manage Private Networks via API

The Vultr API offers several endpoints to manage private networks.

Want to contribute?

You could earn up to $300 by adding new articles