Re: Fix IPv6 ECMP handling with 4.11+ kernel

2017-09-01 Thread Ondrej Zajicek
On Fri, Sep 01, 2017 at 01:19:57PM +0200, Vincent Bernat wrote: > ❦ 1 septembre 2017 13:12 +0200, Ondrej Zajicek  : > > >> > Also, alien routes are correctly parsed when next-hops are correctly > >> > ordered (I didn't check if this restriction is also present for IPv4 or > >> > if Linux is alwa

Re: Fix IPv6 ECMP handling with 4.11+ kernel

2017-09-01 Thread Ondrej Zajicek
On Fri, Sep 01, 2017 at 11:59:19AM +0200, Vincent Bernat wrote: > > We have lots of kit (e.g. https://www.arista.com/en/products/7280r-series) > > that comes with: > > > > Linux labtest 3.4.43.Ar-3964936.4173F #1 SMP PREEMPT Mon Dec 19 > > 14:31:21 PST 2016 x86_64 x86_64 x86_64 GNU/Linux > > >

Re: Fix IPv6 ECMP handling with 4.11+ kernel

2017-09-01 Thread Vincent Bernat
❦ 1 septembre 2017 13:12 +0200, Ondrej Zajicek  : >> > Also, alien routes are correctly parsed when next-hops are correctly >> > ordered (I didn't check if this restriction is also present for IPv4 or >> > if Linux is always sending IPv4 multipath routes with next-hops >> > correctly ordered) >>

Re: Fix IPv6 ECMP handling with 4.11+ kernel

2017-09-01 Thread Ondrej Zajicek
On Fri, Sep 01, 2017 at 11:19:40AM +0200, Vincent Bernat wrote: > ❦ 31 août 2017 22:39 +0200, Vincent Bernat  : > > > Also, alien routes are correctly parsed when next-hops are correctly > > ordered (I didn't check if this restriction is also present for IPv4 or > > if Linux is always sending IPv

Re: Fix IPv6 ECMP handling with 4.11+ kernel

2017-09-01 Thread Vincent Bernat
❦ 31 août 2017 22:39 +0200, Vincent Bernat  : > Also, alien routes are correctly parsed when next-hops are correctly > ordered (I didn't check if this restriction is also present for IPv4 or > if Linux is always sending IPv4 multipath routes with next-hops > correctly ordered) It's the same for

Re: Fix IPv6 ECMP handling with 4.11+ kernel

2017-09-01 Thread Vincent Bernat
❦ 1 septembre 2017 12:53 +0300, Lennert Buytenhek  : >> > Starting from kernel 4.11 (commit beb1afac518d), IPv6 are now notified >> > using RTA_MULTIPATH, like IPv4 routes. Those routes are not handled >> > correctly by BIRD. We handle them correctly. This also enable to parse >> > alien routes

Re: Fix IPv6 ECMP handling with 4.11+ kernel

2017-09-01 Thread Lennert Buytenhek
On Fri, Sep 01, 2017 at 11:36:01AM +0200, Ondrej Zajicek wrote: > > Starting from kernel 4.11 (commit beb1afac518d), IPv6 are now notified > > using RTA_MULTIPATH, like IPv4 routes. Those routes are not handled > > correctly by BIRD. We handle them correctly. This also enable to parse > > alien ro

Re: Fix IPv6 ECMP handling with 4.11+ kernel

2017-09-01 Thread Ondrej Zajicek
On Thu, Aug 31, 2017 at 10:39:01PM +0200, Vincent Bernat wrote: > Hey! > > Starting from kernel 4.11 (commit beb1afac518d), IPv6 are now notified > using RTA_MULTIPATH, like IPv4 routes. Those routes are not handled > correctly by BIRD. We handle them correctly. This also enable to parse > alien r

Fix IPv6 ECMP handling with 4.11+ kernel

2017-08-31 Thread Vincent Bernat
Hey! Starting from kernel 4.11 (commit beb1afac518d), IPv6 are now notified using RTA_MULTIPATH, like IPv4 routes. Those routes are not handled correctly by BIRD. We handle them correctly. This also enable to parse alien routes correctly. Route modifications is still done in the old way as for ins