- swinog - vmaill01.sys

Invitation to DNSHeads Switzerland Meeting 16.5. 15:00
by Michael Hausding 14 Mar '19

14 Mar '19

Dear List SWITCH is hosting the 1st DNSHeads Meetup in Switzerland on May 16 from 15:00 on. If you run a resolver or an authoritative DNS Server you might want to join us in Zurich to discuss DNS-specific topics in an informal setup (yes, this could mean beer is involved.) More Information and registration is here: https://www.meetup.com/de-DE/DNSHeads-Switzerland/events/259123657/ Hope to see you in Zurich! Michael ------------------------------------ Michael Hausding, Competence Lead DNS & Domain Abuse SWITCH-CERT Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland phone +41 44 268 15 77, incident phone +41 44 268 15 40 michael.hausding(a)switch.ch http://securityblog.switch.ch

1 0

SBB.ch / IPv6 MTU / fragmentation problem
by Nico Schottelius 12 Mar '19

12 Mar '19

Good morning, is anyone from sbb.ch reading here? https://sbb.ch does not load on IPv6 for us. It seems that packets > 1420 bytes are dropped inside the SBB network, Local PMTU / fragmentation seems to work, my local outgoing MTU is 1420. MTR below. Best, Nico [10:23] line:~% mtr -w -c1 -s 1500 sbb.ch Start: 2019-03-12T10:24:17+0100 HOST: line Loss% Snt Last Avg Best Wrst StDev 1.|-- 2a0a:e5c1:111:111::42 0.0% 1 11.2 11.2 11.2 11.2 0.0 2.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 3.|-- 2a0a:e5c0:2:12::7 0.0% 1 69.8 69.8 69.8 69.8 0.0 4.|-- 2a0a:e5c0:1:1::9 0.0% 1 74.3 74.3 74.3 74.3 0.0 5.|-- 2001:1620:20e6::1 0.0% 1 69.4 69.4 69.4 69.4 0.0 6.|-- r1zrh2.core.init7.net 0.0% 1 69.1 69.1 69.1 69.1 0.0 7.|-- r1olt2.core.init7.net 0.0% 1 58.0 58.0 58.0 58.0 0.0 8.|-- r1brn1.core.init7.net 0.0% 1 62.8 62.8 62.8 62.8 0.0 9.|-- r2brn1.core.init7.net 0.0% 1 65.4 65.4 65.4 65.4 0.0 10.|-- r1epe1.core.init7.net 0.0% 1 75.2 75.2 75.2 75.2 0.0 11.|-- r1qls1.core.init7.net 0.0% 1 78.4 78.4 78.4 78.4 0.0 12.|-- r1gva3.core.init7.net 0.0% 1 81.0 81.0 81.0 81.0 0.0 13.|-- gw-sunrise.init7.net 0.0% 1 64.4 64.4 64.4 64.4 0.0 14.|-- 2001:1700:1:7:120::2 0.0% 1 84.4 84.4 84.4 84.4 0.0 15.|-- 2001:1700:4d00:2::2 0.0% 1 81.3 81.3 81.3 81.3 0.0 16.|-- 2a00:4bc0:ffff:ff00::1d 0.0% 1 67.0 67.0 67.0 67.0 0.0 17.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 [10:24] line:~% mtr -w -c1 -s 1400 sbb.ch Start: 2019-03-12T10:24:35+0100 HOST: line Loss% Snt Last Avg Best Wrst StDev 1.|-- 2a0a:e5c1:111:111::42 0.0% 1 3.2 3.2 3.2 3.2 0.0 2.|-- 2a0a:e5c1:100::1 0.0% 1 69.0 69.0 69.0 69.0 0.0 3.|-- 2a0a:e5c0:2:12::7 0.0% 1 74.7 74.7 74.7 74.7 0.0 4.|-- 2a0a:e5c0:1:1::9 0.0% 1 69.9 69.9 69.9 69.9 0.0 5.|-- 2001:1620:20e6::1 0.0% 1 60.5 60.5 60.5 60.5 0.0 6.|-- r1zrh2.core.init7.net 0.0% 1 75.3 75.3 75.3 75.3 0.0 7.|-- r1olt2.core.init7.net 0.0% 1 70.7 70.7 70.7 70.7 0.0 8.|-- r1brn1.core.init7.net 0.0% 1 69.1 69.1 69.1 69.1 0.0 9.|-- r2brn1.core.init7.net 0.0% 1 54.6 54.6 54.6 54.6 0.0 10.|-- r1epe1.core.init7.net 0.0% 1 75.9 75.9 75.9 75.9 0.0 11.|-- r1qls1.core.init7.net 0.0% 1 78.8 78.8 78.8 78.8 0.0 12.|-- r1gva3.core.init7.net 0.0% 1 79.8 79.8 79.8 79.8 0.0 13.|-- gw-sunrise.init7.net 0.0% 1 69.9 69.9 69.9 69.9 0.0 14.|-- 2001:1700:1:7:120::2 0.0% 1 77.5 77.5 77.5 77.5 0.0 15.|-- 2001:1700:4d00:2::2 0.0% 1 59.3 59.3 59.3 59.3 0.0 16.|-- 2a00:4bc0:ffff:ff00::1d 0.0% 1 70.1 70.1 70.1 70.1 0.0 17.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 18.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 19.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 20.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 21.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 22.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 23.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 24.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 25.|-- 2a00:4bc0:ffff:ffff::c296:f58e 0.0% 1 58.3 58.3 58.3 58.3 0.0 [10:24] line:~% [10:25] line:~% mtr -w -c1 -s 1420 sbb.ch Start: 2019-03-12T10:25:44+0100 HOST: line Loss% Snt Last Avg Best Wrst StDev 1.|-- 2a0a:e5c1:111:111::42 0.0% 1 16.3 16.3 16.3 16.3 0.0 2.|-- 2a0a:e5c1:100::1 0.0% 1 77.0 77.0 77.0 77.0 0.0 3.|-- 2a0a:e5c0:2:12::7 0.0% 1 67.0 67.0 67.0 67.0 0.0 4.|-- 2a0a:e5c0:1:1::9 0.0% 1 66.7 66.7 66.7 66.7 0.0 5.|-- 2001:1620:20e6::1 0.0% 1 78.8 78.8 78.8 78.8 0.0 6.|-- r1zrh2.core.init7.net 0.0% 1 64.5 64.5 64.5 64.5 0.0 7.|-- r1olt2.core.init7.net 0.0% 1 68.3 68.3 68.3 68.3 0.0 8.|-- r1brn1.core.init7.net 0.0% 1 74.9 74.9 74.9 74.9 0.0 9.|-- r2brn1.core.init7.net 0.0% 1 73.6 73.6 73.6 73.6 0.0 10.|-- r1epe1.core.init7.net 0.0% 1 62.2 62.2 62.2 62.2 0.0 11.|-- r1qls1.core.init7.net 0.0% 1 74.3 74.3 74.3 74.3 0.0 12.|-- r1gva3.core.init7.net 0.0% 1 63.6 63.6 63.6 63.6 0.0 13.|-- gw-sunrise.init7.net 0.0% 1 69.1 69.1 69.1 69.1 0.0 14.|-- 2001:1700:1:7:120::2 0.0% 1 77.4 77.4 77.4 77.4 0.0 15.|-- 2001:1700:4d00:2::2 0.0% 1 78.8 78.8 78.8 78.8 0.0 16.|-- 2a00:4bc0:ffff:ff00::1d 0.0% 1 75.7 75.7 75.7 75.7 0.0 17.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 18.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 19.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 20.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 21.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 22.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 23.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 24.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 25.|-- 2a00:4bc0:ffff:ffff::c296:f58e 0.0% 1 83.8 83.8 83.8 83.8 0.0 [10:25] line:~% mtr -w -c1 -s 1430 sbb.ch Start: 2019-03-12T10:25:55+0100 HOST: line Loss% Snt Last Avg Best Wrst StDev 1.|-- 2a0a:e5c1:111:111::42 0.0% 1 7.3 7.3 7.3 7.3 0.0 2.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 3.|-- 2a0a:e5c0:2:12::7 0.0% 1 60.4 60.4 60.4 60.4 0.0 4.|-- 2a0a:e5c0:1:1::9 0.0% 1 61.9 61.9 61.9 61.9 0.0 5.|-- 2001:1620:20e6::1 0.0% 1 72.2 72.2 72.2 72.2 0.0 6.|-- r1zrh2.core.init7.net 0.0% 1 65.2 65.2 65.2 65.2 0.0 7.|-- r1olt2.core.init7.net 0.0% 1 64.9 64.9 64.9 64.9 0.0 8.|-- r1brn1.core.init7.net 0.0% 1 64.9 64.9 64.9 64.9 0.0 9.|-- r2brn1.core.init7.net 0.0% 1 71.7 71.7 71.7 71.7 0.0 10.|-- r1epe1.core.init7.net 0.0% 1 64.4 64.4 64.4 64.4 0.0 11.|-- r1qls1.core.init7.net 0.0% 1 63.2 63.2 63.2 63.2 0.0 12.|-- r1gva3.core.init7.net 0.0% 1 77.9 77.9 77.9 77.9 0.0 13.|-- gw-sunrise.init7.net 0.0% 1 64.5 64.5 64.5 64.5 0.0 14.|-- 2001:1700:1:7:120::2 0.0% 1 63.5 63.5 63.5 63.5 0.0 15.|-- 2001:1700:4d00:2::2 0.0% 1 81.7 81.7 81.7 81.7 0.0 16.|-- 2a00:4bc0:ffff:ff00::1d 0.0% 1 74.4 74.4 74.4 74.4 0.0 17.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 [10:26] line:~% icmp6, frag works locally: 10:29:44.919328 IP6 2a0a:e5c1:111:111:3185:e802:6548:658c > 2a00:4bc0:ffff:ffff::c296:f58e: frag (0|1368) ICMP6, echo request, seq 33000, length 1368 10:29:44.919368 IP6 2a0a:e5c1:111:111:3185:e802:6548:658c > 2a00:4bc0:ffff:ffff::c296:f58e: frag (1368|92) -- Your Swiss, Open Source and IPv6 Virtual Machine. Now on www.datacenterlight.ch.

