swinog

swinog@lists.swinog.ch

2933 discussions

Swiss4net : any experiences with this company ?
by Félix Curinga 20 Nov '20

20 Nov '20

Hi all, If someone is close to a city or a provider having experiences with Swiss4Net , can you please contact me directly. Thanks --félix -- Félix Curinga

1 0

Fwd: [PDB Announce] PeeringDB Satisfaction Survey
by Arnold Nipper 17 Nov '20

17 Nov '20

Guten Abend zusammen, wer mit Interconnection - sei es Colo, IXP oder Netzbetreiber - zu tun hat, dem ist PeeringDB ein Begriff und die gehört zum Toolset. Bitte lasst uns daher eure Meinung wissen. --- Buona sera a tutti, Chiunque si occupi di interconnessione, sia esso Colo, IXP o operatore di rete, conosce PeeringDB ed è parte del set di strumenti. Quindi per favore fateci sapere cosa ne pensate. --- Bonsoir à tous, Quiconque s'occupe de l'interconnexion - que ce soit Colo, IXP ou opérateur de réseau - connaît PeeringDB et fait partie de l'ensemble d'outils. Alors faites-nous savoir ce que vous en pensez. --- Good evening everyone, Anyone who deals with interconnection - be it Colo, IXP or network operator - is familiar with PeeringDB and it is part of your toolset. So please let us know what you think. Gruß Arnold -------- Weitergeleitete Nachricht -------- Betreff: [PDB Announce] PeeringDB Satisfaction Survey Datum: Mon, 2 Nov 2020 07:55:40 -0800 Von: Leo Vegoda <leo(a)peeringdb.com> An: pdb-announce(a)lists.peeringdb.com We want input from network operators, exchange operators, facility providers, content distributors and anyone who uses our interconnection database. This year we are running an anonymous satisfaction survey in addition to the usual feedback gathering we employ. The survey will be available here: https://surveyhero.com/c/f7be5236 until 23:59 UTC on 20 November 2020. We would like your feedback to help us make PeeringDB more useful to everyone involved in connecting networks.This survey will help us understand what is important to you and how satisfied you are with what we are doing. We will use your responses to focus our product roadmap on the improvements that will make things better for you. If you have specific comments or suggestions, we’d love you to leave them along with your ratings. This is the first survey we are making available in multiple languages. In this survey we are using the six UN languages for the questions. That said, we’re happy with people providing free text comments in another whichever language they are happiest expressing themselves. We’ll share the results and the new product roadmap early in 2021. Leo Vegoda on behalf of PeeringDB ProductCom _______________________________________________ Pdb-announce mailing list Pdb-announce(a)lists.peeringdb.com https://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-announce -- Keep calm, keep distance, keep connected! Arnold Nipper email: arnold(a)nipper.de mobile: +49 172 2650958

1 0

Fwd: [uknof] PeeringDB Satisfaction Survey
by Massimiliano Stucchi 17 Nov '20

17 Nov '20

-------- Forwarded Message -------- Subject: [uknof] PeeringDB Satisfaction Survey Date: Mon, 2 Nov 2020 10:29:01 -0800 From: Leo Vegoda <leo(a)vegoda.org> To: uknof(a)lists.uknof.org.uk PeeringDB is a non-profit, freely available, user-maintained, database of networks, and the go-to location for interconnection data. The database facilitates the global interconnection of networks at Internet Exchange Points (IXPs), data centers, and other interconnection facilities, and is the first stop in making interconnection decisions. We want input from network operators, exchange operators, facility providers, content distributors and anyone who uses our interconnection database. This year we are running an anonymous satisfaction survey in addition to the usual feedback gathering we employ. The survey will be available here: https://surveyhero.com/c/f7be5236 until 23:59 UTC on 20 November 2020. We would like your feedback to help us make PeeringDB more useful to everyone involved in connecting networks.This survey will help us understand what is important to you and how satisfied you are with what we are doing. We will use your responses to focus our product roadmap on the improvements that will make things better for you. If you have specific comments or suggestions, we’d love you to leave them along with your ratings. This is the first survey we are making available in multiple languages. In this survey we are using the six UN languages for the questions. That said, we’re happy with people providing free text comments in another whichever language they are happiest expressing themselves. We’ll share the results and the new product roadmap early in 2021. Leo Vegoda on behalf of PeeringDB ProductCom

