<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - systemd-nspawn --network-bridge breaks networking in container's host" href="https://bugs.freedesktop.org/show_bug.cgi?id=85464#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - systemd-nspawn --network-bridge breaks networking in container's host" href="https://bugs.freedesktop.org/show_bug.cgi?id=85464">bug 85464</a> from <a class="email" href="mailto:mail@leo-von-klenze.de" title="Leo von Klenze <mail@leo-von-klenze.de>"> Leo von Klenze</a> <pre>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</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>