Home / ubuntu / Questions / 1054034
Accepted
tudor -Reinstate Monica-
Asked: 2018-07-11 16:11:19 +0800 CST

Netplan - How to describe veth peer links?

  • 772

I want to peer connect between two bridges in my netplan configuration.

Under iproute2 the commands would be:

ip link add dev vethb1 type veth peer name vethb2       
brctl addif br1 vethb1
brctl addif br2 vethb2

I'm porting from OpenVSwitch, so it's possible I'm thinking about this the wrong way.

Unfortunately, the netplan documentation doesn't seem to cover all device types, particularly veth. Although it does mention veth in terms of matching, so there's some part of netplan that must know what it means.

I've tried doing a vlan with no id but it expects an id.

Creating an ethernet doesn't seem to accept a type or peer attribute. Networkd calls this kind but that isn't an accepted key either.

What does a veth peer link look like in a netplan config?

networking netplan

2 Answers

  1. Best Answer

    @slangasek is correct. As of 0.39 there is no support in the netplan yaml. However, netplan is based on systemd-networkd and plays nicely with it. So here's the solution I came up with:

    Create a file called /etc/systemd/network/25-veth-b1b2.netdev with the contents:

    [NetDev]
Name=vethb1
Kind=veth
[Peer]
Name=vethb2

    Then add to your /etc/netplan/01-netcfg.yaml

    Under:

    ethernets:

    Add:

        vethb1: {}
    vethb2: {}

    What this does is tells netplan to expect interfaces from somewhere called vethb1 and vethb2. ({} is an empty match. match: {} works also, but leaving it blank or just match: causes a parsing error.)

    Then you can add those interfaces to your bridge:

    bridges:
  b1:
    interfaces: [vethb1]
  b2:
    interfaces: [vethb2]

    Then rebuild your netplan config and restart systemd-networkd:

    $ netplan generate
$ service systemd-networkd stop
$ service systemd-networkd start
    • 5

  2. As of netplan 0.39, there is no support for configuring veth devices through netplan yaml. This is currently under consideration for implementation in a future release.

    • 1