On Sun, Jul 6, 2014 at 11:52 PM, Leonid Isaev <lis...@umail.iu.edu> wrote: > On Sun, Jul 06, 2014 at 08:43:01PM +0200, Tom Gundersen wrote: >> On Sun, Jul 6, 2014 at 7:17 PM, Leonid Isaev <lis...@umail.iu.edu> wrote: >> > Hi, >> > >> > With systemd-215 networkd fails to set up the DHCPv4 on WAN >> > interface: >> > ------ >> > $ journalctl -u systemd-networkd.service | grep wlp1s0 >> > Jul 06 12:21:07 hermes systemd-networkd[355]: wlp1s0 : link >> > configured >> > Jul 06 12:21:08 hermes systemd-networkd[355]: wlp1s0 : gained >> > carrier >> > Jul 06 12:21:08 hermes systemd-networkd[355]: wlp1s0 : could not >> > start IPv6 router discovery >> > Jul 06 12:21:08 hermes systemd-networkd[355]: wlp1s0 : failed >> > ------ >> > >> > Interestingly, if I restart networkd, the (DHCPv4) lease _is_ obtained, >> > but the >> > default route is _not_ set. The reason why IPv6 router discovery fails is >> > because I boot with 'ipv6.disable=1' on the kernel cmdline. So, is there >> > now a >> > hard dependency on IPv6 being enabled? >> >> >> Hm, this is unfortunate. In the meantime you can only enable DHCPv4 by >> setting DHCP=v4 (as opposed to DHCP=yes). > > That worked... thanks. BTW, is yes/true still a valid argument for DHCP > (because the manpage says otherwise)?
"yes" is a synonym for "both" and "no" for "none". _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel