Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1077469

Summary: RFE: dnsmasq does not have IPv6 support for DHCP
Product: Red Hat Enterprise Linux 6 Reporter: Ian Wienand <iwienand>
Component: dnsmasqAssignee: Pavel Šimerda (pavlix) <psimerda>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: low    
Version: 6.4CC: iwienand, thozza
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-01 14:40:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ian Wienand 2014-03-18 04:41:52 UTC
Description of problem:

I'm seeing neutron output this command line:

---
[root@host03 agent]# dnsmasq --version
Dnsmasq version 2.48  Copyright (C) 2000-2009 Simon Kelley
Compile time options IPv6 GNU-getopt DBus no-I18N DHCP TFTP "--bind-interfaces with SO_BINDTODEVICE"

This software comes with ABSOLUTELY NO WARRANTY.
Dnsmasq is free software, and you are welcome to redistribute it
under the terms of the GNU General Public License, version 2 or 3.
[root@host03 agent]# dnsmasq --test --dhcp-range=tag0,fdce:4d13:45a3:ad1b:0:0,static,120s

dnsmasq: bad command line options: only one netid tag allowed
---

the same things works on a debian box I have around, with a later version

---
ianw@debian:/tmp$ /usr/sbin/dnsmasq --version
Dnsmasq version 2.62  Copyright (c) 2000-2012 Simon Kelley
Compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack

This software comes with ABSOLUTELY NO WARRANTY.
Dnsmasq is free software, and you are welcome to redistribute it
under the terms of the GNU General Public License, version 2 or 3.
ianw@debian:/tmp$ /usr/sbin/dnsmasq --test --dhcp-range=tag0,fdce:4d13:45a3:ad1b:0:0,static,120s
dnsmasq: syntax check OK.
---

packages are

[root@host03 agent]# rpm -qa | grep dnsmasq
dnsmasq-utils-2.48-13.el6.x86_64
dnsmasq-2.48-13.el6.x86_64

Comment 2 Ian Wienand 2014-03-18 04:50:04 UTC
Looking at the source of the RH package, it can't handle ':'

---
    case 'F':  /* --dhcp-range */
      {
...        
        while(1)
          {
            for (cp = arg; *cp; cp++)
              if (!(*cp == ' ' || *cp == '.' ||  (*cp >='0' && *cp <= '9')))
                break;
---

It looks like upstream added ipv6 address handling with [1]

[1] http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;h=52b92f4db8133c4b9957ab8e74720eb2cb3207e0

Comment 3 Tomáš Hozza 2014-03-19 11:05:31 UTC
dnsmasq version distributed in RHEL-6 does NOT support DHCPv6 at all.

It is even stated in the man page:
"Dnsmasq supports IPv6 for DNS, but not DHCP."

There are two options how to solve this:
1. Try to backport IPv6 DHCP functionality into RHEL-6 (which for sure won't
be trivial).
2. If (1.) will be too difficult or impossible, then to package newer version
of dnsmasq into RHEL-6.

Comment 4 Tomáš Hozza 2014-04-01 14:26:20 UTC
Hi.

Do we have any customer ticket that is requesting this RFE?
Please escalate your request for this RFE with Layered Product PM.
Until we know what is the priority, we are not able to work on this
and most probably it would never get into RHEL-6 update if not approved
by PM.

Please also check out the dnsmasq-2.68 packaged as SCL [1] if it
would be possible to make OpenStack use it. Note that this is unsupported
best-effort version.

[1] https://softwarecollections.org/en/scls/thozza/scl-dnsmasq268-rhel-6/

Comment 6 Tomáš Hozza 2014-11-21 13:36:30 UTC
Adding Devel Cond NAKs since the backport of the functionality from the upstream version will be close to impossible. The code changes very rapidly and and the latest upstream version is almost a different project in the meaning of source code.

I think the most possible way how to address this is by adding new BIND as a new component, add it to RHSCL or some different approach. However the reported should explain the importance of this feature to PM and hunt for the issue priority and PM acks.

Comment 8 Tomáš Hozza 2016-03-01 14:40:37 UTC
This request was evaluated by Red Hat Engineering for inclusion in a Red
Hat Enterprise Linux maintenance release.

As this bug has been in NEEDINFO for an extended period of time we are going
to close this bug due to inactivity. If you would like to pursue this
matter feel free to reopen this bug and attach the needed information.

With the goal of minimizing risk of change for deployed systems, and in
response to customer and partner requirements, Red Hat takes a conservative
approach when evaluating enhancements for inclusion in maintenance updates
for currently deployed products. The primary objectives of update releases
are to enable new hardware platform support and to resolve critical
defects.

However, Red Hat will further review this request for potential inclusion
in future major releases of Red Hat Enterprise Linux.