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

** Changed in: klibc (Ubuntu Trusty)
       Status: In Progress => Fix Committed

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.

  Wrong bit set in klibc PXE dhcp/bootp flags

Status in klibc package in Ubuntu:
  Fix Released
Status in klibc source package in Trusty:
  Fix Committed
Status in klibc source package in Xenial:
  Fix Committed
Status in klibc source package in Yakkety:
  Fix Released

Bug description:

  The patch for bug 1327412 set the wrong bit in the bootp flags field.
  It set flags to 0x800, but the correct value is 0x8000.  That sets the
  "broadcast" bit, and the spec requires all other bits to be 0.

  Setting one of the "must be zero" bits in the flags field causes some
  DHCP relay agents to drop the packets, causing PXE to fail.

  [Test Case]

  Get a DHCP relay agent that drops PXE packets with an invalid
  bootp.flags bit set, and try to PXE boot; it fails.


  None, the previous patch introduced this regression.

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to