Re: [opensource-wg] RV: [ripe-list] Update on the Community Projects Fund 2024
Hello, I would like to congratulate all the projects selected by the Community Projects Fund. I also wish to express my gratitude to the organising committee for initially selecting our project, 'RIPE Atlas distributed network telescope'. I am currently engaged in doctoral research on IBR traffic, and together with my supervisory team, we have proposed this project. We saw this as an ideal opportunity for the community to collect IBR traffic and make it available. We currently have a small working network of sensors (HoDiNT, Home Distributed Network Telescope [1]) and our objective is to extend the network and have RIPE manage the traffic collected. The HoDiNT sensors receive IBR traffic forwarded from the home connection router and forward it to a collector for analysis. They are fully compatible with Atlas sensors. This would enrich the traffic of other research centres, such as CAIDA or Merrit, and offer other students and research centres the possibility of having IBR traffic available for analysis. I was delighted that our project was selected, but a few hours later the organisation sent us an email stating that the RIPE Atlas team had raised some concerns about our proposal which may impact our ability to receive funding. We were requested to attend a meeting with the organisation and the RIPE Atlas team to discuss the proposal a few days later. The meeting was unfortunately not attended by a representative of RIPE Atlas. We were informed that the project was not deemed feasible. I would like to thank Alastair, who had to pass on the news to us, which is not an easy situation. I accept the decision taken, although I do not agree with either the substance or the form. I think we should have been given the opportunity to reformulate the project, maintaining the original objective but circumventing the limitations exposed. We will continue to improve HoDiNT in order to make it available to the community as soon as possible. If anyone is interested in contributing to the project, improving the code (mainly Python) and/or hosting sensors, please contact us. Due to limited resources, it is not possible to add sensors to the network openly, and we are doing so with sensors from colleagues and friends whom we thank for their time and resources. Regards, Rodolfo. [1] https://www.sciencedirect.com/science/article/pii/S138912862400402X [2] https://drive.google.com/file/d/1VGJ4PEcf-kHtFVT7rsXd9QYDqRL6rGH6/view?usp=s... -- Rodolfo García Peñas (kix) http://www.kix.es/ "I asked him once how to change the key bindings and Dave said 'You use the Change Configuration command. On Unix it is abbreviated as cc.' Dave Conroy and Lawrence Stewart. On Friday, November 15th, 2024 at 14:18, Marcos Sanz via opensource-wg <opensource-wg@ripe.net> wrote:
FYI. Sorry for the cross-posting.
-----Mensaje original----- De: Alastair Strachan projectsfund@ripe.net Enviado el: jueves, 14 de noviembre de 2024 12:55 Para: ripe-list@ripe.net Asunto: [ripe-list] Update on the Community Projects Fund 2024
Dear all,
After the announcement of this year’s Community Projects Fund recipients, some challenges emerged with the RIPE Atlas distributed network telescope project which would have prevented the project from achieving the goals outlined in the project plan.
After careful consideration, the Selection Committee made the difficult decision to withdraw funding for the project. While we understand this is really disappointing for the recipients, we sincerely hope they will continue initiatives that bring value to our community and the Internet.
The Selection Committee has now chosen another project to support from our pool of finalists: OpenPenny - An open-source tool to identify non-spoofed traffic. You can read about the project on the Community Projects Fund 2024 page: https://www.ripe.net/community/community-initiatives/cpf/previous- funding-recipients/funding-recipients-2024/ <https://www.ripe.net/community/community-initiatives/cpf/previous- funding-recipients/funding-recipients-2024/>
Warm regards, Alastair Strachan Community Projects Fund Coordinator
----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/opensource-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
truly sad story as project is really useful. i was reading about it and i wish i could send my home fw blocked traffic to somewhere useful for analysis. i do run pf and pflog here. i get loads of fancy traffic, smb attacks, ntp attacks, all sorts of crap. i noticed certain privacy issues with that implementation actually but they can't be resolved. only way is to use unused ip for this. possibly v4 as iirc ipv6 doesn't get such traffic due sheer amount of addresses in space but who knows. but whole idea is good. esp i'm curious myself about who/what/when/why/... sends unwanted traffic to home ranges. unsure about implementation but at least idea is good
participants (2)
-
Rodolfo García Peñas (kix)
-
Sulev-Madis Silber