- ris-users - mailman.ripe.net

RIS Quarterly Planning Q1 2024
by Paul de Weerd 20 Dec '23

20 Dec '23

Dear colleagues, The quarterly plans for RIS can now be found at: https://www.ripe.net/support/documentation/quarterly-planning/ris In this quarter, we'll continue working on modernising the RIS beaconing and open-sourcing the RIS Live code. We hope that by providing these plans, we can better inform the community of the ongoing developments on RIS and get feedback on our work. If you have any input on these plans or suggestions for future work, please reach out to us. Kind regards, Paul de Weerd RIPE NCC

1 0

Re: ris-users Digest, Vol 50, Issue 3
by Rob Ballantyne 29 Nov '23

29 Nov '23

Thanks Colin, I tried today, unsuccessfully unfortunately, to get a small example to fail in the way my stuff was failing. If I can prove out a bug, I’ll definitely create Github issue. Thanks for the help! Rob > > ------------------------------ > > Message: 2 > Date: Tue, 28 Nov 2023 11:43:00 +0100 > From: Colin Petrie <colin(a)spakka.net> > To: Rob Ballantyne <robballantyne3(a)gmail.com> > Cc: ris-users(a)ripe.net > Subject: Re: Restrictions around freeing memory with > bgpdump_free_memory > Message-ID: <2c44746b4c0a70be113a36080fd01539(a)spakka.net> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi Rob, > > bgpdump versions before 1.5.0 had thread-safety issues due to use of > global variables. If you are still having issues with the latest > version, please open an issue on Github so we can look into the problem. > > Thanks, > Colin > >

1 0

Restrictions around freeing memory with bgpdump_free_memory
by Rob Ballantyne 28 Nov '23

28 Nov '23

Hi, I’m running into memory access exceptions when using bgpdump_free_memory(). I’m collecting an interval worth of BGPDUMP_ENTRYs (1 minute worth) into buckets. After I have a bucket full I do a pairwise computation (that can take some time) of just this buckets data on a thread (from a pool) while the main thread moves onto the second bucket (and then starts up potentially another thread on the second bucket). … After the thread completes its summary statistics computation, it goes to call bgpdump_free_memory() on each of the BGPDUMP_ENTRY. I mutex lock so that only on thread will execute in bgpdump_free_memory() at a time. Are there restrictions (express or implied) on how to call bgpdump_free_memory() whether multi-threaded or not? BTW, if I run just a single thread it does seem to work just fine. Thanks, Rob

2 1

Two years of selective peering with RIS
by Michela Galante 23 Nov '23

23 Nov '23

Dear colleagues, We published an article on RIPE Labs where we talk about our RIS peering strategy of the last two years, what we've achieved so far, and why we've temporarily removed the peering form from our website: https://labs.ripe.net/author/emileaben/two-years-of-selective-peering-with-… We would love to hear your thoughts about it either here on this mailing list, in the Forum or live at RIPE 87. Best regards, Michela Galante RIPE NCC

1 0

Using libbgpdump - obtain aspath?
by Rob Ballantyne 07 Nov '23

07 Nov '23

Hello All, I’ve just started looking at libbgpdump for a project where I will be parsing MRT/BGP data. I’ve managed, following the example/advice I’ve seen, to get a basic loop running through an update file from the repository working. However, I don’t seem to be able to find the ASPATH component in the parsed data structure. I can see the type/subtype of the data block is BGPDUMP_TYPE_ZEBRA_BGP/BGPDUMP_SUBTYPE_ZEBRA_BGP_MESSAGE. I can also see that the BGPDUMP_BODY is a discriminated union based on these values. I can see that BGPDUMP_ENTRY.attr should probably contain an ASPATH but it doesn’t seem to be set ever. Should I be expecting the ASPATH to be set in this case? Should I be doing something different (calling some init function after discovering the BGPDUMP_BODY is of the right type?). Thanks! Rob

2 1

RIS Quarterly Planning Q4 2023
by Paul de Weerd 28 Sep '23

28 Sep '23

Dear colleagues, The quarterly plans for RIS can now be found at: https://www.ripe.net/support/documentation/quarterly-planning/ris In this quarter, we'll continue making improvements to RIS data through peering coordination and start working on open sourcing the RIS Live code. We hope that by providing these plans, we can better inform the community of the ongoing developments on RIS and get feedback on our work. If you have any input on these plans or suggestions for future work, please reach out to us. Kind regards, Paul de Weerd RIPE NCC

1 0

rrc03 maintenance - Aug 1st 2023, 12.00-14.00 UTC
by Marco Giuliani 01 Aug '23

01 Aug '23

Dear ris-users, due to an urgent hardware upgrade rrc03.ripe.net will be powered down for two hours. from Aug 1st, 2023, 12.00 UTC to Aug 1st 2023, 14.00 UTC rrc03.ripe.net is the Routing Information Service collector at AMS-IX and NL-IX. BGP sessions will go down and will re-establish once the maintenance is over. Kind regards, Marco Giuliani RIPE NCC

1 0

rrc19 is back
by Marco Giuliani 26 Jul '23

26 Jul '23

Dear all, rrc19.ripe.net, our collector at NAP Africa in Johannesburg, is back. Special thanks to Network Platforms - https://www.networkplatforms.co.za - for generously providing us with the server and Internet connectivity for free! Kind regards, Marco Giuliani RIPE NCC

1 0

RRC14 (Palo Alto) extended maintenance
by Martin Pels 19 Jul '23

19 Jul '23

Dear all, RIS collector RRC14, hosted at Equinix Palo Alto, US will be moved to a different location by our sponsor. Because of this the collector will be unavailable for several days, starting July 19th at 15:00 UTC. We will update this ticket with more information once we have an estimate about the reconnection time. Kind regards, Martin Pels RIPE NCC

1 0

RIS Quarterly Planning Q3 2023
by Paul de Weerd 27 Jun '23

27 Jun '23

Dear colleagues, The quarterly plans for RIS can now be found at: https://www.ripe.net/support/documentation/quarterly-planning/ris In this quarter, we'll continue making improvements to RIS data through peering coordination and start working open sourcing the RIS Live code. We hope that by providing these plans, we can better inform the community of the ongoing developments on RIS and get feedback on our work. If you have any input on these plans or suggestions for future work, please reach out to us. Kind regards, Paul de Weerd RIPE NCC

1 0