swinog

swinog@lists.swinog.ch

3 participants
2927 discussions

ALLOCATED UNSPECIFIED ranges [RIPE/alloc-unspecified]
by Paolo Moroni 08 Feb '18

08 Feb '18

Good afternoon from AS3303 (Swisscom/IP-Plus). This e-mail is intended as help information for those of you who operate IPv4 PI addresses within the following ranges: 193.5.0.0/16 193.134.0.0/15 193.246.0.0/15 for historical reasons, these ranges used to have a status of ALLOCATED UNSPECIFIED in the RIPE data base and were managed by the ch.unisource LIR (ourselves). In 2016 the RIPE-NCC has received a mandate from the RIPE Address Policy working group to transfer these addresses into standard ALLOCATED PA and ALLOCATED PI addresses, managed by the RIPE-NCC; if interested in the details, please see https://www.ripe.net/ripe/mail/archives/address-policy-wg/2016-October/0118… The transfer of these three ranges has been completed recently. This includes the management responsibility of the related PI assignments, although, for practical reasons, the Swisscom maintainer CH-UNISOURCE-MNT has not been removed from some objects yet. Please find enclosed below the guidelines we received from the RIPE-NCC with respect to the administration of the related RIPE data base objects. Thanks for your attention and understanding, Paolo Moroni IP-Plus Engineering ch.unisource ----------------------------------------------------------------------- Following the re-organisation of ALLOCATED UNSPECIFIED addresses blocks formerly managed by CH-UNISOURCE-MNT, the management of the PI assignments has been transferred to the RIPE-NCC. Each PI assignment will need to have a "Sponsoring LIR" (a RIPE NCC member responsible for maintenance, accuracy and communication with regards to a specific assignment). Please see http://www.ripe.net/ripe/docs/ripe-637#20 for details. Please contact your Sponsoring LIR if you have one. If not, please contact RIPE NCC, <ncc(a)ripe.net>

1 0

IPv6 Run Event
by Nico Schottelius 04 Feb '18

04 Feb '18

Good morning Swinog, we are planning our first IPv6 focused event this year. The main topic of the event is, how well the IPv6 deployment of Switzerland has come and to discuss the action points to reach 100% IPv6 coverage. Thus I would like to invite you to join and... ... showcase how and where you enabled sites with IPv6 ... show difficulties and solutions for IPv6 only networks ... meet players from industry to discuss your needs with others ... get a tasty Adler Bräu beer We are at an early planning stage, but wanted to begin to spread the word already (i.e. date to be defined, Website & CfP coming in the next weeks). The format will likely be a 1-2 day event, with talks during the day, discussion in the late afternoon and a networking event in the evening. To decide on the exact format, I would like to ask you to give me a heads up, if you are interested in this event and if you are interested in showcasing something. A simple "+1" or "+1 +talk_about_x" suffices. Depending on the feedback, we will plan for either a 1 or 2 day event. Thanks a lot and have a great snowy Sunday, Nico -- Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch

1 0

datacomm/vtxnet and quicknet/kfsb are missing TLS on their mailservers
by Peter Keel 02 Feb '18

02 Feb '18

Hi I get these errors: | TLS is required, but was not offered by host mx1.datacomm.ch[212.40.2.32] and | TLS is required, but was not offered by host relay.kfsb.ch[213.202.32.8] Since I've made TLS for SMTP mandatory. The respective admins of these servers might want finally at least enable voluntary TLS; some of their customers apparently would like to receive mails from my server. And by the way, RFC 2487 that is referred to for instance in the postfix manpage and stated that one must not make TLS mandatory has been obsoleted by RFC 3207. Cheers Seegras -- "Those who give up essential liberties for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin "It's also true that those who would give up privacy for security are likely to end up with neither." -- Bruce Schneier

7 6

SwiNOG#33 - Save the Date 24.05.2018
by Simon Ryf 24 Jan '18

24 Jan '18

Dear SwiNOG’ers This is a reminder that we already accepting CfP’s and that SwiNOG#33 will be held Thursday May 24th 2018 If you have any questions regarding SwiNOG or a possible Topic, please write to swinog-core(a)swinog.ch or to me directly. Topics for Presentations/Talks --------------------------------------------------- The number and length of presentations per session is not fixed, although due to time constraints we would prefer the length of the presentations to be between 5 to 45 minutes. Here is a non-exhaustive list of typical SwiNOG meeting topics: - Security - DDOS Mitigation - AntiSpam - IPv6 - Open Source tools - International view of the internet (incidents, outages, measurements) - Routing - Server applications (DNS, Web, etc.) - Legal issues (B‹PF, etc.) - Telecommunication politics (Net Neutrality, Incumbent monopoly, etc.) -> PLEASE feel free to talk to us about any kind of topic and collaboration!!! You can always start a discussion on the list - I'm sure people join in. Language of Slides and Talks --------------------------------------------------- The whole day will be held 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 solely promotional for your employer. Please remember that your 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, we request that you provide the following information to <swinog-core at swinog.ch>: * the name of the presenter (and if applicable your affiliation) * a working email address * the name and number of the topic which will contain the presentation * the title of the presentation * its expected length (in minutes) * a short abstract of the presentation (so we know what it is about) We also welcome suggestions for specific presentations which you feel would be valuable to the SwiNOG community. Please be aware that your presentation will be published on the SwiNOG website after the event. We can publish modified slides if requested - it might be that some confidential data will be presented by you which are not intended for publication on the internet. Greetings, Simon Ryf SwiNOG Core Team 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/, Facebook, Xing, Information about the meeting will be published at http://www.swinog.ch/meetings/swinog31/ 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 0

