[systemd-bugs] [Bug 85464] New: systemd-nspawn --network-bridge breaks networking in container's host

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 85464
           Summary: systemd-nspawn --network-bridge breaks networking in
                    container's host
           Product: systemd
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: edt at aei.ca
        QA Contact: systemd-bugs at lists.freedesktop.org

Running kernel 3.17.1 with system 216 (or aur/systemd-git) on an up to date
arch install.

On my physical box (grover) I use systemd-networkd to configure a bridge (br0)
and assign it ip4&6 addresses.  Then start a kvm instance (host) which has the
tap interface it creates added to br0.  In the kvm instance I use
systemd-networkd to add a bridge (br1) and assign it ip4&6 addresses.

At this point I tested and was able to ssh from grover to the kvm instance from
both root and a normal user to both the kvm's root and a normal user.

Then in the kvm as root I start a container (dev) using the
networkd-nspawn at .service modified adding a --network-bridge=br1 option.  The
vhost0 interface in the container is setup using systemd-networkd with only an
ip6 address.

At this point the br1 interface's address is _unreachable_ from a normal user
in grover or dev.  It is pingable with root in these instances. 

Have I encountered a bug or it is a nasty side effect of namespaces and/or
private-network manipulated by systemd-nspawn?

Thanks
Ed

-- 
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/20141026/e1273654/attachment.html>