4 6

Security Chat 5.0 - March 25
by Raffael Marty 12 Mar '19

12 Mar '19

The Security Chat is Back! We are gathering for an evening of short security-related presentations and networking with peers in the industry. Security Chat 5.0 Monday, March 25th, 18.00 - 20.30 AdNovum Informatik AG (Headquarters), 22 Röntgenstrasse, 8005 Zürich (free) singup at: http://bit.ly/securitychat50 If you are interested in giving a short presentation, please indicate on the signup or email me directly. Any topics are welcome: Projects, research, questions you would like to get answers from the attendees, an embarrassing security story - the stage is yours. Keep the rest of your evening open if you can. Last time people stayed until 11pm; chatting and networking. Hope to see you at the event! -Raffy

1 0

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

Byebye SwissIX, hello Equinix Zurich Exchange
by Fredy Kuenzler 21 Dec '18

21 Dec '18

More than 10 years ago Init7 unplugged from the Exchange formerly known as TIX Telehouse Internet Exchange in Zurich. When we decided to do this, it was evident that SwissIX was offering much more value for money, in fact, SwissIX offered ports without recurring monthly fees. SwissIX was completely community driven and a lot of volunteer work made it happen. The fact of free ports made SwissIX big in the number of participants. (Disclaimer: I was president of the SwissIX association between 2004 and 2009). This has changed. The SwissIX association decided to charge for ports above 1 Gigabit a few years ago, in order to renew the infrastructure and to pay a salary for operations (to my knowledge SwissIX pays one part time employee). I respect that decision, while I was not supporting it. Consequently Init7 downgraded to 1 Gigabit then and did not accept new peers ever since. The price for a 10 Gigabit port apparently was lowered recently to CHF 750 per month. Which sums up to CHF 9000 per year. The 2nd port is cheaper: CHF 400 per month. Details can be found here: https://www.swissix.ch/participation I made a quick count of the ports and found ~100 ports with 10 Gigabit and two 100 Gigabit ports (according to PeeringDB). Assuming that 50% are secondary ports a quick estimate of the association revenue adds up to this sum: 50* CHF 750 = CHF 450000 50* CHF 400 = CHF 240000 2* CHF 2600 = CHF 62400 Total ≃ CHF 750000 per year, not including membership fees I suppose that this amount is sufficient to buy the complete equipment required to operate the SwissIX peering mesh twice a year (yes, gear gets cheaper these days; though it's an absurd example) and still includes the salary of the one part time employee. Since such a charging and revenue scheme is in force for several years I suppose SwissIX has accumulated a seven-digit fortune. However it seems that no one really knows about it, as the association of SwissIX didn't make financial reports accessible on the website (I assume they have been presented on the yearly General Meetings only, though it's not possible for all association members to be part of it). So the question remains for many of us: Where did the money go? SwissIX is hardly visible in the international community, so I guess "money was spent for Marketing" is not a valid answer. SwissIX port fees are today among the most expensive in Europe (not including any membership fees), and all of these Exchanges are way bigger in terms of traffic and marketing efforts: LINX 750£ + 424£ (1st, 2nd) AMS-IX 720€ DE-CIX - no price list published anymore, depends on your negotiation skills... Equinix Paris: €400 MIX Milano €750 which includes 1/3 cabinet and power SwissIX claims to be "Not for Profit". Equinix, in contrary, is listed on the stock market. Still, the first 10 Gigabit port on Equinix Zurich Exchange costs CHF 400 per month and includes a cross connect. That's about half of the cost of the Not-for-Profit SwissIX. More than 10 years ago, Init7 unplugged from the Exchange formerly known as TIX Telehouse Internet Exchange in Zurich. Now we are reverting this decision, as preconditions have reverted too. Init7 has cancelled it's membership of the SwissIX association to the end of 2018 and will unplug the remaining 1 Gigabit port anytime soon. We are happy to accept new peering sessions at Equinix Exchange Zurich as long as the requirements are met (no peering with customers or customers of customers). We are also happy to accept new PNI peers in any common location, if resources are available. Please send inquiries to peering at init7 dot net. Happy Peering and good luck, SwissIX. PS. some useful URLs: History of SwissIX: https://www.swissix.ch/about Where it all started - SwiNOG 1: https://www.swinog.ch/meetings/swinog1/ -- Fredy Kuenzler Init7 (Switzerland) Ltd. AS13030 Technoparkstrasse 5 CH-8406 Winterthur http://www.init7.net/

