Hide Forgot
Description of problem: I'm encountering the same problem as reported 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. Applying the patch attached to the Debian bug fixes the parser error, but then it leads to another error: RTNETLINK answers: No such device Version-Release number of selected component (if applicable): iproute-2.6.39-3.fc16.x86_64 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: Parser error, then RTNETLINK error once the parser error has been patched. Expected results: A working IPv6 multipath route. Additional info: Sorry if this feels like a copy-paste of the Debian bug, but it's the exact same issue, only with Fedora 16 rather than Debian Squeeze :) This bug also affects (at least) RHEL6. It seems you also maintain this package there, so I haven't opened a separate bug for it to avoid spamming you too much. Do you want me to also report it for RHEL6?
Any news on this?
(In reply to comment #1) > Any news on this? Ah, no. I haven't looked at this much yet. Thanks for the reminder :)
The Debian patch seems correct in every way. I wonder if there's another bug elsewhere...
*** Bug 887594 has been marked as a duplicate of this bug. ***
iproute-3.6.0-5.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/iproute-3.6.0-5.fc18
iproute-3.3.0-5.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/iproute-3.3.0-5.fc17
iproute-2.6.39-8.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/iproute-2.6.39-8.fc16
Package iproute-3.6.0-5.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing iproute-3.6.0-5.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-20744/iproute-3.6.0-5.fc18 then log in and leave karma (feedback).
iproute-3.3.0-5.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
iproute-2.6.39-8.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
iproute-3.6.0-5.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
It seems that this problem is still not fixed in RHEL6. Do we have any plan to fix it in RHEL6?
If this is an issue in el6, please open/clone this bug for the Red Hat Enterprise Linux 6 product.