Wrong bit set in klibc PXE dhcp/bootp flags

PPA containing fixed klibc pkg:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1624014

This bug was fixed in the package klibc - 2.0.4-8ubuntu3

---------------
klibc (2.0.4-8ubuntu3) yakkety; urgency=medium

  * debian/patches/broadcast_dhcp_send.patch: the patch sets the wrong bit in
    the bootp flags field, instead of 0x800 it must be 0x8000. (LP: #1624014)

 -- Dan Streetman <email address hidden> Fri, 16 Sep 2016 20:20:58 -0400

Hello Dan, or anyone else affected,

Accepted klibc into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/klibc/2.0.4-8ubuntu1.16.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Dan, or anyone else affected,

Accepted klibc into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/klibc/2.0.3-0ubuntu1.14.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

The fix has been tested and is working. Several machine's have been booted and commissioned successfully

I can confirm that with this fix I have been successfully able to enlist, commission and deploy ubuntu to multiple servers in a cabinet via a DHCP relay agent to MaaS in another cabinet. THis is great! THanks.

Note, I was using a provided hotfix build of xenial in my tests.

This bug was fixed in the package klibc - 2.0.4-8ubuntu1.16.04.2

---------------
klibc (2.0.4-8ubuntu1.16.04.2) xenial; urgency=medium

  * debian/patches/fix_broadcast_flag-bit.patch: the previous patch set the
    wrong bit in the bootp flags field, instead of 0x800 it must be 0x8000.
    (LP: #1624014)

 -- Dan Streetman <email address hidden> Tue, 20 Sep 2016 14:20:36 -0500

The verification of the Stable Release Update for klibc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Hello, cyphermox!

Do you think you could send your patches upstream as well?

The same bug affects Debian (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756633) and, probably, the source packages. It's sad seeing this fixed in Ubuntu only.

Thanks!

I've tested Clonezilla's Alternative Stable branch (Yakkety-based), and its Alternative Testing branch (Zesty-based) and the bug is squashed on both platforms. It would be nice if someone could test Trusty as well.

I confirmed the fix is correct in trusty by tcpdumping a run of /usr/lib/klibc/bin/ipconfig

to clarify, tcpdump with klibc-utils 2.0.3-0ubuntu1.14.04.1 shows the flag is 0x0800 (incorrect) while tcpdump with klibc-utils 2.0.3-0ubuntu1.14.04.2 (from -proposed) shows the flag is 0x8000 (correct).

This bug was fixed in the package klibc - 2.0.3-0ubuntu1.14.04.2

---------------
klibc (2.0.3-0ubuntu1.14.04.2) trusty; urgency=medium

  * debian/patches/fix_broadcast_flag-bit.patch: the previous patch set the
    wrong bit in the bootp flags field, instead of 0x800 it must be 0x8000.
    (LP: #1624014)

 -- Dan Streetman <email address hidden> Tue, 20 Sep 2016 14:07:24 -0500