Configure networking#
Hostnames and IP addresses#
Update the server’s Pillar file:
network:
host_id: ocp12
ipv4: 198.51.100.34
ipv6: 2001:db8::12
ipv6
is optional.
Netplan#
Netplan uses YAML files for configuration. Configurations are available for Linode and other hosts. The configuration is written to /etc/netplan/10-salt-networking.yaml
.
Linode#
This configuration disables automatic IP configuration and configures static networking on IPv4 and IPv6.
Note
By default, a Linode server listens on – and prefers traffic to – its default IPv6 address. We use our own IPv6 block – 2a01:7e00:e000:02cc::/64
– to improve IP reputation and email deliverability.
One-time setup
Open a support ticket with Linode to request an IPv6 /64 block:
Hello,
Please provision an IPv6 /64 block for our account.
Thank you,
A /64 block is requested, because spam blocklists use /64 ranges.
Update the server’s Pillar file:
network:
host_id: ocp12
ipv4: 198.51.100.34
ipv6: 2001:db8::12
netplan:
template: linode
addresses:
- 2001:db8::32/64 # SLAAC
gateway4: 198.51.100.1
gateway6: fe80::1
To fill in the above, from the Network tab on the Linode’s page, collect:
ipv4
The Address with a Type of IPv4 – Public
addresses
The Address with a Type of IPv6 – SLAAC, suffixed by “/64”
gateway4
The Default Gateway with a Type of IPv4 – Public
gateway6
The Default Gateway with a Type of IPv6 – SLAAC
For ipv6
, use our IPv6 block with the hostname’s digits as the final group of the IPv6 address: for example, 2a01:7e00:e000:02cc::12 for ocp12.
Other hosting providers#
Note
This step is optional. Only override a Netplan configuration if necessary. For example, Hetzner’s installimage script creates a configuration file.
In the server’s Pillar file, set network.netplan.template
to custom
and set network.netplan.configuration
:
network:
host_id: ocp12
ipv4: 198.51.100.34
ipv6: 2001:db8::12
netplan:
template: custom
configuration: |
network:
version: 2
renderer: networkd
ethernets:
eth0:
addresses:
- 198.51.100.34/32
...
Time servers#
systemd-timesyncd synchronizes the local system clock with remote NTP servers.
You should select NTP servers from the NTP Pool Project that are close to the server’s location, in order to mitigate network latency and improve time accuracy.
For example, to use the NTP servers in Finland, add to the server’s Pillar file:
ntp:
- 0.fi.pool.ntp.org
- 1.fi.pool.ntp.org
- 2.fi.pool.ntp.org
- 3.fi.pool.ntp.org
By default, the NTP servers in the UK are used.