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.

Description of problem:

This is the same bug as in Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=734697

In Fedora, this bug has been fixed.

Also in Debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556974

Doing multipath routing with IPv4 works fine, but it doesn't with IPv6:
    # ip -6 route add default nexthop via 2001:470:25:94::1 weight 1 nexthop via 2001:41e0:ff00:47::1 weight 1
    Error: an IP address is expected rather than "2001:470:25:94::1"

Note that the Debian bug doesn't specify it, but the problem happens even if you only specify one path:
    # ip -6 route add default nexthop via 2001:470:25:94::1 weight 1

This should be equivalent to the same command without the "nexthop":
    # ip -6 route add default via 2001:470:25:94::1 weight 1
    Error: an IP address is expected rather than "2001:470:25:94::1"

Again, this works perfectly fine with IPv4.

How reproducible:
    100%

Steps to Reproduce:
    1. Make sure your network is IPv6 enabled
    2. Try adding a multipath IPv6 route (it doesn't have to have several "nexthop", one is enough to trigger the bug)

Actual results:
Below error output:
Error: an IP address is expected rather than "2001:470:25:94::1"

Expected results:
A working IPv6 multipath route.

Created attachment 969509 [details]
patch

Still does not work. Same error message.

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-1331.html