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.

Created attachment 945309 [details]
upstream patch for bug #1005814

Description of problem:
Patch [1] that we use to fix bug #1005814 breaks dhcrelay (dhcp relay agent daemon) for IPv6.
When the 'lower' interface is specified ('-l') on command line before 'upper' interface ('-u') the relaying of messages does not work.
Example:
$ dhcrelay -d -6 -I -l eth0 -u eth1

http://pkgs.devel.redhat.com/cgit/rpms/dhcp/tree/dhcp-4.2.5-ipv6-bind-to-interface.patch?h=rhel-7.1

Version-Release number of selected component (if applicable):
dhcp-4.2.5-30.el7

How reproducible:
always

Steps to Reproduce:
1. [relay machine]
  $ dhcrelay -d -6 -I -l eth0 -u eth1
2. [relay machine]
  $ wireshark
3. [client machine]
  $ dhclient -d -6 -S ethx (ethx is connected to the same link as dhcrelay's 'lower' interface)

Actual results:
no Relay-Forw message

Expected results:
Relay-Forw message sent to ff05::1:3

Additional info:
dhcrelay -d -6 -I -u eth1 -l eth0
still works

cloned for RHEL-6 as bug #1151054

Verified with dhcp-4.2.5-32.el7. dhcrelay works with any 'upper' 'lower' interface order on the cmdline.I can also confirm that bz#1005814 works as well.

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, 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://rhn.redhat.com/errata/RHBA-2015-0450.html