On Thu, 27 Feb 2014 19:32:03 +0100 Tom Gundersen <teg@jklm.no> wrote:
On Thu, Feb 27, 2014 at 7:20 PM, Leonid Isaev <lisaev@umail.iu.edu> wrote:
On Thu, 27 Feb 2014 13:03:27 -0500 Dave Reisner <d@falconindy.com> wrote:
On Thu, Feb 27, 2014 at 12:56:02PM -0500, Leonid Isaev wrote:
On Thu, 27 Feb 2014 14:25:15 +0100 Jouke Witteveen <j.witteveen@gmail.com> wrote:
Support for additional DHCP clients is now easy to add.
Just a quick question: are there any plans to use networkd as a DHCP backend? Yes, it is config-file-driven, but one can probably generate the .network files in /run on the fly...
This sounds like pointless masturbation. Just use networkd directly.
That's what I originally thought, and (in a nutshell) this is what I am currently using.
However, networkd config is based on an interface name, not a profile. Hence there are special cases when e.g. 2 wireless networks use different settings (dynamic/static IP, different DNS, etc.). In these scenarios one needs wpa_actiond. As long as the correct profile is selected, one can make use of networkd instead of dhcpcd.
We probably want to improve networkd's [Match] logic, to also work in this case. I.e., to match on SSID. Not on my immediate TODO though, but patches welcome ;-)
So, the SSID is supposed to be exposed by wpa_supplicant via dbus?
In general though, I quite like the idea of using networkd as a glorified dhcp client. We probably still lack some features in networkd before to make it support a bit of dynamic configuration before this really makes sense though.
Yes, but hopefully it won't become another NetworkManager :)
Cheers,
Tom
Thanks, -- Leonid Isaev GPG key fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D