> > The container usecase alone is already the reason why I am so very sure > I want this stuff, and that it needs to be in networkd, and just work. I > want this fully automatic, so that we can create a hundred of veth > tunnels, and trivially easy (simply by setting DHCPServer=yes for their > .network file) make them automatically configured, passing the relevant > configuration bits on.
I'm sorry to intervene, but there are other ways to configure containers and similar stuff. I mean, systemd is great because it pioneered so many cool things. Why can't we do something new? For example, prohibit IPv4 for containers and VMs and require them to use IPv6 with link-local addresses which will eliminate the need for any kind of configuration. Pushing IPv6 forward is a good idea. But, well, if you find this unacceptable, what's wrong with IPv4LL? DHCP is complex (well, not _that_ complex, but still) and it's not always required. E.g. IPv6 networks can live without DHCP by using link-local addresses and, say, some basic NDP. It seems to me that IPv4LL should suffice for all the “container use-cases”.
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
