swinog

swinog@lists.swinog.ch

1 participants
2942 discussions

Security Chat 5.0 - March 25 - Save the Date
by Raffael Marty 09 Mar '19

09 Mar '19

SAVE THE DATE! The Security Chat 5.0 will be taking place in Zurich on Monday the 25th of March at 6pm. This is a free event open to anyone who has an interest in security. We will listen to a few short (10-15 minute) presentations and then have a chance to network with each other. Last time we had a fabulous turn out of security practitioners, startup founders, geeks, cyber experts, and people who like to mingle until 11pm, making new friends in the security community. The exact location and signup information will follow soon. For now, mark your calendar and spread the word! You will have a chance to sign up to give a presentation when the official invite goes out. Hope to see you all in a couple of weeks! -Raffy

1 0

routing to bluewin.ch
by Martin Schenkel 05 Mar '19

05 Mar '19

Hi Has anybody else seen this weird announcement to the bluewin.ch /24 through AS60633? Network Path *> 213.3.75.0/24 1836 59622 64521 60633 i * 213.3.75.0/24 1836 59622 64521 60633 i Cheers, Martin

2 1

UPC-Contact off-list
by Swiss Network Operators Group (SwiNOG) 28 Feb '19

28 Feb '19

Hi list Can somebody from UPC contact me off-list regarding some suspicious DNS queries (from an UPC-IP) to our authoritative NS? Thanks in advance. Kind regards, Thomas Amgarten arcade solutions ag +41 41 417 31 73

1 1

##### SwiNOG #35 - Call for Papers (2019-May-08) #####
by Simon Ryf 12 Feb '19

12 Feb '19

Dear SwiNOG supporter, this is the official Call for Paper email. Please submit your proposal via https://www.swinog.ch/cfp/ The 35th meeting of the Swiss Network Operators Group (SwiNOG) will be held in Berne on top of the Gurten on Thursday May 8th 2019. Important Dates for https://www.swinog.ch/meetings/swinog35/: 12.02.2019 Call for Papers tbd Registration opens 28.04.2019 Final publication of agenda 03.05.2019 Registration closes 06.05.2019 Deadline for all slides 08.05.2019 Meeting day 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, * IPv6 * Open Source tools and interesting Github projects * 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 to 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. 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

JunOS Filter Question
by Viktor Steinmann 01 Feb '19

01 Feb '19

Dear SwiNOGers I'm new to JunOS. I like this OS so far, but I'm having a hard time, securing this stuff... Something's wrong in my JunOS filters... Basically I want to block everyone from accessing the interface on the router itself, but I want to allow traffic to pass the interface. Somehow that doesn't work. See below the (relevant) configuration parts: interfaces { xe-0/1/2 { description blabla; vlan-tagging; } unit 100 { description Blabla; vlan-id 100; family inet { filter { input INTERFACE-INCOMING; } address 192.168.1.1/24 } } } policy-options { prefix-list MYINTERFACE { 192.168.1.1/32; } } firewall { family inet { filter INTERFACE-INCOMING { term WAN-ADDRESS { from { destination-prefix-list { MYINTERFACE; } } then { discard; } } term ALLOW-ALL { then accept; } } } } Anybody with a hint, why this filter doesn't actually block traffic to 192.168.1.1? I can still ping it. Kind regards, Viktor

2 2

Weird Bluewin Server Problem (occasional 550 5.1.1)
by Benoit Panizzon 24 Jan '19

24 Jan '19

