February 2021 - NLNOG - mailman3.nlnog.net

NLNOG at MCH2021
by Nathalie Trenaman 25 Feb '22

25 Feb '22

Hi all, As you might know, the organisers of MCH2021 ( https://mch2021.org/#/ <https://mch2021.org/#/>) have started the ticket sales. Some of us in the board of NLNOG thought it would be cool to have an NLNOG Village there. But we had an NLNOG Camp a few years back and although it was great fun, if was a bit expensive for the amount of people that attended. That’s why we decided to first find out if there is enough interest to move forward with this. We’ve set up a 3 question (30 seconds!) questionnaire on SurveyMonkey: https://nl.surveymonkey.com/r/LT86B8G <https://nl.surveymonkey.com/r/LT86B8G> If you don’t want to click links, you can also reply to the questions in this mail: -Are you considering to attend MCH2021? -Would you join the NLNOG Village? -Would you be interested to help out organising? (build-up, program, bar, etc.) It would help us tremendously if you could take 30 seconds to reply or fill in the survey on SurveyMonkey! (Also if you’re not going to attend MCH2021!) Thanks and happy holidays from all of us! NLNOG Crew

3 2

Call for Presentations: RIPE 82
by Jelte Jansen 25 Feb '21

25 Feb '21

*RIPE 82 will be a free virtual event and will take place from 17-21 May 2021* The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, lightning talks and BoFs. Please note that no workshops or tutorials will be organised at this meeting. The RIPE 82 Meeting plan is available here: https://ripe82.ripe.net/programme/meeting-plan/ You have until *19 March 2021* to submit your presentations proposals. Proposals submitted after this date will be considered depending on the slots still available in the programme. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Connected Things (aka. Internet of Things - IoT) RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and should not attempt a product demonstration. --------------------------------------------------------------------- Submissions --------------------------------------------------------------------- The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe82.ripe.net/submit-topic/submission-form/ - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panelists, presenters and moderators. - Presenters should indicate how much time their presentations will require. Here’s an indication of the average duration of each session format: o Plenary presentations: 20-25 minutes presentation with 10-5 minutes discussion o Lightning talks: 10 minutes for both the presentation and discussion o BoFs: one hour - Lightning talks should also be submitted using the same meeting submission system and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced the week before the RIPE Meeting. - Presenters who propose a BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. More detail on the presentation formats can be found here: https://ripe82.ripe.net/submit-topic/presentation-formats/ --------------------------------------------------------------------- Plenary or Working Group? --------------------------------------------------------------------- Presenters should be clear on whether they wish to submit a presentation for a plenary or working group session. At present, most working groups will solicit policy proposals, discussion points or other content directly via their mailing lists. If you’re not sure what kind of session you should be presenting at, please visit: https://ripe82.ripe.net/submit-topic/plenary-or-wg/ --------------------------------------------------------------------- The RIPE Meeting Code of Conduct --------------------------------------------------------------------- To ensure that RIPE Meeting values are upheld and that attendees experience a professional, respectful and safe meeting is a priority, please read the RIPE Meeting Code of Conduct: https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… --------------------------------------------------------------------- If you have any questions or requests concerning content submissions, please email pc at ripe.net . Jelte Jansen On Behalf of the RIPE PC

1 0

Spoofer Report for NLNOG for Jan 2021
by CAIDA Spoofer Project 08 Feb '21

08 Feb '21

In response to feedback from operational security communities, CAIDA's source address validation measurement project (https://spoofer.caida.org) is automatically generating monthly reports of ASes originating prefixes in BGP for systems from which we received packets with a spoofed source address. We are publishing these reports to network and security operations lists in order to ensure this information reaches operational contacts in these ASes. This report summarises tests conducted within nld. Inferred improvements during Jan 2021: none inferred Source Address Validation issues inferred during Jan 2021: ASN Name First-Spoofed Last-Spoofed 33915 TNF 2019-01-28 2021-01-19 8587 Infracom 2019-10-28 2021-01-27 213251 de-srv-2-mnt 2020-07-30 2021-01-13 213268 Cloudwebservices 2020-12-07 2021-01-12 Further information for these tests where we received spoofed packets is available at: https://spoofer.caida.org/recent_tests.php?country_include=nld&no_block=1 Please send any feedback or suggestions to spoofer-info(a)caida.org

1 0

Re: [NLNOG] weet iemand wie deze amateurs zijn?
by Thomas de Looff 02 Feb '21

02 Feb '21

Hoi Sabri, Bedankt voor het melden van de Abuse, dit heb ik doorgegeven. Zie dat er inderdaad een probleem is met ons AbuseIO systeem. Hier wordt aan gewerkt. PS: Het is ook mogelijk om de PCextreme support hiervoor te contacteren. Met vriendelijke groet, Thomas de Looff From: NLNOG <nlnog-bounces(a)nlnog.net> on behalf of Sabri Berisha <sabri(a)cluecentral.net> Date: Monday, 1 February 2021 at 20:31 To: nlnog <nlnog(a)nlnog.net> Subject: Re: [NLNOG] weet iemand wie deze amateurs zijn? Hi, Dusss... 3 jaar geleden werd ik nog geflamed toen ik deze club "amateurs" noemde (zij die mij kennen, weten precies wat we daar mee bedoelen). Dit, daarentegen, doet wel een klein beetje echt amateuristisch aan. Zit er iemand van pcextreme op de lijst? Ik had al ff op #nlnog rondgevraagd, zonder success. This is the mail system at host abuseio.pcextreme.nl. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <notifier(a)abuseio.pcextreme.nl>: Command died with status 1: "/usr/bin/php -q /opt/abuseio/libexec/mda". Command output: Could not open input file: /opt/abuseio/libexec/mda Ik wou alleen wat info@ spam melden. Thanks, Sabri ----- On Feb 22, 2018, at 10:41 AM, Sabri Berisha <sabri(a)cluecentral.net> wrote: Hi, Elke 30 seconden proberen ze het opnieuw: Jan 1 07:50:14 mail postfix/smtpd[1243]: NOQUEUE: filter: RCPT from unknown[185.103.159.70]: <vsaveliev(a)openprovider.ru>: Sender address triggers FILTER smtp-amavis:[127.0.0.1]:10024; from=<vsaveliev(a)openprovider.ru> to=<null(a)null.nl> proto=ESMTP helo=<mail-dev101-01.openprovider.nl> Jan 1 07:50:14 mail postfix/smtpd[1243]: NOQUEUE: reject: RCPT from unknown[185.103.159.70]: 554 5.7.1 <null(a)null.nl>: from=<vsaveliev(a)openprovider.ru> to=<null(a)null.nl> proto=ESMTP helo=<mail-dev101-01.openprovider.nl> root@mail:/var/log# host 185.103.159.70 70.159.103.185.in-addr.arpa domain name pointer hosted.by.pcextreme. <--- lekker profi PTR. role: PCextreme - Global NOC address: PCextreme B.V. address: Gyroscoopweg 134 En was dat hele openprovider.nl niet van Beefje? Thanks, Sabri Jr Network Amateur _______________________________________________ NLNOG mailing list NLNOG(a)nlnog.net http://mailman.nlnog.net/listinfo/nlnog _______________________________________________ NLNOG mailing list NLNOG(a)nlnog.net http://mailman.nlnog.net/listinfo/nlnog

1 0

weet iemand wie deze amateurs zijn?
by Sabri Berisha 01 Feb '21

01 Feb '21

Hi, Elke 30 seconden proberen ze het opnieuw: Jan 1 07:50:14 mail postfix/smtpd[1243]: NOQUEUE: filter: RCPT from unknown[185.103.159.70]: <vsaveliev(a)openprovider.ru>: Sender address triggers FILTER smtp-amavis:[127.0.0.1]:10024; from=<vsaveliev(a)openprovider.ru> to=<null(a)null.nl> proto=ESMTP helo=<mail-dev101-01.openprovider.nl> Jan 1 07:50:14 mail postfix/smtpd[1243]: NOQUEUE: reject: RCPT from unknown[185.103.159.70]: 554 5.7.1 <null(a)null.nl>: from=<vsaveliev(a)openprovider.ru> to=<null(a)null.nl> proto=ESMTP helo=<mail-dev101-01.openprovider.nl> root@mail:/var/log# host 185.103.159.70 70.159.103.185.in-addr.arpa domain name pointer hosted.by.pcextreme. <--- lekker profi PTR. role: PCextreme - Global NOC address: PCextreme B.V. address: Gyroscoopweg 134 En was dat hele openprovider.nl niet van Beefje? Thanks, Sabri Jr Network Amateur

2 2