1 0

Fwd: [ncc-announce] [news] LIR Account closure? Notify us by 1 December
by Massimiliano Stucchi 16 Nov '20

16 Nov '20

If you have an LIR account you would like to close before the end of the year, pay attention to this email. -------- Forwarded Message -------- Subject: [ncc-announce] [news] LIR Account closure? Notify us by 1 December Date: Mon, 16 Nov 2020 13:38:00 +0100 (CET) From: henriette(a)ripe.net To: ncc-announce(a)ripe.net Dear RIPE NCC members, We would like to inform you that a request to close an LIR account or any request that will result in the closure of an LIR account should be submitted in full before 1 December 2020. This includes closures that result from policy transfers and changes in business structures. Any requests submitted after this date mean that you could be invoiced for 2021. The request should contain all the requested information and documents in order for the RIPE NCC to process it before the end of the year. An overview of the required documents can be found at: https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/req… For requests resulting in the closure of an LIR account that are submitted later than 1 December 2020, or requests that are incomplete, we can not guarantee that the LIR account will be closed before 31 December 2020. Invoices for 2021 will be issued for LIR accounts still open on 1 January 2021. Best Regards, Henriette van Ingen Registry Services Assistant Manager RIPE NCC

1 0

Cloudflare 'relaying' complaints and take down notices to the hosting ISP instead of handling them.
by Benoît Panizzon 12 Nov '20

12 Nov '20

Hi Community A website (no imprint, domain registered via anonymous proxy), which allegedly breaks some copyright laws, is proxied by CloudFlare. CloudFlare got a DMCA take-down notice from an attorney and replied to the attorney, that the site in question is hosted at AS6772, ImproWare AG, but did not tell the attorney the IP Address (nor the customer which could have been looked up via RIPE). Cloudflare also contacted us and told the IP Address. I contacted the customer in question. He states he has nothing to do with that website (I might be tempted to doubt this statement, it could be a customer of the customer who is involved...). But I cannot verify: I have no access to the logs of our customer's Server. I have no access to the proxy logs @ Cloudflare. The attorney is now getting a bit impatient and considers filing a legal complaint against us to have us 'solve the issue'. So I contact Cloudflare as they must have a customer who ordered said proxy service with them and probably pays for it. Cloudflare could handle the issue themself, directly at the source, knowing the paying 'culpit'. I quickly got the reply, that they are not responsible for content hosted by their customer, therefore they relay complaints to the ISP in charge of the IP address in question. That is a bit weird.... isn't it? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- 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

Übersetzer für PeeringDB gesucht // SwiNOG
by Arnold Nipper 05 Nov '20

05 Nov '20

[ German only for obvious reasons ] Hallo SwiNOG community seit einiger Zeit gibt es PeeringDB [0] nicht nur in Englisch, sondern in zwölf weiteren Sprachen; unter anderem Deutsch (de_de). Da PeeringDB ständig erweitert wird, sind auch laufend neue Übersetzungen im kleineren Umfang notwendig. Hast du Lust, an der Übersetzung mitzumachen? Ja? * du hast einen PeeringDB-Account [1] * registriere dich auf der Übersetzerliste [2] * melde dich bei dem Übersetzungstool [3] an * fülle dein Profil aus [4] * starte mit der Übersetzung [5] Wenn Du Fragen hast, komm gerne auf mich zu. Viele Grüße Arnold [0] https://peeringdb.com/ [1] https://peeringdb.com/register [2] http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-translate [3] https://translate.peeringdb.com/accounts/login/?next=/ [4] https://translate.peeringdb.com/accounts/profile/ [5] https://translate.peeringdb.com/languages/de/peeringdb/ -- Keep calm, keep distance, keep connected! Arnold Nipper email: arnold(a)nipper.de mobile: +49 172 2650958

1 0

IANA AS Numbers Registry Update
by Selina Harrington 03 Nov '20

03 Nov '20

