[systemd-bugs] [Bug 81225] New: regression in systemd-networkd: unable to acquire address via DHCP since 63a070415db09f5b

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=81225

          Priority: medium
            Bug ID: 81225
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: regression in systemd-networkd: unable to acquire
                    address via DHCP since 63a070415db09f5b
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: asb at asbradbury.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

I've been playing with Arch on Linode (a popular VPS provider using Xen for
virtualisation) and have found that systemd-networkd fails to acquire an IP via
DHCP in systemd-214+. Some googling revealed I'm not the only one to encounter
this: https://bbs.archlinux.org/viewtopic.php?pid=1434549. `dhcpcd eth0` works
just fine. systemd-networkd gives no useful output, giving nothing after eth0:
gained carrier.

I looked through the commit log for likely candidates and came across
63a070415db09f5b5bcc5c487bfc85dabe443dde "sd-dhcp-client: allways request
broadcast". I confirmed that running `dhcpcd -J eth0` also failed to acquire an
IP (this flag forces the broadcast flag in dhcpcd) and further confirmed that
recompiling systemd with the offending patch reverted fixed things for me. This
patch did see some discussion which featured ideas on alternate behaviour:
http://lists.freedesktop.org/archives/systemd-devel/2014-May/019621.html

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140711/a34c404c/attachment.html>