CIXP / GVA - Infomaniak
by DUCHET Rémy 24 Jan '18

24 Jan '18

Hello all, We have seen multiple problem for reach AS29222, via CIXP. Is this problem already known ? Is it affecting other AS ? Thanks. Rémy DUCHET

3 4

PC Engines APU training material
by Stanislav Sinyagin 23 Jan '18

23 Jan '18

hi, I was giving a training to some taxpayer-sponsored organization, and it's natural to give whatever is useful back to the public. Here is the slideshow about PC Engines hardware and applications: https://github.com/ssinyagin/pcengines-apu-debian-cd/tree/master/misc enjoy

1 0

Bluewin Error: Der MX-Eintrag fuer die Domaene aerni.com kann nicht verifiziert werden
by Benoit Panizzon 12 Jan '18

12 Jan '18

Hello List Does anyone know, how bluewin does 'verify' an MX? The MX of our customer is prefectly reachable for sender verification but his emails sent 'to' bluewin recipients are getting blocked with: MAIL FROM: <[scrubbed](a)aerni.com> Unable to verify MX-Record for domain aerni.com aerni.com mail is handled by 10 mail.aerni.com. mail.aerni.com has address 87.102.181.130 Connected to mail.aerni.com. Escape character is '^]'. 220 mail.aerni.com ESMTP ready. quit 221 mail.aerni.com closing connection Connection closed by foreign host. benoit@krup:~$ telnet mail.aerni.com. smtp Trying 87.102.181.130... Connected to mail.aerni.com. Escape character is '^]'. 220 mail.aerni.com ESMTP ready. ehlo imp.ch 250-mail.aerni.com Hello dhcp-186.imp.ch [157.161.4.186] 250-SIZE 52428800 250-8BITMIME 250-PIPELINING 250-AUTH PLAIN LOGIN 250-STARTTLS 250 HELP mail from:<> 250 OK rcpt to:<[scrubbed](a)aerni.com> 250 Accepted rset 250 Reset OK 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 ______________________________________________________

3 4

Re: [swinog] Bluewin Error: Der MX-Eintrag fuer die Domaene aerni.com kann nicht verifiziert werden
by Daniel Rechsteiner 12 Jan '18

12 Jan '18

Hi Benoit, Maybe Bluewin requires a matching PTR? Currently 87.102.181.130 resolves to cable-static-181-130.breitband.ch <http://cable-static-181-130.breitband.ch/> and not to mail.aerni.com <http://mail.aerni.com/>. Daniel > Does anyone know, how bluewin does 'verify' an MX? > > The MX of our customer is prefectly reachable for sender verification > but his emails sent 'to' bluewin recipients are getting blocked with: > > MAIL FROM: <[scrubbed](a)aerni.com> Unable to verify MX-Record for > domain aerni.com > > aerni.com mail is handled by 10 mail.aerni.com. > > mail.aerni.com has address 87.102.181.130

1 0

Mobile Provider of 185.183.104.170
by Tobias Brunner 12 Dec '17

12 Dec '17

Hi all, I'm interested to which mobile provider the IP 185.183.104.170 belongs. WHOIS shows: inetnum: 185.183.104.0 - 185.183.104.255 netname: M247-LTD-Zurich descr: M247 LTD Zurich Infrastructure country: CH geoloc: 47.3667 8.5500 [...] Does anyone have an idea which mobile provides has his network managed by M247? Cheers, Tobias

1 0

Beer in Zurich on Monday 11/12 ?
by Massimiliano Stucchi 06 Dec '17

06 Dec '17

Hi all! It's been a while since the last Beer Event (and not that I participated in many of them, though), so I think it's time to do something. I will be at Kennedy's (http://www.kennedys.ch/) near Europaallee starting from 19:15 on Monday, 11/12. If you feel like joining, please do, and please let me know so I can get an appropriately sized table. Ciao! -- Massimiliano Stucchi MS16801-RIPE

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