RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
dnsmasq as a DHCPv6 server doesn't correctly form the NTP server option (56) in its responses. It doesn't use the suboptions specified in RFC 5908.

This was fixed in upstream commit dded78b2338147daf69064d6d48c16b12744e441.


Version-Release number of selected component (if applicable):
dnsmasq-2.79-19.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1. add "dhcp-option=option6:ntp-server,[2001:db8:ca2:2::1]" to configuration
2. restart dnsmasq
3. start tshark -V -f 'port 547'
4. wait for DHCP response

Actual results:
Malformed message

Expected results:
NTP server option contains NTP server address suboption

Additional info:

Seems reasonable. While it were possible to encode correct payload in hex format, that is unconvenient and inpractical. It is just small addition and self contained. Already present in RHEL9.

Upstream commit: http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=dded78b2338147daf69064d6d48c16b12744e441

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: dnsmasq security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:7633