How to Configure a Private Network on OpenBSD

Introduction

Vultr provides many flexible networking options for your cloud servers. In addition to the public network attached to every Vultr instance, you can configure up to five private networks per location. Private networks allow instances within a location to communicate without exposing the traffic to the public internet.

Note: Your network adapter names may not match the examples. See our article How to Find the Network Adapter Names for a Vultr Cloud Server.

Please see the guide How to Configure a Private Network at Vultr for general information about Vultr's private network feature.

Private networks do not have DHCP. When deploying a Vultr cloud server with private networking, you must manually configure the private adapters or supply your own DHCP server. We provide network configuration examples for many popular operating systems, pre-configured for your instance's IP addresses. You can find these by navigating to the settings screen (1) for your server, then selecting IPv4 (2). Follow the networking configuration link (3) to view the configuration examples.

The configurations in the customer portal are your best source of specific information. Please see below for step-by-step instructions with generic examples.

OpenBSD 6.x

1. Verify that private networking is enabled for your cloud server. Your private network device is vio1. Your public network device is vio0.

2. Change 10.10.10.3 to the selected private IP address and replace the contents of /etc/hostname.vio1 with:

   inet 10.10.10.3 255.255.240.0
   !ifconfig vio1 mtu 1450
   

3. Restart the interface or reboot.

   # sh /etc/netstart vio1
   
   # reboot
   

Manage Private Networks via API

The Vultr API offers several endpoints to manage private networks.