<div dir="ltr">This is another reason why I previously suggested to expose a directive to allow administrators to enable/disable the broadcast flag. I have seen DHCP servers ignoring the flag and always sending broadcasted DHCPOFFERs. There could be other servers that may only use unicast, and even networks that might disallow broadcast traffic altogether. <div> </div><div>IMHO, a pragmatic solution to this could be: <div><ul><li>Set broadcast flag always ON for Firewire interfaces: <a href="http://tools.ietf.org/html/rfc2855#section-2" style="color:rgb(65,131,196);text-decoration:none;font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:14px;line-height:23.799999237060547px;background-image:initial;background-repeat:initial">http://tools.ietf.org/html/rfc2855#section-2</a></li> <li>Set broadcast flag always ON for Infiniband interfaces: <a href="http://tools.ietf.org/html/rfc4390#section-2.2" style="color:rgb(65,131,196);text-decoration:none;font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:14px;line-height:23.799999237060547px;background-image:initial;background-repeat:initial">http://tools.ietf.org/html/rfc4390#section-2.2</a></li> <li>Set broadcast flag OFF by default, if and only if the interface is not Infiniband or Firewire</li><li>Expose a configuration directive to allow administrators to configure the broadcast flag in case there are DHCP servers ignoring the RFC, or networks disallowing broadcast traffic. </li></ul><div>Best, </div></div></div><div>Camilo Aguilar</div><div class="gmail_extra"> <div class="gmail_quote">On Sat, Jun 21, 2014 at 12:03 PM, Friedrich Kröner <<a href="mailto:friedrich@mailstation.de" target="_blank">friedrich@mailstation.de</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Saturday 21 June 2014 15:24:03 Tom Gundersen wrote: > On Fri, Jun 20, 2014 at 12:12 PM, Michal Sekletar <<a href="mailto:msekleta@redhat.com">msekleta@redhat.com</a>> wrote: > > On Wed, Jun 18, 2014 at 09:51:02PM +0200, Friedrich Kröner wrote: > >> Hello, > >> > >> when trying systemd-networkd with >=214 and the following config: > >> > >> [Match] > >> Name=eth* > >> > >> [Network] > >> DHCP=yes > >> > >> Address=2001:db8::1234:5678/64 > >> DNS=8.8.8.8 > >> DNS=2001:db8:1::ab9:C0A8:102 > >> > >> > >> I get lots of DHCP DISCOVER events and it doesn't aquire an IPv4 address, > >> nor sets the configured IPv6. > >> > >> Jun 18 18:44:31 localhost systemd[1]: Starting Network Service... > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: timestamp of > >> '/etc/systemd/network' changed > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: sd-rtnl: discarding 20 > >> bytes of incoming message > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: eth0 : link > >> 3 > >> added > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: eth0 : udev > >> initialized link > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: eth0 : > >> flags > >> change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: eth0 : > >> gained > >> carrier > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: could not add new link > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: lo : link > >> 1 > >> added > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: lo : udev > >> initialized link > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: lo : > >> flags > >> change: +LOOPBACK +UP +LOWER_UP +RUNNING > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: lo : > >> gained > >> carrier > >> Jun 18 18:44:31 localhost systemd[1]: Started Network Service. > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: eth0 : link > >> state is up-to-date > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: eth0 : > >> found > >> matching network '/etc/systemd/network/80-dhcp.network' > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: eth0 : > >> acquiring DHCPv4 lease > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: DHCP CLIENT > >> (0x3ddf8f7): > >> STARTED on ifindex 3 with address 52:54:e4:d2:24:44 > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: Sent message > >> type=method_call sender=n/a destination=org.freedesktop.DBus > >> object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello > >> cookie=1 reply_cookie=0 error=n/a > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: DHCP CLIENT > >> (0x3ddf8f7): > >> DISCOVER > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: lo : > >> getting address failed: Device or resource busy > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: lo : link > >> state is up-to-date > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: lo : > >> unmanaged Jun 18 18:44:31 localhost systemd-networkd[19468]: sd-rtnl: > >> discarding 20 bytes of incoming message > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: eth0 : > >> added > >> address: fe80::5054:e4ff:fed2:2444/64 > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: rtnl: received address > >> for a nonexistent link, ignoring > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: lo : > >> added > >> address: ::1/128 > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: eth0 : > >> added > >> address: <a href="http://123.23.23.21/22" target="_blank">123.23.23.21/22</a> > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: lo : > >> added > >> address: <a href="http://127.0.0.1/8" target="_blank">127.0.0.1/8</a> > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: Got message > >> type=method_return sender=org.freedesktop.DBus destination=:1.45 > >> object=n/a > >> interface=n/a member=n/a cookie=1 reply_cookie=1 error=n/a > >> Jun 18 18:44:31 localhost systemd-networkd[19468]: Got message > >> type=signal > >> sender=org.freedesktop.DBus destination=:1.45 > >> object=/org/freedesktop/DBus > >> interface=org.freedesktop.DBus member=NameAcquired cookie=2 > >> reply_cookie=0 > >> error=n/a > >> Jun 18 18:44:33 localhost systemd-networkd[19468]: DHCP CLIENT > >> (0x3ddf8f7): > >> DISCOVER > >> Jun 18 18:44:34 localhost systemd-networkd[19468]: DHCP CLIENT > >> (0x3ddf8f7): > >> DISCOVER > >> Jun 18 18:44:38 localhost systemd-networkd[19468]: DHCP CLIENT > >> (0x3ddf8f7): > >> DISCOVER > >> Jun 18 18:44:46 localhost systemd-networkd[19468]: DHCP CLIENT > >> (0x3ddf8f7): > >> DISCOVER > >> Jun 18 18:45:02 localhost systemd-networkd[19468]: DHCP CLIENT > >> (0x3ddf8f7): > >> DISCOVER > >> Jun 18 18:45:33 localhost systemd-networkd[19468]: DHCP CLIENT > >> (0x3ddf8f7): > >> DISCOVER > >> Jun 18 18:46:36 localhost systemd-networkd[19468]: DHCP CLIENT > >> (0x3ddf8f7): > >> DISCOVER > >> Jun 18 18:47:41 localhost systemd-networkd[19468]: DHCP CLIENT > >> (0x3ddf8f7): > >> DISCOVER > >> Jun 18 18:48:44 localhost systemd-networkd[19468]: DHCP CLIENT > >> (0x3ddf8f7): > >> DISCOVER > >> > >> reverting commit 63a070415db09f5b5bcc5c sd-dhcp-client: allways request > >> broadcast > >> restores the previous behavior. Upon restart of systemd-networkd I get > >> the > >> usual OFFER, REQUEST, ACK confirmation and the IPv6 gets set as well. > >> > >> This is on a kvm-machine with virtio_net as module. > >> > >> Please let me know if you want me to test anything or need further > >> information. > > > > What DHCP server do you use? I was running networkd with > > 63a070415db09f5b5bcc5c included and was able to obtain offers just fine > > on qemu-kvm vms using dnsmasq as DHCP server. > > Thanks guys for looking into this. I finally got my containers working > again today so I could reproduce. There was a bug in sd-dhcp-server so > that it would never send out broadcast packets (so the change > defaulting to requesting broadcast in the client obviously broke > everything). I fixed that now in git, so let me know if there are any > more problems. > > Cheers, > > Tom </div></div>My problem persists. I don't know which DHCP server is used, running current git still only gets me DISCOVERS. Reverting the commit in question fixes the issue. <div class="HOEnZb"><div class="h5">_______________________________________________ systemd-devel mailing list <a href="mailto:systemd-devel@lists.freedesktop.org">systemd-devel@lists.freedesktop.org</a> <a href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/systemd-devel</a> </div></div></blockquote></div> <div> </div>-- <div dir="ltr"><div>Camilo Aguilar</div><div>Software Engineer</div><div><a href="http://github.com/c4milo" target="_blank">http://github.com/c4milo</a></div> </div> </div></div>