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

[bugzilla-daemon at freedesktop.org]

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

--- Comment #3 from Leo von Klenze <mail at leo-von-klenze.de> ---
Hi Ed,

I've a similar setup and made the following observation:
After starting the container instance the host0 interface has two ips assigned
to it:
1) 169.254.*
2) the ip from my dhcp server gathered over the bridge interface

After deleting the 169.254.* address from the interface (ip addr del ...) the
container can reach the network and is reachable as well.

If that works for you, maybe you can made the following test:
download e.g. the arch iso (88M) several times from an mirror via wget and
check the checksum. In my setup I get corrupted files :-(

BTW: I've both effects with running a container directly on the physical box as
well as running in an KVM instance.

Best regards,
  Leo

-- 
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/8cfc3101/attachment-0001.html>