Skip to content

Network Setup: Investigate Tap Device Creation for type="ethernet" #134

@phip1611

Description

@phip1611

First of all: this has a low priority, as our pipeline is currently stable (because of #124).

Objective of this ticket is to investigate if our network setup we have is correct at all or a "works by accident". This is especially important if we want to upstream general ch libvirt improvements soon.

Why do we use <target dev="tap1" rather than <source dev="tap1" for network devices of type ethernet. By definition, type ethernet is for externally provided network devices. But we use it in a way that libvirt still create these devices and a systemd-networkd rule then attaches the right IP to it once the device appears.

Although this works, it technically sounds broken. Please investigate and perhaps refactor!

More info also in this thread: #127.

Metadata

Metadata

Assignees

No one assigned

    Labels

    quality-of-lifeQualitfy of Life (QoL) improvements for developers.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions