> On Apr 12, 2019, at 4:45 AM, Ondrej Zajicek wrote:
>
> Like Alexander Zubkov already noted, i also does not see any issue.
Thanks Ondrej, welcome back :-) Hope you had a great break.
I accidentally hit “reply” instead of “reply all” and part of our conversation
went private. Having been on t
On Sat, Apr 06, 2019 at 01:11:32PM -0600, Brian Topping wrote:
> Hi all, I think I looked in all the regular places and inferred that
> reporting issues might best be done here. The gitlab issue tracker shows no
> issues.
Hi
Yes, this is proper place for reporting issues.
> T
Hi Brian,
But I still have not understood what state you consider an error and
where do you expect a warning?
On Wed, Apr 10, 2019 at 7:56 PM Brian Topping wrote:
>
> Hi Alexander,
>
> The “error” I had before was the lack of a warning. I think the usability of
> BIRD would be improved if there
Hi Alexander,
The “error” I had before was the lack of a warning. I think the usability of
BIRD would be improved if there was a warning for the state that I described.
Thanks, Brian
> On Apr 10, 2019, at 6:17 AM, Alexander Zubkov wrote:
>
> Hi Brian,
>
> It is a bit more information, but i
Hi Brian,
It is a bit more information, but it does not help fully still. You are saying:
> With the patch, I use the configuration as shown and it peers as before, but
> the RIB is properly formed:
But I can not understand what error did you have before. If you showed
original bgp configuratio
> On Apr 6, 2019, at 1:38 PM, Alexander Zubkov wrote:
>
> Hi Brian,
>
> Can you give specific examples of what is happening? Configuration samples,
> show running route information from cli, etc.
Hi Alexander, I can give it a shot here. Apologies for the previous direct
reply.
These are the
Hi Brian,
Can you give specific examples of what is happening? Configuration
samples, show running route information from cli, etc.
On Sat, Apr 6, 2019 at 9:19 PM Brian Topping wrote:
>
> Hi all, I think I looked in all the regular places and inferred that
> reporting issues might bes
Hi all, I think I looked in all the regular places and inferred that reporting
issues might best be done here. The gitlab issue tracker shows no issues.
The problem I have seen is where BIRD BGP is running a passive process. The
initiator peer is running the product at https