2 1

SwiNOG #34 – first videos published
by Steven Glogger 16 Dec '18

16 Dec '18

Hi everybody, As announced at SwiNOG #34 we we're recording the presentations and I'm glad to announce that first two Videos are published. Link to the presentation & video: http://www.swinog.ch/meetings/swinog34/ Youtube-Playlist for SwiNOG #34 https://www.youtube.com/playlist?list=PLMP2Spqss4Ipu2bEWyqnHPDziyK74uoi0 SwiNOG Channel: https://www.youtube.com/channel/UCNc3EckU23H4rXn_SdgpTUw We release more videos in the next weeks. Please note that we're not announcing every video on the mailinglist. Simply use the playlist, subscribe to the youtube channel or follow us on twitter. greetings -steven SwiNOG Core Member

2 2

How do website operators get the mobile phone number of visitors?
by Benoit Panizzon 07 Dec '18

07 Dec '18

Hi List I have read: https://nakedsecurity.sophos.com/2012/01/25/smartphone-website-telephone-nu… And I have sniffed the traffic between my swisscom mobile Samsung Mobile and my Website, but can't find any of the additional headers disclosing my phone number. Is there a trick to make a mobile phone disclose it's phone number while connected via the mobile network's operator network? How can 'website payment' operator like 'obligo' get the phone number associated with a visitor? Obligo states they got the phone number to bill 'from the service operator'. Would it be possible, that a fraudster injects such headers from a client to make obligo bill the wrong number? PS: I know obligo's reputation. 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

