Bug 9233

Summary:	ip -6 route nexthop expects ipv4 instead of ipv6 address
Product:	Mageia	Reporter:	AL13N <alien>
Component:	RPM Packages	Assignee:	Thomas Backlund <tmb>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	alien, stormi-mageia, tmb
Version:	2	Keywords:	Triaged
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	iproute2	CVE:
Status comment:

Description AL13N 2013-03-02 00:43:47 CET

patch is here: http://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/commit/?id=4d6c3796a5cba380afca43c46aeafd2cbf997323

i wanted to fix this myself, but then i noticed that on MGA2!

3.3.0-1.mga2 is the current version (revision 224980 dated 2012-03-20!!!)

and the newest revision on mga2 (339768 dated 2013-01-06) updates to 3.7.0... which actually requires 3.7.0 ... ? why would we switch to 3.7.0 kernel in mga2?

between that there's several tries for rebuilding against db5.2 and db5.3

but nothing submitted...

i just wanted to add a little bugfix?

what do i do? do i just remove all this newer unsubmitted stuff from svn (reverse merge) and patch it so i can get the bug fixed?

Reproducible: 

Steps to Reproduce:

AL13N 2013-03-02 00:44:39 CET

CC: (none) => alien, thierry.vignaud, tmb

Comment 1 Thomas Backlund 2013-03-03 02:44:24 CET

There is now a iproute2-3.3.0-2.mga2 to test in mga2 core updates_testing

Comment 2 AL13N 2013-03-03 08:11:37 CET

[root@localhost linux]# ip -6 route add default nexthop via 2001:770:100:56::1 dev sixxs weight 1 nexthop via 2001:470:1f14:199e::1 dev h-e weight 1
RTNETLINK answers: No such device


something is stilm wrong :-(

Comment 3 Thomas Backlund 2013-03-03 11:02:23 CET

Does it work in cauldron ?

Thierry Vignaud 2013-03-03 11:11:24 CET

CC: thierry.vignaud => (none)

Comment 4 AL13N 2013-03-03 13:09:32 CET

it does :-(

Comment 5 AL13N 2013-03-03 20:57:11 CET

is it unfixable in mga2? wdyt?

Samuel Verschelde 2013-09-06 21:51:28 CEST

Keywords: (none) => Triaged
CC: (none) => stormi
Assignee: bugsquad => tmb

Comment 6 AL13N 2013-09-08 14:29:58 CEST

i guess i'll have to upgrade my firewall to mga3 in order to have multiple nexthop in IPv6

Comment 7 Manuel Hiebel 2013-10-22 12:11:23 CEST

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Comment 8 AL13N 2013-10-22 19:17:14 CEST

@thomas:

if it is not doable to find the patches on newer kernels to backport to this kernel to get it fixed for real, then please close as WONTFIX

Comment 9 Manuel Hiebel 2013-11-23 16:14:41 CET

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD