swinog

swinog@lists.swinog.ch

2996 discussions

Hardware, Netzwerk abzugeben, 6 St. HPE P10115-B21 neuwertig
by Mueller Urs SBB CFF FFS 29 Sep '26

29 Sep '26

Hello / Hallo Wir haben aus einem Fehlkauf folgende Ware abzugeben: * 6 Stück HPE P10115-B21 Broadcom 57414 10/25GbE Dualport SFP28 OCP3 Adapter zB für HPE DL 3xx Gen 11 * Aus Originallieferung in Server ausgebaut, nie benutzt * In Antistatikbeuteln und Schachteln (der bei uns danach eingebauten BCM 57608) Angebote bitte direkt off liste. Wir sind ein verarmter Bundesbetrieb (Schuldenlast, siehe Suchmaschine) und brauchen Geld 😉 Grüsse, Urs SBB AG Konzernsicherheit Bollwerk 10, 3000 Bern 65 Mobil +41 79 433 21 67<tel:+41794332167> urs.bf.mueller(a)sbb.ch<mailto:urs.bf.mueller@sbb.ch> / www.sbb.ch<http://www.sbb.ch/> C2 - Intern: Diese Informationen sind vertraulich zu behandeln und dürfen nur im geschäftlichen Kontext verwendet werden. Eine Weitergabe an Dritte ist nur in Abstimmung mit der SBB zulässig. // C2 – Interno: Queste informazioni devono essere trattate in modo confidenziale e possono essere utilizzate solo in ambito aziendale. La trasmissione a terzi è consentita solo previo accordo con le FFS. // C2 – Interne: Ces informations doivent être traitées de manière confidentielle et ne doivent être utilisées que dans le contexte des affaires. Un transfert à des tiers est permis uniquement sous réserve de l’accord des CFF. // C2 - Internal: - This information is to be treated as confidential and may only be used for business purposes. Disclosure to third parties is only permitted with the prior agreement of SBB.

2 1

PCH 2026 global peering survey
by Bill Woodcock 29 Sep '26

29 Sep '26

