Skip to content

Networking

IPv4 Configuration

We support both dynamic (DHCP) and static IPv4 configuration. It will automatically be set to DHCP if you install your server with one of our templates. However, you may change this to static configuration if you prefer to not rely on the DHCP server. The necessary details (gateway, netmask) are available in the control panel under the network management section.

IPv6 Configuration

We do not support automatic (SLAAC) or dynamic (DHCPv6) IPv6 assignment, it needs to be configured statically. If you choose to enable IPv6 when you first create your server, it will automatically be configured via cloud-init. However, manual configuration is needed if you choose to enable it after your server has been created, or if you install your OS via ISO.

You will be assigned a public /64 IP block. The ::1 address within this block needs to be configured on your primary network interface eth0. Please see the configuration examples below.

Tip

The entire /64 subnet is routed towards your VM and the ::1 address, so it's not necessary to configure additional addresses on the interface in order to receive traffic to them.

  1. Identify the interface name: ip -o link | grep 00:20
  2. Create a new interfaces.d file for the IPv6 config. Replace 2a0e:dc0:d0d0:c0de::1/64 with your unique IPv6 block and replace eth0 with your interface name, if different.
    /etc/network/interfaces.d/90-ipv6
    iface eth0 inet6 static
        address 2a0e:dc0:d0d0:c0de::1/64
        gateway fe80::1
    
  3. Restart the networking service: sudo systemctl restart networking
  4. Confirm it's configured: ip -6 a
  1. Identify the interface name: ip -o link | grep 00:20
  2. Create a new netplan file for the IPv6 config. Replace 2a0e:dc0:d0d0:c0de::1/64 with your unique IPv6 block and change eth0 to your interface's name, if different.
    /etc/netplan/90-ipv6.yaml
    network:
        ethernets:
            eth0:
                addresses:
                - 2a0e:dc0:d0d0:c0de::1/64
                gateway6: fe80::1
        version: 2
    
  3. Enable the new config: sudo netplan apply
  4. Confirm it's configured: ip -6 a
  1. Identify the interface name: ip -o link | grep 00:20
  2. Append the IPv6 configuration (keep the current configuration) to the already existing configuration file as per below. The file name depends on your interface name. Replace 2a0e:dc0:d0d0:c0de::1/64 with your unique IPv6 block.
    /etc/sysconfig/network-scripts/ifcfg-eth0
    IPV6ADDR=2a0e:dc0:d0d0:c0de::1/64
    IPV6INIT=yes
    IPV6_DEFAULTGW=fe80::1%eth0
    
  3. Restart the network service: sudo systemctl restart network
  4. Confirm it's configured: ip -6 a

Private Networking

Info

If you enable private networking on your server after it has been setup, you must reboot it by clicking the reboot button in the control panel in order to attach the interface.

If you enable Private Networking on your VM you will get an additional network interface that you can use for traffic between your own VMs in the same region. You cannot access any external networks through this interface. It is isolated with its own unique VLAN/VXLAN and you can assign any IPv4/IPv6 address to it. We do not offer any automated address assignment or DHCP on these networks. If you configure all your servers to the same subnet/broadcast domain you don't have to set any manual routes or gateway, e.g 192.168.10.1/24, 192.168.10.2/24 etc. See below for configuration examples.

If you add it upon creation of your VM, or if you reinstall your VM once it is enabled, the interface will automatically be named eth1. You can also identify it by its MAC address, it always starts with 00:22. You can use jumbo frames (MTU 9000) on this interface for maximum throughput.

Bandwidth is unlimited and not counted towards your server's monthly bandwidth usage. Following is a general configuration guide. Note that your configuration may be different, depending on your OS and it's version.

  1. Identify the interface name: ip -o link | grep 00:22
  2. Create a new interfaces.d file. Change eth1 to your interface's name, if different.
    /etc/network/interfaces.d/90-private
    iface eth1 inet static
        address 192.168.10.1/24
    
  3. Restart the networking service: sudo systemctl restart networking
  1. Identify the interface name and MAC address: ip -o link | grep 00:22
  2. Create a new netplan file with your 00:22 MAC address. Change eth1 to your interface's name, if different.
    /etc/netplan/90-private.yaml
    network:
        ethernets:
            eth1:
                addresses:
                - 192.168.10.1/24
                match:
                    macaddress: 00:22:xx:xx:xx:xx
        version: 2
    
  3. Restart the networking service: sudo systemctl restart networking
  1. Identify the interface name and MAC address: ip -o link | grep 00:22
  2. Create a new ifcfg file with your 00:22 MAC address. Change eth1 to your interface's name, if different.
    /etc/sysconfig/network-scripts/ifcfg-eth1
    BOOTPROTO=static
    DEVICE=eth1
    HWADDR=00:22:xx:xx:xx:xx
    ONBOOT=yes
    TYPE=Ethernet
    IPADDR=192.168.10.1
    NETMASK=255.255.255.0
    
  3. Restart the network service: sudo systemctl restart network

BGP

Info

Please note that this is under active development and may not be available in all locations yet. You should only try to configure this if you have been in contact with our support team to have it enabled.

Setup a BGP session using a router software such as Bird using the details below.

Our side

  • ASN: 65473
  • IPv4: 169.254.169.254
  • IPv6: 2605:4840:ffff::179

Your side

  • IPv4: The main IP address of your server
  • IPv6: The ::1 address of your server's /64 subnet
  • eBGP multihop 2
  • Password provided by our support team

We are advertising default route for both v4 and v6.

Tip

You can announce more specific subnets within your allowed prefixes up to /32 (IPv4) or /128 (IPv6). This means you can use IPs from one prefix on multiple servers in same location. Please make sure to also announce the full subnet (as per your LOA) from at least one server so that it gets announced out on the internet.

Bandwidth Usage

Both incoming and outgoing traffic is counted towards the bandwidth usage of your VM (traffic on the private network interface is not counted). You can see the limit in the control panel (cloud.hosthatch.com). The counter resets on the 1st day of each calendar month, no matter what your billing period is.