On Wed, 22.04.15 15:52, Spencer Baugh (sba...@catern.com) wrote: > > As soon as networkd gains a bus interface maybe an option could be to > > hook up nspawn's --network-interface= with it: if the specified > > interface doesn't exist, nspawn could synchronously ask networkd to > > create it. With that in place you could then configure .netdev files > > outside of the container, and neatly pass them on into the container, > > without races. Would that fix your issue? > > Yes, that sounds like it would work. This would destroy and recreate the > interface on reboot, which is fine for my use case.
I'll add it to the TODO list. It's not actually nspawn that destroys these interfaces, it's the kernel. > There might at some point be a desire by someone else to have the > interface not be destroyed on reboot. At that point it would just > require teaching networkd something about network namespaces, which > shouldn't be hard. I don't want that myself, of course. Hmm, I am not sure that that teaching networkd namespacing is that easy or desirable. But anyway, we can discuss this when this comes up. > >> I would somewhat prefer to be using this feature of IPv6, rather than > >> using DHCPv6; and anyway, networkd doesn't support DHCPv6 right now, > >> right? So this doesn't necessarily work for me. > > > > True. It's certainly our plan to support it eventually. > > That's in reference to just DHCPv6, right? What about stateless > autoconfiguration, out of curiosity? THe code for that is already in place. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel