Thanks!
-
Nasato Goto
JPNAP / INTERNET MULTIFEED CO.
g...@mfeed.ad.jp
-
2020/04/15 11:07 に、"Ondrej Zajicek" を書き込みました:
On Wed, Apr 15, 2020 at 01:59:22AM +, Nasato Goto wrote:
> Hi Ondrej,
>
> Thank you!
> Could you tell me will it be merged on next release, v2.
On Wed, Apr 15, 2020 at 01:59:22AM +, Nasato Goto wrote:
> Hi Ondrej,
>
> Thank you!
> Could you tell me will it be merged on next release, v2.0.8?
Yes, i just committed it.
> > Just wondering whether you noticed this issue during testing or during
> > operation (so there are still some 2B-
Hi Ondrej,
Thank you!
Could you tell me will it be merged on next release, v2.0.8?
> Just wondering whether you noticed this issue during testing or during
> operation (so there are still some 2B-AS-only implementations in the
> wild.
I found this through our test suite. We faced with this kind o
Hi,
I recently upgraded from 4.19.97 to 5.4.28 and I noticed that bird was
using a lot more CPU (about three times).
On those two graphs you can see the CPU usage and when I rebooted:
https://pix.milkywan.fr/gallery#ugO0qVvx.png,ncr9kHfi.png
I rebooted to 4.19.113 and now I’m back to the ~10 % a
On Tue, Apr 14, 2020 at 02:45:29PM +, Nasato Goto wrote:
> Hi all,
>
> I found a bit strange behavior of handling AGGREGATOR attributes in BIRD
> v2.0.7 route server.
> When BIRD receives a route containing AGGREGATOR attribute from 4byte-AS
> capable peer,
> it sends the route with strange
Hi all,
I found a bit strange behavior of handling AGGREGATOR attributes in BIRD v2.0.7
route server.
When BIRD receives a route containing AGGREGATOR attribute from 4byte-AS
capable peer,
it sends the route with strange AGGREGATOR to 4byte-AS incapable peer.
On the other hand, BIRD can sends AS
On 15:30 09.05.18, Toke Høiland-Jørgensen wrote:
> Ondrej Zajicek writes:
> > There are some minor issues (like there should be check for error values
> > from neigh_find2()), but that can i fix. I just wonder whether we would
> > want this behavior as a default or whether it should be configurabl
