Hi, > To clarify this: systemd-networkd is supposed to cover the initrd, > container, server and (some) embedded usecases. However, use NM or > connman for the "interactive" stuff (like wlans and suchlike) you need > on laptops/desktops and mobile.
Will this cover the UseCase of having a DHCP enabled Interface which starts asking for IP if the interface is coming up? or is this already considered as interactive uses case? in embedded this is often a standard configuration as such devices don't have a interactive interface and assigning a IP via DHCP makes the live much easier. currently we integrate http://0pointer.de/lennart/projects/ifplugd/ > The idea is that this can work jointly with NM/connman in some ways or > another. For example you can make use of .link files even with > interfaces that otherwise are handled by connman/NM, but for IP config > you have to chose one. > Lennart > > -- > Lennart Poettering, Red Hat > -- Holger Winkelmann _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
