Hi Bruce, > I'm not so sure about handing the IP configuration to the service that > is managing the link level. What then do we do with Ethernet? Do we > build an iwd equivalent to set up the routes, etc. for the Ethernet > connections? What I like about what I've seen with systemd-networkd and > wpa_supplicant so far is that I can manage one set of systemd-networkd > configuration files to determine which interface (eth0 or wlan0) gets > priority, and whether or not to use the link's DNS and time services. It > all "just works" for me. I understand that iwd is going to be more > straightforward and better than wpa_supplicant, but systemd-networkd has > also been straightforward and easy for me to work with. I'd like iwd to > "just work", too.
actually we have been working on ead (Ethernet Authentication Daemon) that does indeed will handle Ethernet setup and configuration. It is not about setting up the routes. For that you need a networkd, NM etc. It is about the actual IP configuration of the interface. Regards Marcel _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