Hi, The IANA AS Numbers registry has been updated to reflect the allocation of the following blocks to ARIN: 399261-400284 Assigned by ARIN 2020-11-02 400285-401308 Assigned by ARIN 2020-11-02 You can find the registry at: https://www.iana.org/assignments/as-numbers/ The allocation was made in accordance with the Policy for Allocation of ASN Blocks to Regional Internet Registries: https://www.icann.org/resources/pages/global-policy-asn-blocks-2010-09-21-en Best Regards, -- Selina Harrington Lead IANA Services Specialist

1 0

Handling of UCE / RBL while minor misconfigurations
by Mueller Urs SBB CFF FFS 27 Oct '20

27 Oct '20

Hello list I am writing on behalf of a colleague who is operating a small hosting business, mainly focused on the setup of the cms and consulting. He is not on the list and asked me to put his words into it. He had the following dispute with an ISP, but I will let him speak (translation via deepl reviewed by me). --- We run a small hosting business on three managed servers, which we rent from a well-known Swiss ISP and host our customers (SMEs and individuals) there. We have had the misfortune three times that the IP of one of our servers got on the blacklist "UCEprotect" through no fault of our own: http://www.uceprotect.net In each of these cases a Zurich-based ISP was at fault, who apparently is involved in this blacklist - he didn't want to tell us how exactly, but in the first case he still apologized and he was able to remove the IP from the blacklist at short notice without any problems. Therefore we assume that he has a great influence there. The first times the IP was blacklisted because there was a chaos with a telephone system (short: bounces on non-existent addresses). Last week the IP came back on UCEprotect because a customer had edited his SPF entry incorrectly (he forgot to enter the IP of the server) - a single mail from our customer to a customer of the mentioned Zurich provider was already enough for an entry on the RBL. There was neither a spam dispatch nor a spamtrap; the wrong SPF automatically led to a blacklisting of the whole IP with more than 200 hosting customers, who then of course got mail problems. It would be normal and justifiable for a mail to be classified as spam because of a wrong SPF record. However, we find it very questionable that a whole IP is "dragged into the abyss" because of this. Especially since we have been fighting against spam for almost 25 years, keeping our servers clean and thus "fighting on the same side", it is all the more irritating to have such obstacles put in the way by this provider. The fact that customers can adjust the DNS entries and thus the SPF record themselves is normal for many providers. A single hosting customer's mistake should not also affect his provider and dozens of other customers. The methods used for an automatic entry on the blacklist UCEprotect seem at least questionable. I would like to show the provider that he means well, but that it can easily hit the wrong people - and would be grateful for input. After the first case still said "sorry, you've been good to me", there are no more answers to the question whether he really considers these methods to be useful. What do you think can be done here? I don't have time and money for a legal dispute, and blocking any traffic to his IPs to prevent damage to our IPs would probably not be clean either. --- So, what is your opinion on the behavior of this ISP? Me, Urs, I am with my colleague and I think, it's not acceptable to block a whole IP just while receiving one or a small number of mail without a correct SPF. Thank you your thoughts, I will collect it and send it to my colleague. Urs Müller Schweizerische Bundesbahnen SBB Senior Architekt / Product Owner Informatik Operations-Management / CYBER Poststrasse 6 - Ostermundigen, 3000 Bern 65 urs.bf.mueller(a)sbb.ch / www.sbb.ch

10 19

IANA AS Numbers Registry Update
by Selina Harrington 21 Oct '20

21 Oct '20

Hi, The IANA AS Numbers registry has been updated to reflect the allocation of the following blocks to APNIC: 141626-142649 Assigned by APNIC 2020-10-20 142650-143673 Assigned by APNIC 2020-10-20 You can find the registry at: https://www.iana.org/assignments/as-numbers/ The allocation was made in accordance with the Policy for Allocation of ASN Blocks to Regional Internet Registries: https://www.icann.org/resources/pages/global-policy-asn-blocks-2010-09-21-en Best Regards, -- Selina Harrington Lead IANA Services Specialist

1 0

Bluewin Mail > Senior DevOps Engineer Unix/Linux
by Steven.Glogger＠swisscom.com 20 Oct '20

20 Oct '20

Hi All I have an open position @ Bluewin Mail. Details: https://jobs.swisscom.ch/professionals/offene-stellen/berufserfahrene/senio… greetings -steven

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

swinog