swinog

swinog@lists.swinog.ch

2 participants
2989 discussions

A survey on performance diagnosis for Network functions/middleboxes
by Junzhi Gong 27 Jan '20

27 Jan '20

Dear SwiNOG community, Today's networks (data centers, ISPs, and enterprises) all run many hardware middleboxes and software network functions. The performance of these components is critical for network management and user experiences. However, when performance problems happen, it often takes a lot of human efforts to instrument and debug these systems especially when many network functions interact with each other and with traffic dynamics. We are a group of researchers from Harvard and AT&T who are building new diagnosis tools that can automatically find potential root causes for performance problems in network functions (especially those tail latency problems that are hard to diagnose). This project is led by my advisor Minlan Yu (Homepage: http://minlanyu.seas.harvard.edu/ <http://minlanyu.seas.harvard.edu/>), an Associate Professor in Harvard University. We're reaching out to the SwiNOG community to understand the performance problems you have seen and your needs on diagnosis tools. This will greatly help us to incorporate your needs in our tool. We plan to release our debugging tool for the community to use. We greatly appreciate your help in filling out the survey below. It should take less than 10 minutes to complete. The survey and the collected data are anonymous (so please do *not* include information that may identify you or your organization). All questions are optional, so if you don't like a question or don't know the answer, please skip it. In the survey, we use network functions as a general term to represent both hardware and software middleboxes. A summary of the aggregate results will be published as a part of a scientific article later this year. Survey URL: https://docs.google.com/forms/d/e/1FAIpQLSdx1j2BZzk_iEuIqHLDF20Rv_LuxLcrGze… <https://docs.google.com/forms/d/e/1FAIpQLSdx1j2BZzk_iEuIqHLDF20Rv_LuxLcrGze…> We would also be extremely grateful if you could forward this email to any operator you know beyond this SwiNOG mailing list. Junzhi Gong Harvard University

1 1

postmaster bluewin please contact
by Tobias Oetiker 22 Jan '20

22 Jan '20

Hi we got several reports from customers with bluewin addresses who do not get automated mails from "vermietung(a)floerli-olten.ch" in their mailboxes. according to our mailserver log mails get delivered to bluewin correctly, but they never arrive in the users mailboxes. does bluewin take it upon itself to destroy mail messages without notice ? Tobi Oetiker tobi.oetiker.ch

2 2

swisscom dtag cogent overbooking
by solutions＠datawire.ch 20 Jan '20

20 Jan '20

Hi I`m looking for someone from swisscom to make it`s customers happy :) Looks like we get a lot of swisscom traffic over cogent via dtag, and since the customers of our customers use swisscom, they have to deal with packet loss and slow connections every day after 3 pm until 6 pm. Cogent just told us to blame dtag for not peering, and swisscom for using dtag as an upstream. It looks like that «smart ict» customers have even more problems, even with outgoing connections, some of them started to work from home for faster connections (=different isp). Maybe somebody from the swisscom team can contact us noc(a)datawire.ch <mailto:noc@datawire.ch> Thank you very much 😉 Cheers Sebastian ___________________________ DATAWIRE AG Bösch 80A, 6331 Hünenberg Tel. +41 41 728 09 99 E-Mail: <mailto:solutions@datawire.ch> solutions(a)datawire.ch Website: <https://datawire.ch/> https://datawire.ch

1 0

DNS issue @ metanet?
by Benoit Panizzon 17 Jan '20

17 Jan '20