tl;dr: the survey is at https://pch.net/survey Background: Every five years, beginning in 2011, PCH has conducted a comprehensive global survey characterizing Internet peering agreements. They are the only ones of their kind, and are relied upon not only by network operators, but also by legislators and regulators throughout the world to understand the Internet interconnection landscape. Our write-ups of the prior surveys can be found here: https://www.pch.net/resources/Papers/peering-survey/PCH-Peering-Survey-2011… https://www.pch.net/resources/Papers/peering-survey/PCH-Peering-Survey-2016… https://www.pch.net/resources/Papers/peering-survey/PCH-Peering-Survey-2021… …and video of the NANOG presentation of the 2016 results is here: https://www.youtube.com/watch?v=lPuoBmxyXMc At the time of the 2011 survey, we committed to repeating the survey every five years, to provide time-series data about the direction peering trends take. We’re now conducting the fourth iteration of the survey. Among other things, the surveys have helped establish a better understanding of trends in: • The increasingly uniform global norms of interconnection • National preferences within the network operator community for country of governing law • The long tail of small networks which don’t yet support IPv6 routing • The significance of multilateral peering agreements in the density of the interconnection mesh These findings, particularly the first, have been invaluable in giving regulators in the vast majority of the world’s countries a data-driven basis for refraining from prescriptively regulating Internet interconnection. They have demonstrated in objective terms that the Internet self-regulates in a way that’s more globally uniform and closely harmonized than any coordination of national regulatory bodies could accomplish. Participation: The survey is global in scope, and our goal is to reflect the diversity of peering agreements in the world. Your participation ensures that your norms and ways of doing business are represented accurately and proportionately in the dataset. If you don’t participate, the way you do business will be less well-represented in the data, and will seem less normal to regulators and policy-makers. We’re interested in large ISPs and small ISPs, ISPs in Afghanistan and in Zimbabwe, bilateral agreements and multilateral, private and public. Our intent is to be as comprehensive as possible. In 2011, the responses we received represented 41% of the world’s ISPs, across 96 countries; in 2016, 65% of the world’s ISPs, across 148 countries; in 2021, 76% of the world’s ISPs across 192 countries. Our aim is to be equally inclusive this year. Since our principal method of soliciting participation is via NOG mailing lists, I’m afraid many of you will see this message several times, on different lists, for which we apologize in advance. Privacy: In 2011, 2016, and 2021, we promised to collect the smallest set of data necessary to answer the questions, to perform the analysis immediately, and not to retain the data after the analysis was accomplished. In that way, we ensured that the privacy of respondents was fully protected. We did as we said, no data was leaked, and the whole community benefited from the trust that was extended to us. We ask for your trust again now as we make the same commitment to protect the privacy of all respondents, using the same process as was successfully employed the last three times. We are asking for no more data than is absolutely necessary. We will perform the analysis immediately upon receiving all of the data. We will delete the data once the analysis has been performed. The Survey: We would like to know your Autonomous System Number, and the following five pieces of information relative to each other AS you peer with: • Your peer’s ASN (peers only, not upstream transit providers or downstream customers) • Whether a written and signed peering agreement exists (the alternative being a less formal arrangement, such as a "handshake agreement") • Whether the terms are roughly symmetric (the alternative being that they describe an agreement with different terms for each of the two parties, such as one compensating the other, or one receiving more or fewer than full customer routes) • What jurisdiction of governing law is defined, if any • Whether IPv6 routes are being exchanged (this year, we’ll still assume that IPv4 are) The easiest way for us to receive the information is as a tab-text or CSV file or an Excel spreadsheet, consisting of rows with the following columns: Your ASN: Integer Peer ASN: Integer Written agreement: Boolean [true,1,yes,y] or [false,0,no,n] Symmetric: Boolean [true,1,yes,y] or [false,0,no,n] Governing Law: ISO 3166 two-letter country-code, or empty IPv6 Routes: Boolean [true,1,yes,y] or [false,0,no,n] For instance: 42 <tab> 715 <tab> false <tab> true <tab> us <tab> true <cr> 42 <tab> 3856 <tab> true <tab> true <tab> us <tab> true <cr> We need the ASNs so we can avoid double-counting a single pair of peers when we hear from both of them, and so that when we hear about a relationship in responses from both peers we can see how closely the two responses match, an important check on the quality of the survey. As soon as we've collated the data, we'll strip the ASNs to protect privacy, and only the final aggregate statistics will be published. We will never disclose any ASN or any information about any ASN. We'd like to finish collecting data in the first week of October, about two weeks from now. If you’re peering with an MLPA route-server, you’re welcome to include just the route-server’s ASN, if that’s easiest, rather than trying to include each of the peer ASNs on the other side of the route-server. Either way is fine. If all of your sessions have the same characteristics, you can just tell us what those characteristics are once, your own ASN once, and give us a simple list of your peer ASNs. If your number of peers is small enough to be pasted or typed into an email, rather than attached as a file, and that’s simpler, just go ahead and do that. If you have written peering agreements that are covered by non-disclosure agreements, or if your organizational policy precludes disclosing your peers, but you’d still like to participate in the survey, please let us know, and we’ll work with whatever information you’re able to give us and try to ensure that your practices are statistically represented in our results. If you're able to help us, please email me the data in whatever form you can. If you need a non-disclosure, we're happy to sign one. Finally, if there are questions you’d like us to try to answer when we analyze the data, please suggest them, and if there are any additional questions you’d like us to include in future iterations of the survey, please let us know so that we can consider including them in the 2031 survey. Please respond by submitting your survey at https://pch.net/survey or emailing it to me directly (woody(a)pch.net, not replying to the NOG mailing list), by the second week of October. Thank you for considering participating. We very much appreciate it, and we look forward to returning the results to the community. -Bill Woodcock Secretary General Packet Clearing House

1 0

CHNUG #4 – Rapperswil, August 26
by Severin Dellsperger 19 Aug '26

19 Aug '26

