Contents
Do you need to set up a bridge in systemd?
If you are running virtual machines, you probably have set up a bridge in your interfaces file. Since that is no longer used, you need to set up a bridge using systemd-networkd. Fortunately this is very easy. First you need to define the virtual network device using a .netdev file (in /etc/systemd/network of course).
Is there a command to restart the network?
This should update your network changes. But if your network is not managed by NetworkManager, this command will do no change to your interface configuration. Use this command with precaution as this can bring down your active interface which you may be using for SSH connections locking you out of the system.
How to force new configuration without reboot?
On my Arch box, I had a network bridge. The goal was to remove the bridge and to only use the network adapter not bridged. In order to do so, I removed all the *.netdev and *.network configuration files under /etc/systemd/network and replaced them with one simple file:
What to do after systemd networkd is set up?
If you currently have a network running using /etc/network/, move the interfaces file there to another name so that it won’t be used after systemd-networkd is set up: Next enable systemd-networkd.
Is there a way to build a network bridge?
As of systemd 210 and up, a special service called systemd-networkd is available for network configuration. This service can handle bridge construction. The basic procedure of creating a network configuration with systemd-networkd is creating several .network and .netdev files. First, create a bridge.
Which is the IP address for systemd networkd?
This tells systemd-networkd to use eth0 (which was set up by udev) and assign it an address using DHCP. For a static IP, lan0.network could be: I recommend a reboot at this point to remove the currently running network and to ensure that your network comes up properly.