<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - systemd-nspawn/networkd: Networking does not work when using --network-bridge"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=76192">76192</a>
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>systemd-nspawn/networkd: Networking does not work when using --network-bridge
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>tobias.hunger@gmail.com
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Other
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>general
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>systemd
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Could you please bring up the interfaces you create and add to bridges? That
would make systemd-nspawn work out of the box for me.

Details of what I did:

I am trying to run a container like this:
systemd-nspawn --directory=/vms/test --boot --network-bridge=br0 --machine=test

The container starts fine and I can login there.

Running "ip addr" in the container shows host0 to be there but without carrier.

Some poking around the host shows that vb-test is there and is set up as part
of br0. "ip addr" claims that the link is down. Running "ip link set dev
vb-test up" on the host brings that link up. Inside the container host0 now got
its carrier and it can go out via DHCP to retrieve its IP (once networkd is
started in the container).</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>