Network tips

A stable cable connection matters more for a home server than anything in the dashboard.

Cable first, Wi-Fi as standby

Give the cable the fixed address everything points to, and keep Wi-Fi as a fallback with a second address. Example for Netplan in /etc/netplan/01-cloudzh.yaml, with 192.168.1.200 as <server-ip>, 192.168.1.1 as the router and the adapter names from ip -br link. Use your own values:

network:
  version: 2
  renderer: networkd
  ethernets:
    enp3s0f0:
      dhcp4: false
      addresses: [192.168.1.200/24]
      routes: [{ to: default, via: 192.168.1.1, metric: 100 }]
      nameservers: { addresses: [192.168.1.1] }
  wifis:
    wlp2s0:
      optional: true
      dhcp4: false
      addresses: [192.168.1.201/24]
      routes: [{ to: default, via: 192.168.1.1, metric: 600 }]
      nameservers: { addresses: [192.168.1.1] }
      access-points:
        "YourWiFi": { password: "…" }

Apply it safely with sudo netplan try --timeout 300, so a mistake rolls back by itself. With two interfaces in one network, also set:

# /etc/sysctl.d/60-cloudzh-dualnic.conf
net.ipv4.conf.all.arp_ignore = 1
net.ipv4.conf.all.arp_announce = 2

Why not both at once

Bonding cable and Wi-Fi does not work cleanly with a Wi-Fi client, and a single download always uses one path. Your internet line is the limit, not the LAN.

Router

• Reserve the address of the server in the router.
• Forward TCP 443 (dashboard, apps, Plex) and UDP 51820 (VPN). Plex needs TCP only.