Hi all, At SwiNOG #41, I introduced CHNUG, the Swiss Network User Group. We're now hosting our fourth meetup on August 26 in Rapperswil, at OST. Expect three technical talks: * Network Monitoring with the gNMIc Operator | Roman Weber and Valentino Diller (OST) * Managing IP Allocation with an Open-Source DDI | Marco Martinez * What's Next for Nornir: Project Update and Roadmap | Damien Garros (OpsMill) The event is free to attend and includes a burger party afterwards. More info and registration: https://events.chnug.ch/event/5/chnug-4 Looking forward to seeing some of you there. Best, Severin Severin Dellsperger Senior Network and Research Engineer P central +41 58 257 44 99<tel:+41582574499> P direct +41 58 257 44 76<tel:+41582574476> severin.dellsperger(a)ost.ch<mailto:severin.dellsperger@ost.ch> OST – Eastern Switzerland University of Applied Sciences INS – Institute for Network and Security | Oberseestrasse 10 | 8640 Rapperswil | Switzerland | www.ost.ch<http://www.ost.ch>

1 0

Contact to mail.swisscom.com (or sharedit.ch / itoper.local) postmaster?
by Benoit Panizzon 31 Jul '26

31 Jul '26

Hi We have one customer with their MX on mail.swisscom.com. Since about two months, our customer experiences huge delays (we talk about days and even weeks) when receiving our emails (mostly affected: PDF Invoices but also happened with other simple text test emails without attachments). From what I see from a header of an affected email delayed 48 hours, supplied by the customer, the delay happens 'internally' between: mail.swisscom.com (sg007451.sharedit.ch) and pps.reinject (sg007430.itoper.local [127.0.0.1]) Our customer was not yet able to get a contact at Swisscom to explain the cause and to find the cause or how fix it (also because there seem to be several parties, including government involved in running this service and it's not clear which party is in charge. An request for help to the RIPE contact for the IP range remained unanswered. Have others observed similar issues? I could imagine all PDF emails somehow get quarantined and have to manually be release by 'some human', but our customer is not aware of such a functionality. Does anyone how know operates sharedit.ch or itoper.local and cold start an investigation? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 1

### SwiNOG #41 (2026-04-28) - Call for Papers ###
by Simon Ryf 24 Jul '26

24 Jul '26

Dear SwiNOG community, Please forward me to whomever you think should know about our community and the upcoming event. This is the official Call for Paper email. Please submit your proposal via https://www.swinog.ch/cfp/ The 41st meeting of the Swiss Network Operators Group (SwiNOG) will be held in Berne on top of the Gurten on Tuesday April 28th, 2026. Location: https://wego.here.com/l/46.91963060309784,7.439032069847434 Important Dates for http://www.swinog.ch/meetings/swinog41/ 30.01.2026 Call for Papers 02.02.2026 Registration opens -> https://register.swinog.ch/ 29.03.2026 Publication of preliminary agenda 19.04.2026 Registration closes 24.04.2026 Deadline for all slides 28.04.2026 Meeting Day Topics for Presentations/Talks Please re-submit your paper if you're still up with a topic which you have submitted earlier. The number and length of presentations per session is not fixed, although we prefer it to be between 5 to 30 minutes. Here is a non-exhaustive list of typical SwiNOG meeting topics: * Security, DDOS Mitigation, * IPv6 * Open-Source- / GitHub projects * International view of the internet (incidents, outages, measurements) * Routing & Peering * Applications (DNS, Web, Network Virtualization, Orchestration, Monitoring etc.) * Takeaways from your projects / troubleshooting-sessions * Legal issues (BÜPF, etc.) * Telecommunication politics (Net Neutrality, Incumbent monopoly, etc.) * Off-Topic if you think the audience will enjoy Feel free to talk to us about any kind of topic and collaboration! Or you can always start a discussion on the list - I'm sure people join in. Or join our telegram group at https://t.me/SWINOG Language of Slides and Talks The whole day will be hold in English, therefore we kindly ask you to produce your presentation in English. Submission Guidelines * All submissions must have a strong technical bias and must not be promotional. * We also welcome lightning talks (3-5 Minutes). If entertaining – they can also be completely off-topic. * Presentations should be suitable for a target audience of technicians from varied backgrounds, working for companies whose sizes may vary considerably. * Presentation will be published (PDF) on the SwiNOG website after the event (if confirmed/permitted by the speaker). * On request we publish modified slides (removed confidential content, etc.) * Presentations should be suitable for a target audience of technicians from varied backgrounds, working for companies whose sizes may vary considerably. To submit a proposal for a presentation, please fill in the form at https://www.swinog.ch/cfp/ We also welcome suggestions for specific presentations which you feel would be valuable to the SwiNOG community and we try to chase a speaker for it. Greetings, Simon SwiNOG Core Team swinog-core(a)swinog.ch<mailto:swinog-core@swinog.ch> General Information (SwiNOG Community) The Swiss Network Operators Group (SwiNOG) is an informal group of people who are concerned with engineering and operation of the Swiss Internet. SwiNOG exists to enhance the quality of Internet services available in Switzerland. It does this by fostering the free exchange of technical ideas and information between different companies and organisations. SwiNOG is a community for professionals who are operating, designing, or researching the Internet. It provides a technical forum where those working on, with and for the Internet can come together to solve problems with every aspect of their (net)work. The meeting is designed to provide an opportunity for the exchange of information among network operators, engineers, researchers, and other professionals close to the network community. More information about SwiNOG can be found at http://www.swinog.ch<http://www.swinog.ch/> Information about the meeting will be published at http://www.swinog.ch/meetings/swinog41/ General Information (SwiNOG Organisation) The SwiNOG Organisation Association is a non-profit association under article 60 and further of the swiss civil law. It manages the SwiNOG community ressources (domain, web, mailing-lists, etc..) and organises SwiNOG meetings. Contact: SwiNOG Organisation 8000 Zurich Switzerland

1 1

BGP/RPKI hygiene checker + monitoring for small operators (free check, FR/EN)
by N&R consulting 22 Jul '26

22 Jul '26

Hi all, first post here from a neighbour in France, so a quick intro: I run Sentinelle Routage, a small French BGP/RPKI monitoring service aimed at small and mid-size operators (hijack/leak alerts, RPKI-invalid detection, ROA hygiene, loss of visibility). Two things that might be useful to this list: - A free, no-signup checker that grades an ASN's routing hygiene (ROA coverage, RPKI-invalids, overly permissive maxLength per RFC 9319, IRR consistency): https://sentinelle-routage.fr (EN available) - A sample of the monitoring report we generate (fictional network, RFC 5398/5737 resources): https://sentinelle-routage.fr/rapport-exemple.pdf Under the hood it runs on RIS data (RISwhois + RIS Live, used with attribution) and a self-hosted Routinator instance, no RIPEstat involved. Feedback from operators here is very welcome, especially on the maxLength/RFC 9319 warnings: too noisy, or useful? Some background on why we flag overly permissive maxLength: https://sentinelle-routage.fr/roa-maxlength.html Best, Abdelaziz El Borgi N&R Consulting / Sentinelle Routage https://sentinelle-routage.fr

1 0

### SwiNOG #42 (20/21 October 2026) - Registration Open ###
by Simon Ryf 20 Jul '26

20 Jul '26

Dear SwiNOG community, Registration for SwiNOG #42 is now open! SwiNOG #42 is a little different. After all, when the number is forty two, doing things the usual way somehow feels wrong! Instead of our traditional packed one-day format, #42 will be held over two days, giving us a more relaxed, spread-out agenda. Where: ENTER Technikwelt Solothurn - Gewerbestrasse 4, 4552 Derendingen Agenda Day ONE - 20.10.2026: 11:40 (optional) Shuttle Bus from Railway station Solothurn 12:00 - 13:00 Lunch & Networking 13:00 - 17:30 Presentations 17:30 - 18:15 Apreo & Drinks 18:30 (optional) Shuttle Bus to Railway station Solothurn 18:15 - 21:30 Dinner & Networking + Guided tour ENTER Museum (!! ONLY with Social Event Ticket) 22:00 (optional) Shuttle Bus to Railway station Solothurn Agenda Day TWO - 21.10.2026: 08:40 (optional) Shuttle Bus from Railway station Solothurn 09:00 - 12:30 Presentations 12:30 - 13:30 Lunch & Networking 13:40 (optional) Shuttle Bus to Railway station Solothurn 13:30 - 16:30 1:1 Meetings (Organizer Tool will be made available soon) 16:40 (optional) Shuttle Bus to Railway station Solothurn If we do have enough exciting talks, we might extend the Presentations into the Afternoon - TBD. Registration * Decide if you want the “Meeting & Social Event” or “Meeting” Ticket * Device if you want the optional Shuttle Bus from/to Railway station Solothurn Register here: https://register.swinog.ch Travel By Public Transport: Train to Bahnhof Solothurn, from there we recommend the SwiNOG-Shuttle-Bus, but you can also take the public bus Solothurn, Hauptbahnhof -> Derendingen, Freiheit By Car: Free parking directly at the Venue, Gewerbestrasse 4, 4552 Derendingen Staying overnight? If you would like to stay overnight we recommend the following hotels. Both are within walking distance of Solothurn main station, making them an ideal choice for SwiNOG#42 attendees: H4 Hotel Solothurn: https://www.h-hotels.com/de/h4/hotels/h4-hotel-solothurn Hotel Ambassador: https://www.ambassador-hotel.ch/ Please note: There is no special SwiNOG hotel rate, bookings should be made through the hotel’s regular booking channels. See you at SwiNOG #42 SwiNOG Core Team

1 0

Someone from t-online.de in this list?
by Claudio Kuenzler 20 Jul '26

20 Jul '26

Hello all, might be a long shot but worth a try. Is there something in this list from t-online.de that could help with a mail delivery issue? If yes, please contact me directly off-list. I already tried to contact the "official way", but haven't received an answer there. thank you, CK

1 0

SwiNOG #42 - 20/21.10.2026 - Save the Date
by Simon Ryf 06 Jul '26

06 Jul '26

Dear SwiNOG community, We’re working hard to make the second event this year possible. Location: Enter Technikwelt Solothurn Timetable: 20.10 12:00 - 13:30 Lunch & Networking 20.10 13:30 - 17:30 Presentations 20.10 18:00 - 21:00 Dinner & Networking + Museum Visit — 21.10 09:00 - 12:00 Presentations 21.10 12:00 - 13:30 Lunch & Networking 21.10 16:30 - 16:00 1:1 Meetings We’re still working on the details, please allow us some more time to finalise them. Further info will be available soon - we’ll keep you posted. — 13.07.2026 Call for Papers start 20.07.2026 Registration opens 20 & 21.10.2026 Meeting Day — Please save the date. Greetings Simon SwiNOG Core Team

1 0

RTBH Support Across the Industry
by James Bensley 03 Jul '26

03 Jul '26

Dear Community, We see that RTBH is not as effective as it could be, for various reason, just a few include: * Not all networks support RTBH. * Networks that do support RTBH implement it differently to each other. * There is no one place where one can easily find the info for how to use RTBH with a given network. * Operators have different ideas about how / when / where / why someone should / shouldn’t use RTBH. To this end, we have created the first of two surveys. This first one is quantitative and captures how networks have implemented RTBH and provides (1) a public repository which anyone can use to look-up the RTBH details for their peers/upstreams, and (2) an insight into the (mis-)alignment of RTBH implementations across the industry. Please take the time to fill out the short survey for your own network (even if you don’t support RTBH!), and if you can, please fill it out for other networks where you know how they have implemented RTBH (e.g., peers you use RTBH with): https://docs.google.com/forms/d/e/1FAIpQLScg2Bvr_14onOtZRdoK2SNd0kCHFtqsdw-… (^ No login required) The data ends up in this public repository (you can of course make a pull request directly if you want): https://remotely-triggered-black-hole.github.io/rtbh/ The second survey we are working on will be qualitative, to gather information from the industry community on why you do / don’t support RTBH, when do you use it, how do you think the routing should be secured, etc. The long term goal is to use the data from both surveys as input in to a community effort to improve RTBH alignment across the industry and improve it’s effectiveness for all (e.g. maybe we produce a new BCOP for implementing RTBH, or usage guidelines for blackholing, or maybe a new RFC is required to secure the filtering; regardless, the first step is to gather data about the status quo and review that data to get a baseline of where we are at today). Any questions, please let me know, and thank you for your time and help, it is appreciated. With kind regards, James.

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

swinog