Re: [swinog] swinog Digest, Vol 167, Issue 1
by Martin Fischer 07 Dec '18

07 Dec '18

....with a code that is sent by an SMS to confirm identity before transaction becomes confirmed.. Fründlechi Grüess Martin > Am 07.12.2018 um 12:00 schrieb swinog-request(a)lists.swinog.ch: > > Send swinog mailing list submissions to > swinog(a)lists.swinog.ch > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog > or, via email, send a message with subject or body 'help' to > swinog-request(a)lists.swinog.ch > > You can reach the person managing the list at > swinog-owner(a)lists.swinog.ch > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of swinog digest..." > > > Today's Topics: > > 1. How do website operators get the mobile phone number of > visitors? (Benoit Panizzon) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 6 Dec 2018 14:54:04 +0100 > From: Benoit Panizzon <benoit.panizzon(a)imp.ch> > To: swinog(a)swinog.ch > Subject: [swinog] How do website operators get the mobile phone number > of visitors? > Message-ID: <20181206145404.74dcac40(a)go.imp.ch> > Content-Type: text/plain; charset=UTF-8 > > Hi List > > I have read: > > https://nakedsecurity.sophos.com/2012/01/25/smartphone-website-telephone-nu… > > And I have sniffed the traffic between my swisscom mobile Samsung > Mobile and my Website, but can't find any of the additional headers > disclosing my phone number. > > Is there a trick to make a mobile phone disclose it's phone number > while connected via the mobile network's operator network? > > How can 'website payment' operator like 'obligo' get the phone number > associated with a visitor? Obligo states they got the phone number > to bill 'from the service operator'. > > Would it be possible, that a fraudster injects such headers from a > client to make obligo bill the wrong number? > > PS: I know obligo's reputation. > > 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 > ______________________________________________________ > > > > ------------------------------ > > _______________________________________________ > swinog mailing list > swinog(a)lists.swinog.ch > http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog > > > End of swinog Digest, Vol 167, Issue 1 > **************************************

