[Solved] Creating a Bridge With Systemd-Networkd

brando56894 · 2016-05-02 00:13:11

I have a few KVMs running on my server and I can't seem to figure out how to get a persistent bridge to work. I created one with iproute2 tools and it works fine, and systemd-networkd also creates it fine, but the latter never assigns it the IP address I want, and I can't seem to figure out what the reason is.

This is how I want everything to be setup

3: left: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbridge state UP group default qlen 1000
    link/ether 0c:c4:7a:76:c7:1f brd ff:ff:ff:ff:ff:ff

11: vmbridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 0c:c4:7a:76:c7:1f brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.6/24 brd 192.168.1.255 scope global vmbridge
       valid_lft forever preferred_lft forever

12: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbridge state UNKNOWN group default qlen 1000
    link/ether fe:54:00:13:d8:ff brd ff:ff:ff:ff:ff:ff

16: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbridge state UNKNOWN group default qlen 1000
    link/ether fe:54:00:a9:2c:92 brd ff:ff:ff:ff:ff:ff

Using this tutorial I created the following files

/etc/systemd/network/vmbridge.netdev

[NetDev]
Name=vmbridge
Kind=bridge

/etc/systemd/network/left.network

[Match]
Name=left

[Network]
Bridge=vmbridge

/etc/systemd/network/vmbridge.network

[Match]
Name=vmbridge

[Network]
Address=192.168.1.6/24
DNS=192.168.1.1
Gateway=192.168.1.1
Broadcast=192.168.1.255

After restarting systemd-networkd the bridge and associated devices are created successfully, but the vmbridge has no IP. I tried doing it with DHCP also, as they did in the tutorial, but it still didn't work.

Last edited by brando56894 (2016-05-03 17:27:17)

firecat53 · 2016-05-02 01:06:57

Is your 'left' network an actual network device? For my sever, the 'eno1' ethernet device is setup equivalent to your 'left' network, and my setup works fine.

Scott

brando56894 · 2016-05-02 03:45:47

yes, left is an actual NIC.

djgera · 2016-05-02 22:38:52

enable debug log level in networkd to see what happens (and sometimes due race conditions, enabling debug workaround these kinds of networkd bugs, I remember that I least reported two bugs that at today the "fix" is enabling debug)

/etc/systemd/system/systemd-networkd.service.d/debug.conf

[Service]
Environment=SYSTEMD_LOG_LEVEL=debug

brando56894 · 2016-05-03 17:27:04

It seems all I needed was a reboot, I was trying to do it without a reboot because I had a bunch of things running, now I needed to reboot and when the system came up everything was applied correctly.

djgera · 2016-05-03 22:14:40

Nice, but reboot is not needed, something was wrong.

brando56894 · 2016-05-03 23:23:35

Yea something was obviously screwed up.

Arch Linux

#1 2016-05-02 00:13:11

[Solved] Creating a Bridge With Systemd-Networkd

#2 2016-05-02 01:06:57

Re: [Solved] Creating a Bridge With Systemd-Networkd

#3 2016-05-02 03:45:47

Re: [Solved] Creating a Bridge With Systemd-Networkd

#4 2016-05-02 22:38:52

Re: [Solved] Creating a Bridge With Systemd-Networkd

#5 2016-05-03 17:27:04

Re: [Solved] Creating a Bridge With Systemd-Networkd

#6 2016-05-03 22:14:40

Re: [Solved] Creating a Bridge With Systemd-Networkd

#7 2016-05-03 23:23:35

Re: [Solved] Creating a Bridge With Systemd-Networkd

Board footer