[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 #6 from Ed Tomlinson <edt at aei.ca> ---
If use the following commands in the kvm (host) instance:

ip netns add dev
ip link add veth0 type veth peer name host0
ip link set dev veth0 master br1
ip link set host0 netns dev
ip netns exec dev systemd-nspawn --link-journal=guest -bqD /jail/dev &
ip netns exec dev ip link set lo up
ip netns exec dev ip addr add 2001:4830:1100:xxxx::a/64 dev host0
ip netns exec dev ip -6 route add default via 2001:4830:1100:xxxx::2
ip netns exec dev ip link set host0 up
ip link set veth0 up

Then the network acts as expected and ssh connections to the address assigned
to
br1 continue to work for both root and user clients.  This is what I understand
--network-bridge-br1 should be doing.  Also not that the netns is setup by
systemd-nspawn it does not show up in ip netns list.

I'll create a new parameterized service using the above setup for now but this
really should just work.

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/20141028/f6c18f10/attachment-0001.html>