Bug#948332: extended next hop capability not working in Buster

2020-01-17 Thread David Lamparter
On Fri, Jan 17, 2020 at 02:01:30PM +0100, Thomas Goirand wrote: > David Lamparter wrote: > > could you maybe cherrypick the same patches from the 6.0 branch? > > The relevant commit IDs are > > e933c6dd9d62bf8ed09f5eb47d3f1cc59405a492 > > 048586179fe635ee01af371411b81c49238e3581 > > Looking at

Bug#948332: extended next hop capability not working in Buster

2020-01-17 Thread Thomas Goirand
David Lamparter wrote: > Hi Thomas, > > could you maybe cherrypick the same patches from the 6.0 branch? > The relevant commit IDs are > e933c6dd9d62bf8ed09f5eb47d3f1cc59405a492 > 048586179fe635ee01af371411b81c49238e3581 > > This should come down to the exact same changes, just with a lower >

Bug#948332: extended next hop capability not working in Buster

2020-01-09 Thread David Lamparter
Hi Thomas, could you maybe cherrypick the same patches from the 6.0 branch? The relevant commit IDs are e933c6dd9d62bf8ed09f5eb47d3f1cc59405a492 048586179fe635ee01af371411b81c49238e3581 This should come down to the exact same changes, just with a lower chance for error & is a bit more useful

Bug#948332: extended next hop capability not working in Buster

2020-01-07 Thread Thomas Goirand
Source: frr Version: 6.0.2-2 Severity: important Dear maintainer, As per the issue described here: https://github.com/FRRouting/frr/issues/3251 extended next hop capability does not work in Debian Buster. As a consequence, we aren't able to advertize for an IP address on our local loopback