[systemd-bugs] [Bug 81713] New: Adding VLAN causes main interface to be down

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=81713

          Priority: medium
            Bug ID: 81713
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: Adding VLAN causes main interface to be down
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: freedesktop at techmunk.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

I have installed a fresh archlinux install in virtualbox, installing only base,
base-devel, and grub.

I've then built systemd-git pkgbuild and installed.

The following is the simplest configuration I've found that does not work.
The vlan gets added, however all of the interfaces are down, and need to be
bought up manually. I've tried with a second vlan, to the same effect. The only
way I've found to have the main interface come up on boot, is to not include
the vlans.

CONFIG:
----------------------------
enp0s3.network
----------------------------
[Match]
Name=enp0s3

[Network]
VLAN=vlan2
----------------------------


----------------------------
vlan2.netdev
----------------------------
[NetDev]
Name=vlan2
Kind=vlan

[VLAN]
Id=2
----------------------------


----------------------------
vlan2.network
----------------------------
[Match]
Name=vlan2

[Network]
Address=192.168.6.1/24
----------------------------

I've been able to replicate this on two other archlinux machines.

The output of "ip a" with the above configuration after boot is below:
----------------------------
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
qlen 1000
    link/ether 08:00:27:96:01:af brd ff:ff:ff:ff:ff:ff
3: vlan2 at enp0s3: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN
group default
    link/ether 86:9c:35:e5:cb:51 brd ff:ff:ff:ff:ff:ff
    inet 192.168.6.1/24 brd 192.168.6.255 scope global vlan2
       valid_lft forever preferred_lft forever
----------------------------


Manually running "ip link set enp0s3 up", makes things work as expected.
What also works, is rebooting with the VLAN line commented out of
enp0s3.network, after the system has booted, re-add the line and restart
systemd-networkd.service, and everything is working as it should.

There is nothing of note in journal logs for systemd-networkd in the virtualbox
environment.

On a box which is running systemd 215-4, the following is present after boot:

Assertion 'link->manager->rtnl' failed at src/network/networkd-address.c:306,
function address_configure(). Aborting.

This machine is bringing up two vlans.

This config worked in systemd 214-2.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140724/043ca4d5/attachment.html>