On Fri, Feb 01, 2019 at 03:12:12PM +0200, michal.no...@lnk.ro wrote:
> We've upgraded to 2.0.3 (from 1.6.3) and observed that the number of exported
> routes shown in the protocol details ('show protocol all') does not match (by
> large) these show in 'show route export PROTOCOL count'.
Hi
I w
On Tue, Feb 05, 2019 at 04:35:02PM +0300, Ondrej Zajicek wrote:
> No, BIRD 1.6.x does not print out 'filtered' when 'keep filtered' is
> disabled. So for compatibility it would make sense to not print it
> either. Also reporting 0 does not make sense as there may be routes that
> were filtered,
On Sun, Feb 03, 2019 at 09:14:21AM +0200, michal.no...@lnk.ro wrote:
> On Sat, Feb 02, 2019 at 02:50:39PM +0300, Ondrej Zajicek wrote:
>
> > This is likely just integer overflow during counter decrease, it is
> > mostly harmless. We will see how to fix it.
>
> Hi Ondrej, thanks for quick response
On Sun, Feb 03, 2019 at 04:37:36PM +0300, Ilya Evseev wrote:
> Hi all!
> There is a problem in time output.
> Consider timeformat protocol "%Y-%m-%d %H:%M:%S";
> ...
> As you can see, time is changed by 1 second.
> That's bad for monitoring when it's configured to alert on time/state
> changes.