Hi Community Since yesterday we see more and more message of the kind: (host mail.zabli.ch[80.74.146.90] said: 450 4.7.1 Client host rejected: cannot find your hostname, [157.161.13.198] (host mx03.sui-inter.net[80.74.146.163] said: 554 IP name lookup failed. No PTR record found (host mx03.sui-inter.net[2a00:1128:0:146::163] said: 554 IP name lookup failed. No PTR record found (host mx01.sui-inter.net[2a00:1128:0:143::111] said: 554 IP name lookup failed. No PTR record found (host mail.musikstunden.ch[80.74.153.11] said: 450 4.7.1 Client host rejected: cannot find your hostname (host mail.schreinerei-furler.ch[80.74.145.2] said: 450 4.7.1 Client host rejected: cannot find your hostname (host mail.von-rickenbach.com[80.74.155.60] said: 450 4.7.1 Client host rejected: cannot find your hostname It looks like all those cases are hosted @ metanet. But there are some mailserver @ metanet which do accept emails. Is there any known DNS issue with metanet? According to their status page there are no issues. Or is something wrong with the readability of our DNS from outside AS6772? (ns1.imp.ch, ns2.imp.ch) 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 ______________________________________________________

1 0

FYI: admin.ch broken DNSSEC thus DNS down!
by Jeroen Massar 11 Jan '20

11 Jan '20

As mentioned on Swinog IRC (yes we are alive there, join us! :): admin.ch is unreachable due to broken DNSSEC. See: https://dnsviz.net/d/admin.ch/dnssec/ 8<---- ch to admin.ch: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. (162.23.37.16, 162.23.37.160, 212.103.72.85, 2a00:c38:2:28:0:ffff:d467:4855, UDP_-_EDNS0_4096_D_K) ch to admin.ch: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. (162.23.37.16, 162.23.37.160, 212.103.72.85, 2a00:c38:2:28:0:ffff:d467:4855, UDP_-_EDNS0_4096_D_K) ------>8 (I got a screencap of the page for later, just in case it get fixed/changed in the meantime; swinog only allows 40KiB attachments which would ruin the res too much for it to be useful :) Thus for all ISPs on this list: tell your customers that it is an admin.ch issue, not something you can solve (unless you disable dnssec validation for admin.ch, which is an option, but kinda against dnssec). (Fortunately it is not tax time or something like that) For folks working at admin.ch: I offer myself pro bono to help out resolving the issue, don't hesitate to reach out (email or contact details on my homepage). We can then replicate a stable environment as described in: https://jeroen.massar.ch/presentations/vid/SwiNOG35-Managing_sleep_with_a_r… or otherwise likely improve the situation to avoid such outages. Good luck folks at admin.ch in resolving this.. Greets, Jeroen

1 1

DNSSEC admin.ch
by Samuel Aymon 10 Jan '20

10 Jan '20

Hello everyone, If someone at admin.ch read this before it is too late, please check your DNSSEC config. All admin.ch domains and subdomains are unresolvable due to an errors in your DNSSEC. More infos here: https://www.admin.ch/ or here: https://dnssec-debugger.verisignlabs.com/admin.ch or here: https://dnsviz.net/d/admin.ch/dnssec/ Best regards Samuel

1 0

Fwd: [ncc-announce] [news] De-bogonising 2a10::/12
by Arnold Nipper 09 Jan '20

09 Jan '20

Happy New Year and a successful 2020 to all of you. Cheers Arnold -------- Weitergeleitete Nachricht -------- Betreff: [ncc-announce] [news] De-bogonising 2a10::/12 Datum: Wed, 8 Jan 2020 12:23:17 +0100 Von: Nikolas Pediaditis <npediaditi(a)ripe.net> An: ncc-announce(a)ripe.net Dear colleagues, A few months ago the RIPE NCC became the first RIR to receive an additional /12 IPv6 allocation (2a10::/12) from IANA. We will soon begin to delegate space from this IPv6 block to LIRs. Prior to this, in order to improve routability and minimise the risk of filtering, the RIPE NCC will perform several de-bogonising activities in the next few weeks. We plan to start announcing the full /12, as well as a few /32 or longer blocks out of 2a10::/12 from AS12654 (RIPE Routing Information System (RIS)), within the next few days. We will analyse data from RIS and RIPE Atlas and we plan to write up an analysis around this effort. We want to remind everybody to update their bogon filters and allow routes originating from 2a10::/12 in their network. Kind regards, Nikolas Pediaditis Registration Services and Policy Development Manager RIPE NCC -- Arnold Nipper email: arnold(a)nipper.de mobile: +49 172 2650958

1 0

Fwd: [ncc-announce] [news] De-bogonising 2a10::/12
by Massimiliano Stucchi 08 Jan '20

08 Jan '20

Guys, update your filters! -------- Forwarded Message -------- Subject: [ncc-announce] [news] De-bogonising 2a10::/12 Date: Wed, 8 Jan 2020 12:23:17 +0100 From: Nikolas Pediaditis <npediaditi(a)ripe.net> To: ncc-announce(a)ripe.net Dear colleagues, A few months ago the RIPE NCC became the first RIR to receive an additional /12 IPv6 allocation (2a10::/12) from IANA. We will soon begin to delegate space from this IPv6 block to LIRs. Prior to this, in order to improve routability and minimise the risk of filtering, the RIPE NCC will perform several de-bogonising activities in the next few weeks. We plan to start announcing the full /12, as well as a few /32 or longer blocks out of 2a10::/12 from AS12654 (RIPE Routing Information System (RIS)), within the next few days. We will analyse data from RIS and RIPE Atlas and we plan to write up an analysis around this effort. We want to remind everybody to update their bogon filters and allow routes originating from 2a10::/12 in their network. Kind regards, Nikolas Pediaditis Registration Services and Policy Development Manager RIPE NCC

1 0

Cleanmail contact
by Patrick Velder 11 Dec '19

11 Dec '19

Hi there Is there anyone from cleanmail? They are rejecting mails from my server (Reason: "Host blocked. Request whitelisting"). Forward/reverse DNS/HELO matches, no blacklist entries, no spamming, ... Nobody is answering mails (sent using another server). Best regards Patrick

1 0

Equinix PIN
by Michael Koloff 05 Dec '19

05 Dec '19

Hello I assume that some of you also have an account / access to Equinix data centers. And that you have been informed that you have to define a new 6-digit PIN in your account. Two things make me wonder, see the FAQ here: https://equinix.app.box.com/s/lcrutseubx9vebi4m21dir8fp66fmmlq Extract: I'm trying to select my 6-digit PIN but am receiving an error message. --> OUR SECURITY SYSTEMS ONLY ALLOW EACH PIN/COMBINATION TO BE USED FOR ONE PERSON. If you are receiving an error, please input a new combination of numbers or use the "Generate PIN" selection to generate a random, unique PIN. I forgot my 6-digit PIN, what should I do? / I want to change my 6-digit PIN DUE TO SECURITY REASONS, where can I change it? --> ....Your 6-digit PIN cannot be changed.... In concrete terms, this means that every person has a PIN, but no other person in the world can have the same PIN. This means that a maximum of 900,000 people worldwide can have access to Equinix data centres. (PINs with leading zero are not allowed) And if someone knows your PIN, at least your first authentication factor is broken and cannot be changed. Support has confirmed this behavior to me so far. Am I the only one here who finds that very weird? How do you deal with it? Best regards Michi -- Michael Koloff System- & Networkengineer sasag Kabelkommunikation AG Mühlenstrasse 21 8201 Schaffhausen Telefon: +41 52 633 01 72 mkoloff(a)sasag.ch www.sasag.ch

3 2

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