Dear List Has anyone else experienced this problem? According to our customer, it occurred a couple of times in the last days: Sender and Destinations are the same in all examples: Our customer is sending an email to bluewin: Jan 23 13:32:42 obelix postfix-submit.obelix/smtp[28721 C5015C0CE5: to=<****(a)bluewin.ch>, relay=mxbw.lb.bluewin.ch[195.186.120.50]:25, delay=57, delays=1.6/0.01/44/11, dsn=2.0.0, status=sent (250 2.0.0 mHh5gTobfzOqbmHhngLDSm mail accepted for delivery) Bluewin Customer replies: Jan 23 17:10:17 obelix milter-greylist: (unknown id): skipping greylist because address 195.186.120.132 is in DNSRBL, (from=<****(a)bluewin.ch>, rcpt=<****(a)breitband.ch>, addr=vimdzmsp-sfwd03.bluewin.ch[195.186.120.132]) ACL 196 Our customer replies: Jan 23 17:24:38 obelix postfix-submit.obelix/smtp[12583 D0AE7C10EE: to=<****(a)bluewin.ch>, relay=mxbw.lb.bluewin.ch[195.186.120.50]:25, delay=101, delays=0.27/0.01/66/35, dsn=5.1.1, status=bounced (host mxbw.lb.bluewin.ch[195.186.120.50] said: 550 5.1.1 <*****(a)bluewin.ch> recipient rejected, address unknown (in reply to RCPT TO command)) Same IP Address of same bluewin server as before, not replies the destination does not exist. I can assure you, it is the same address as before. Our customer tries again: Jan 23 17:32:23 obelix postfix-submit.obelix/smtp[26676 C9470C1271: to=<*****(a)bluewin.ch>, relay=mxbw.lb.bluewin.ch[195.186.227.50]:25, delay=3, delays=0.24/0.02/0.59/2.1, dsn=2.0.0, status=sent (250 2.0.0 mJApg3d9Gp4S3mJAqgsUex mail accepted for delivery) Now the email is getting through! 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 2

Beginning of the year beers
by Massimiliano Stucchi 22 Jan '19

22 Jan '19

Hi everyone! Since there is no one organising any more beer events, I think the beginning of the year could be a good opportunity to try to meet. I suggest to meet Thursday, 24th of January at Kennedy's, near Zurich HB, around 18. I created an event on eventbrite: https://www.eventbrite.it/e/swiss-netops-new-year-beer-registration-5492147… so I can keep track of who's supposed to come. I will proceed with booking the venue at the beginning of next week, when I expect to have a rough idea of the number of participants. I hope to see many of you there! Ciao! -- Massimiliano Stucchi MS16801-RIPE

1 1

New BÜPF / VÜPF: Technical, Organisational and Administrative Requirements, March 1, 2019
by Fredy Kuenzler 21 Jan '19

21 Jan '19

Did anyone notice and read the new BÜPF / VÜPF Technical, Organisational and Administrative Requirements, valid from March 1, 2019? To my understanding FDAs with reduced requirements don't have to do anything. Press release in DE/FR/IT DE https://www.admin.ch/gov/de/start/dokumentation/medienmitteilungen.msg-id-7… FR https://www.admin.ch/gov/fr/accueil/documentation/communiques.msg-id-73716.… IT https://www.admin.ch/gov/it/pagina-iniziale/documentazione/comunicati-stamp… -- Fredy Kuenzler Init7 (Switzerland) Ltd. AS13030 Technoparkstrasse 5 CH-8406 Winterthur Twitter: @init7 / @kuenzler http://www.init7.net/

4 3

mail.protection.outlook.com - dns issues?
by Tobias Goeller 11 Jan '19

11 Jan '19

Hi All, Anyone else having problems with customers using mail.protection.outlook.com or spf.protection.outlook.com in their SPF Records? Just asking (both records seem to be not resolvable at the moment...) Tobias -- E = M * C^2 +/- 3.2db

2 1

Fwd: BGP Experiment
by Steven Glogger 23 Dec '18

23 Dec '18

fyi > Von: Arnold Nipper <arnold(a)nipper.de> > Datum: 23. Dezember 2018 um 08:16:51 MEZ > An: DENOG <denog(a)lists.denog.de> > Betreff: Wtr:⁨ BGP Experiment⁩ > > Erholsame Feiertage und viele Grüße > Arnold > > > -------- Weitergeleitete Nachricht -------- > Betreff: BGP Experiment > Datum: Tue, 18 Dec 2018 10:05:26 -0500 > Von: Italo Cunha <cunha(a)dcc.ufmg.br> > An: NANOG <nanog(a)nanog.org>, DISCO experiment mailing list > <disco-experiment(a)googlegroups.com> > > NANOG, > > We would like to inform you of an experiment to evaluate alternatives > for speeding up adoption of BGP route origin validation (research > paper with details [A]). > > Our plan is to announce prefix 184.164.224.0/24 with a valid > standards-compliant unassigned BGP attribute from routers operated by > the PEERING testbed [B, C]. The attribute will have flags 0xe0 > (optional transitive [rfc4271, S4.3]), type 0xff (reserved for > development), and size 0x20 (256bits). > > Our collaborators recently ran an equivalent experiment with no > complaints or known issues [A], and so we do not anticipate any > arising. Back in 2010, an experiment using unassigned attributes by > RIPE and Duke University caused disruption in Internet routing due to > a bug in Cisco routers [D, CVE-2010-3035]. Since then, this and other > similar bugs have been patched [e.g., CVE-2013-6051], and new BGP > attributes have been assigned (BGPsec-path) and adopted (large > communities). We have successfully tested propagation of the > announcements on Cisco IOS-based routers running versions 12.2(33)SRA > and 15.3(1)S, Quagga 0.99.23.1 and 1.1.1, as well as BIRD 1.4.5 and > 1.6.3. > > We plan to announce 184.164.224.0/24 from 8 PEERING locations for a > predefined period of 15 minutes starting 14:30 GMT, from Monday to > Thursday, between the 7th and 22nd of January, 2019 (full schedule and > locations [E]). We will stop the experiment immediately in case any > issues arise. > > Although we do not expect the experiment to cause disruption, we > welcome feedback on its safety and especially on how to make it safer. > We can be reached at disco-experiment(a)googlegroups.com. > > Amir Herzberg, University of Connecticut > Ethan Katz-Bassett, Columbia University > Haya Shulman, Fraunhofer SIT > Ítalo Cunha, Universidade Federal de Minas Gerais > Michael Schapira, Hebrew University of Jerusalem > Tomas Hlavacek, Fraunhofer SIT > Yossi Gilad, MIT > > [A] https://conferences.sigcomm.org/hotnets/2018/program.html > [B] http://peering.usc.edu > [C] https://goo.gl/AFR1Cn > [D] > https://labs.ripe.net/Members/erik/ripe-ncc-and-duke-university-bgp-experim… > [E] https://goo.gl/nJhmx1 > > -- > Arnold Nipper > email: arnold(a)nipper.de > mobile: +49 172 2650958 >

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