[quagga-dev 15918] Re: bgpd regression of 8/ff results (was Re: Someone rebased volatile/patch-tracking/8/proposed/ff branch)

2016-07-19 Thread Lou Berger
Hi Paul, On 7/19/2016 12:00 PM, Paul Jakma wrote: > On Wed, 13 Jul 2016, Lou Berger wrote: > >> The quick test with the offending patch removed looked good. It just >> found the already reported memory leak. I've started a more >> comprehensive test on whole branch -- will take a~2.5 hours to

[quagga-dev 15919] Re: Someone rebased volatile/patch-tracking/8/proposed/ff branch

2016-07-19 Thread Lou Berger
Thanks! On 7/19/2016 12:03 PM, Paul Jakma wrote: >> > PS I rebased the following commits to be 1st in order to get the >> > regression environment running: > K, will do same. ___ Quagga-dev mailing list Quagga-dev@lists.quagga.net https://lists.quagg

[quagga-dev 15917] Re: Patchwork updated

2016-07-19 Thread David Lamparter
DNS changed (Thanks Paul!), Certificate rolled out, TLS now available: https://patchwork.quagga.net/ I'll add a redirect from HTTP to HTTPS after checking if that breaks Martin's CI scripts again ;) Enjoy! -David On Tue, Jul 19, 2016 at 02:34:46PM +0200, David Lamparter wrote: > On Tue, Jul 19,

[quagga-dev 15916] Re: Patchwork updated

2016-07-19 Thread David Lamparter
On Tue, Jul 19, 2016 at 11:49:06AM +0100, Paul Jakma wrote: > On Tue, 19 Jul 2016, David Lamparter wrote: > > Thanks; the problem there is a different one though - my hosting setup > > has a separate reverse proxy doing all TLS handling; i.e. the > > patchwork setup can't access its own certifica

[quagga-dev 15915] Re: Patchwork updated

2016-07-19 Thread Paul Jakma
On Tue, 19 Jul 2016, David Lamparter wrote: Thanks; the problem there is a different one though - my hosting setup has a separate reverse proxy doing all TLS handling; i.e. the patchwork setup can't access its own certificates. I'm using the ACME DNS method to get my LetsEncrypt certificates

[quagga-dev 15914] Re: Patchwork updated

2016-07-19 Thread David Lamparter
On Tue, Jul 19, 2016 at 11:19:48AM +0100, Paul Jakma wrote: > On Wed, 13 Jul 2016, David Lamparter wrote: > > > I've just installed the most recent version of patchwork; the upgrade > > was a bit bumpy - please report any malfunctions. It looks quite a > > bit different since upstream moved to

[quagga-dev 15913] Re: Patchwork updated

2016-07-19 Thread Paul Jakma
On Wed, 13 Jul 2016, David Lamparter wrote: I've just installed the most recent version of patchwork; the upgrade was a bit bumpy - please report any malfunctions. It looks quite a bit different since upstream moved to bootstrap for styling, but functionally there isn't much different. The

[quagga-dev 15912] Re: Ospf flood reduction

2016-07-19 Thread Paul Jakma
Hi Vivek, On Thu, 14 Jul 2016, Vivek Subbarao wrote: Hi, Does quagga support ospf flood reduction ? If yes, how to configure it ? Please help. What kind of flood reduction do you mean exactly? Things like Ogier's DB-Exchange optimisation, we've implemented since late '06. See https://tool

[quagga-dev 15911] Re: Someone rebased volatile/patch-tracking/8/proposed/ff branch

2016-07-19 Thread Paul Jakma
On Tue, 12 Jul 2016, Lou Berger wrote: Just an update: we've hooked our regression system into the github mirror and are now running minimal regression tests on bgpd. The tests start at a commit and move to the head of the branch, commit by commit -- pretty simple approach. Each run does a co

[quagga-dev 15910] Re: bgpd regression of 8/ff results (was Re: Someone rebased volatile/patch-tracking/8/proposed/ff branch)

2016-07-19 Thread Paul Jakma
On Wed, 13 Jul 2016, Lou Berger wrote: The quick test with the offending patch removed looked good. It just found the already reported memory leak. I've started a more comprehensive test on whole branch -- will take a~2.5 hours to run. Cool. I'll shuffle that from 'ff' to a 'nits' branch. A