Static IP with systemd-networkd
Recent Raspberry Pi OS Lite images dropped dhcpcd and use systemd-networkd to manage interfaces. There are workarounds to put dhcpcd back, but they’re more trouble than they’re worth — systemd-networkd is well-supported, declarative, and ships with the OS.
Configure the interface
Section titled “Configure the interface”The FR201’s PoE-capable port is eth0; the standard LAN port is eth1. The example below pins eth0 — swap the interface name if you wired into the other port.
-
Create a network unit file in
/etc/systemd/network/. The numeric prefix controls processing order — anything between10-and90-is fine for a single static config:Create the unit file sudo nano /etc/systemd/network/10-eth0-static.network -
Add the configuration. Replace the addresses with values that match your network:
/etc/systemd/network/10-eth0-static.network [Match]Name=eth0[Network]Address=192.168.1.50/24Gateway=192.168.1.1DNS=192.168.1.1 1.1.1.1 -
Save (Ctrl+O, Enter) and exit (Ctrl+X).
-
Make sure
systemd-networkdis enabled so the change survives a reboot, then restart it to apply:Enable and restart systemd-networkd sudo systemctl enable systemd-networkdsudo systemctl restart systemd-networkd
Verify the new address
Section titled “Verify the new address”ip addr show eth0You can also ask networkctl for the high-level state of every managed interface:
networkctl statusA healthy result looks like State: routable (configured) with the address you set listed under Address:.
- Both ports: if you want both Ethernet ports configured, create a second unit file (for example
10-eth1-static.network) withName=eth1and a different address. - DHCP fallback: replace the static
Address=andGateway=lines withDHCP=yesto revert to DHCP on a single interface without uninstalling anything. - Resolved DNS: on Lite images,
systemd-resolvedmay not be enabled. If DNS lookups fail, install or enable it (sudo systemctl enable --now systemd-resolved) so theDNS=entries in your unit file are honored.