1 0

CANCELLED: SwiNOG-BE169
by Viktor Steinmann 26 Nov '18

26 Nov '18

Dear SwiNOGers, Due to scheduling conflicts, I'll have to cancel the announced Beer Event on Monday, 3rd December 2018. It seems, the Beer Events have come to an end. If someone would like to take the lead for 2019, please let me and/or Steven know off-list. Kind regards, Viktor (aka Stony)

1 0

Do ISP still offer outgoing smtp relaying services to business customers with own smtp server?
by Benoit Panizzon 16 Nov '18

16 Nov '18

Dear List We sometimes get requests from business customers, with own mailserver, which directly receives email via smtp, for an outgoing smtp-relay. I then argue with: * Their server is absolutely capable of sending emails directly * They have better control of the sending process. * They can look for problem them self in their logs. * Anti-Spam thresholds aimed at end users, not companies. * They are not affected if another customer is spaming and therefore the IP of the relay blacklisted. But still, I then often get an "BUT... you are our ISP, isn't it your duty to offer such a relay service? Other ISP do this!" rly? Do other ISP still offer smtp relaying services to business customers with own email infrastructure? 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 3

Inbound DNS query filtering on "broadband" IPs?
by Claudio Luck 13 Nov '18

13 Nov '18

Hi all I'm currently experimenting to host DNS zones on dynamic IP addresses and dynamic DNS. But I'm encountering more difficulties than expected on "broadband connections" in receiving UDP port 53 DNS query packets. In one case they're filtered completely (TCP port 53 works, UDP port 53 is blacked out), while on some there seems to be some adaptive filtering requiring like 10 minutes to "open up". Does this ring a bell? I would be thankful about any hint what could be interfering, PM or here. Thanks! Best Claudio Luck

2 1

Invalid ROA on Sunrise managed IP range
by Mike Kellenberger 12 Nov '18

12 Nov '18

Hi Could someone from Sunrise contact me off-list? We received a message about an invalid ROA of one of our customers IP-ranges, which is managed by Sunrise. I've tried contacting ip-reg(a)sunrise.net multiple times already, but I'm not getting any response. Regards, Mike -- Mike Kellenberger Teamleader Network & Security nexellent ag Sägereistrasse 33 CH-8152 Glattbrugg Phone: + 41 44 872 20 00 Direct: + 41 44 872 20 30 Mobile: + 41 79 421 17 78 www.nexellent.ch twitter.com/nexellent

1 0

.CH/.LI DNSSEC Algorithm Rollover
by Daniel Stirnimann 12 Nov '18

12 Nov '18

Hello, for your information, SWITCH will perform a DNSSEC algorithm rollover from RSA to ECDSA for ch. and li. ECDSA uses smaller keys and signatures than their RSA counterparts, which means responses to DNS queries are smaller. ECDSA was already standardised for use in DNSSEC in 2012. While switch.ch has been signed with ECDSA since 2016, IANA the root zone operator has only recently allowed TLDs to use it. The changes to the ch. and li. zones DNSKEY record are as following with times reported in UTC: 2018-11-21T13:30 Add new ECDSA key to DNSKEY record set 2018-12-21T13:30 Remove old RSA key from DNSKEY record set Between this interval, the chain of trust for ch. and li. will be updated in the root zone to point to the new ECDSA key only. Operators of DNSSEC validating DNS resolvers do not need to do anything. In the unlikely case that your validating DNS resolver only understands RSA but not ECDSA, then it will answer to ch. or li. queries as if they were not DNSSEC signed. You can test which DNSSEC algorithms are supported by the DNS resolver(s) configured on your system by visiting: https://rootcanary.org/test.html Best regards, Daniel Stirnimann, SWITCH -- SWITCH Daniel Stirnimann, SWITCH-CERT Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland phone +41 44 268 15 15, direct +41 44 268 16 24 daniel.stirnimann(a)switch.ch, www.switch.ch

1 0

Mail MX Databaar
by walter＠onda.ch 05 Nov '18

05 Nov '18

Hello Could somebody from Bluewin connect to me offlist? We have some trouble sending mails. Regards Walter

1 0

*** Save the Date - SwiNOG#35 08.05.2019 ***
by Simon Ryf 04 Nov '18

04 Nov '18

Dear SwiNOG’ers Save the Date ! Put it in your Calendar - NOW :) Wednesday May 5th 2019 is SwiNOG #35 Have nice week SwiNOG Team

3 5

Google DNS on Salt Mobile
by Gregor Riepl 01 Nov '18

01 Nov '18

Hi, It seems like Salt is no longer supplying their own DNS servers when establishing an LTE connection. Instead, the network responds with Google DNS servers (8.8.8.8 8.8.4.4). Is there a particular reason for that? I'd rather not send all my DNS requests to Google. Perhaps it's time to switch to private resolvers everywhere, if not even ISPs are providing that service any more... Thanks for any info. Greg

6 12

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

swinog