swinog

swinog@lists.swinog.ch

1 participants
2916 discussions

SwiNOG-BE158 - Beer Event 158 @ Don Weber Zurich, Monday, 2016-08-29
by Emanuel Kleindienst 26 Aug '16

26 Aug '16

Dear SwiNOGers, Let's have some Beer & Food at Don Weber! *** And an IMPORTANT announcement: JOINED Beering SwiNOG & SwissIX on Monday, 26.9.2016!!! Details will come up beginning of September. SAVE THE DATE!!! *** Upcoming events for rest of 2016: > SwiNOG-BE159: Mo, 26.9.16 - joined SwiNOG & SwissIX beering > SwiNOG-BE160: Mo, 24.10.16 > SwiNOG-BE161: Mo, 28.11.16 > SwiNOG-BE162: Mo, 12.12.16 (Christmas dinner) Looking forward seeing you! Emanuel, Mobile +41 79 382 73 77, Email emanuel(a)vshn.ch Details for the next event: ----------------------------------------------- Event: SwiNOG-BE158 - Beer Event 158 When? Monday, 29th August 2016 18:30 Where? Don Weber Heinrichstrasse 213, 8005 Zürich http://www.donweber.ch/ (GoogleMaps Link: http://goo.gl/maps/PqOPb) Places available? 8 !! Please sign up if you're really coming - because the seats are limited! !! ----------------------------------------------- Registration: Start: Friday, 26th August 2016 - 12:00 Stop: Monday, 29th August 2016 - 17:00 Reg-URL: http://swinog.be/ ----------------------------------------------- Since we have to make reservations, I need to know who's coming and who's not. If you can't attend and you're registered please inform me ASAP (+41 79 382 73 77). Cheers, Emanuel Kleindienst

1 0

RFC 1918 usage in Internet routes - was: Re: Swinog Post RFC1918 IP's on BBCS and Cable based Services
by Stephan Wolf 23 Aug '16

23 Aug '16

Hello Sunrise, many thanks for your (anonymous) feedback. <Offtopic> Ok, I have not seen this other discussion - and simply I do NOT want to start this "relegious" discussion about it. For me personally it is "bad behaviour" to use RFC1918 in internet public based services / routes. For sure others CAN do, because it is not strictly forbidden. This is for me also a general "problem" according RFC's: what is "MUST" and what is "SHOULD".... So I stop it here. </Offtopic> Back to my case: Here see the traces which use RFC1918 in your backbone. So you assign it ! Or may send me an introduction why I am wrong. May I missed something. Many thanks in advance, Best Regards Stephan remark: 192.168.12.254 is your CPE / Fritzbox /root: traceroute local.ch traceroute to local.ch (185.101.119.163), 64 hops max, 40 byte packets 1 192.168.12.254 (192.168.12.254) 0.826 ms 0.650 ms 0.559 ms 2 10.136.71.241 (10.136.71.241) 18.020 ms 18.421 ms 18.051 ms 3 172.16.19.146 (172.16.19.146) 22.824 ms 22.594 ms 20.392 ms 4 172.16.19.145 (172.16.19.145) 20.397 ms 23.046 ms 22.561 ms 5 194.230.108.185 (194.230.108.185) 18.058 ms 19.911 ms 19.526 ms 6 * * * 7 * * * 8 oer02pe05.ge1-0-19.bb.sunrise.net (212.161.250.138) 20.847 ms oer02pe05.ge1-0-0.bb.sunrise.net (212.161.250.134) 22.801 ms 22.368 ms 9 195.141.229.234 (195.141.229.234) 22.636 ms 22.517 ms 22.724 ms 10 * * * 11 * * * (snip) /root: traceroute -I local.ch traceroute to local.ch (185.101.119.163), 64 hops max, 48 byte packets 1 192.168.12.254 (192.168.12.254) 0.682 ms 0.543 ms 0.506 ms 2 10.136.71.241 (10.136.71.241) 18.382 ms 20.533 ms 17.602 ms 3 172.16.19.146 (172.16.19.146) 22.372 ms 22.011 ms 22.478 ms 4 172.16.19.145 (172.16.19.145) 21.672 ms 21.664 ms 22.113 ms 5 194.230.108.185 (194.230.108.185) 19.564 ms 19.532 ms 19.533 ms 6 * * * 7 * * * 8 oer02pe05.ge1-0-19.bb.sunrise.net (212.161.250.138) 22.131 ms 22.230 ms 21.965 ms 9 195.141.229.234 (195.141.229.234) 21.793 ms 22.007 ms 21.611 ms 10 * * * 11 * * * (snip) >tracert local.ch Routenverfolgung zu local.ch [185.101.119.163] über maximal 30 Hops: 1 <1 ms <1 ms 1 ms 192.168.12.254 2 18 ms 17 ms 18 ms 10.136.71.241 3 23 ms 22 ms 22 ms 172.16.19.146 4 23 ms 23 ms 22 ms 172.16.19.145 5 24 ms 20 ms 20 ms 194.230.108.185 6 * * * Zeitüberschreitung der Anforderung. 7 * * * Zeitüberschreitung der Anforderung. 8 87 ms 85 ms 83 ms oer02pe05.ge1-0-19.bb.sunrise.net [212.161.250.138] 9 87 ms 86 ms 79 ms 195.141.229.234 10 * * * Zeitüberschreitung der Anforderung. 11 * * * Zeitüberschreitung der Anforderung. (snip) Inbound: (snip) .... 6 e1-19.c-r1.es34.nine.ch (5.148.160.143) 12.509 ms 11.148 ms 11.102 ms 7 194.230.36.32 (194.230.36.32) 1.271 ms 1.261 ms 1.214 ms 8 * * * 9 zur01are02.et-10-3-0.bb.sunrise.net (195.141.217.155) 1.355 ms 1.225 ms 1.088 ms 10 * * * 11 * * * 12 * * * 13 adsl-84-227-50-245.adslplus.ch (84.227.50.245) 22.971 ms 23.458 ms 23.962 ms 2016-08-16 13:44 GMT+02:00 peering <peering(a)sunrise.net>: > Hi > Based on the current post at the swinog mailing list and a previous one > which discussed the topic in detail. In fact there is no obligation to not > use private IP Addresses for internet based Services. > Therefore be aware, that the seen RFC1918 Addresses has not been assigned > by sunrise. > Many Thanks for your understanding > > > > > >

1 1

Question about SwiNOG #30
by Alisha Manuela Stutz 17 Aug '16

17 Aug '16

Hi to all, Is there any plan when SwiNOG #30 will coming up? Best regards Alisha Manuela -- Eine sehr informative Broschüre über Transsexualität die Einblicke gibt um Vorurteile abzubauen oder gar nicht entstehen lässt. http://www.stadt-zuerich.ch/content/dam/stzh/prd/Deutsch/Gleichstellung/PDF…

2 1

SwiNOG-30 - SAVE THE DATE: 4.11.2016
by Steven Glogger 17 Aug '16

17 Aug '16

Dear SwiNOG supporter, We have great news, since our talks for the location and the sponsors are progressing. SAVE THE DATE: 4.11.2016 The 30th meeting of the Swiss Network Operators Group (SwiNOG) will be held in Berne on top of the Gurten on November 4th 2016. Important Dates for SwiNOG#28 --------------------------------------------------- 17.08.2016 Announcement of Meeting 24.08.2016 Call for Papers (you may submit already if you wish to do so) 05.09.2016 Registration opens 16.10.2016 Call for Papers closing 23.10.2016 Final publication of agenda 27.10.2016 Registration closes 01.11.2016 Deadline for all slides 04.11.2016 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 - 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 <http://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, Steven 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/ <http://www.swinog.ch/>, Facebook, Xing, Information about the meeting will be published at http://www.swinog.ch/meetings/swinog29/ <http://www.swinog.ch/meetings/swinog29/> 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

Bad Connectivity at UPC Home Internet
by Tobias Brunner 17 Aug '16

17 Aug '16

Hi all, I'm having a hard time with my UPC Internet at home. Connections to f.e. Github are nearly impossible since a few weeks (can't remember exactly since when =( ), but when connecting through a VPN (exits at AS57118) there are no performance issues other connection problems. This connection troubles are not only to Github, but also to other random destinations like Ifolor, sometimes Google, sometimes SRF, ... I couldn't find patterns at the moment, SmokePing started collecting them for me =) (currently it shows huge paketloss, but still have to wait some more days for better graphs). Is anyone else having such issues with UPC home Internet? Cheers, Tobias

7 9

Recent Leak & Auction
by Silvan M. Gebhardt 16 Aug '16

16 Aug '16

I guess you guys all heard about it but https://xorcatt.wordpress.com/2016/08/16/equationgroup-tool-leak-extrabacon… It's still - say - kinda scary what could be in the rest of this leak? Silvan

1 0

'known' DNS Problems with Migros Banking App?
by Benoit Panizzon 09 Aug '16

09 Aug '16

Hello One customer contacted us, because the Migros Banking App does not work from within our network and asked me to contact the Migros NOC to find out what we should change to make it work. From the Migros NOC I got the feedback, that this is an issue they observed with customers whose ISP have IPv6 enabled DNS Server. They recommend that either the ISP disables IPv6 on the nameservers, or that the customers uses a different ISP, for example via Mobile Phone Hotspot to use their Banking app. Apparently UPC Cablecom is another ISP with the same issue and cablecom is able to resolve the issue by disabling IPv6 for the affected customers. I am a bit puzzled. I first suspected a DNSSEC issue as our servers do validate DNSSEC. But this does not seem to be the case. I can resolve the hostnames without any problems via our DNS Servers. Our DNS Servers are IPv6 enabled. When another DNS Server has an IPv6 address, they will prefer IPv6. But our customer does not get an IPv6 address. So his local resolver does only know the IPv4 address of our DNS Servers. The Migros DNS Servers do not publish an IPv6 address. So how is IPv6 involved in this issue? The Domain in Question: mbmid.ch is: mbmid.ch. 241 IN NS ns1.datacenter-migros.ch. mbmid.ch. 241 IN NS migze104.migros.ch. mbmid.ch. 241 IN NS migze100.migros.ch. ns1.datacenter-migros.ch. 146 IN A 164.14.130.66 migze100.migros.ch. 3222 IN A 146.67.146.20 migze104.migros.ch. 3222 IN A 193.8.177.201 They are not DNSSEC Signed. The only issue I found is that ns1.datacenter-migros.ch is not published in the registrar glue record, but this also would not lead to a failure to resolve the hostname. Has anyone else come across that issue and could give me a hint where to further investigate? -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

Re: [swinog] Rack mounting Switch/Routers in Cold and Hot Isle DC
by Robert.Guentensperger＠swisscom.com 05 Aug '16

05 Aug '16

Hi Patrick better airflow vs. nice/easy cabling better airflow = less HW issues = less impact = equip. lives longer = saves finally money nice/easy cabling = nice to see = less cable problems = faster changes/troubleshooting on HW-side So my vote is clear for better airflow. Cheers, Günti > -----Original Message----- > From: swinog-bounces(a)lists.swinog.ch [mailto:swinog- > bounces(a)lists.swinog.ch] On Behalf Of Patrick Studer > Sent: Friday, August 05, 2016 2:31 PM > To: swinog(a)lists.swinog.ch > Subject: ***Signed_Message*** Re: [swinog] Rack mounting Switch/Routers > in Cold and Hot Isle DC > > Hi > > Thanks for all the input. > > Unfortunately, my questions seems not to be clear enough. > > I know, how to solve the issue. > > I just wanted to know, if anybody is strictly following the best > practice for the airflow or if some ignore the best practice in place > for a proper cabling (and perhaps just leaves an additional U free for > airflow)? > > Or in other words, which option count more (better airflow vs. nice/easy > cabling). > > Kind regards > > Patrick Studer > > ************************************************************************ > **** > ** > X-NetConsulting GmbH Internet http://www.x- > netconsulting.ch Nauenstrasse 49 E- > Mail p.studer(a)x-netconsulting.ch > CH-4052 Basel Telefon +41 61 315 85 55 > Schweiz Fax +41 61 315 85 59 > ************************************************************************ > **** > ** > > > -----Ursprüngliche Nachricht----- > Von: swinog-bounces(a)lists.swinog.ch [mailto:swinog- > bounces(a)lists.swinog.ch] > Im Auftrag von Gregor Riepl > Gesendet: Donnerstag, 4. August 2016 23:16 > An: swinog(a)lists.swinog.ch > Betreff: Re: [swinog] Rack mounting Switch/Routers in Cold and Hot Isle > DC > > > How to you solve this issue? > > The easiest solution, if there is no fancy (i.e. software controlled) > way to reverse fan flow: > > Just open the switch, unscrew the fans, turn them around and remount > them. > > Our network engineer did that countless times, and it always works. > > No need to spend heaps of $$$ on hardware with the "correct" flow > direction. > > > _______________________________________________ > swinog mailing list > swinog(a)lists.swinog.ch > http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog

1 0

Rack mounting Switch/Routers in Cold and Hot Isle DC
by Patrick Studer 05 Aug '16

05 Aug '16

Hi I'm interested, how swinog members mount their (switch/router/firewall) equipment in a hot/cold isle environment. In theory, one should mount the switches/routers in front (toward cold isle) of the rack to have an optimal airflow, but then cabling get a little bit messy. If this type of equipment is mounted in the back (toward hot isle), the cabling can be done much cleaner, but the airflow isn't optimal and in worst case, switches and routes take in hot air from other devices. How to you solve this issue? Thanks for you valuable input. Kind regards Patrick Studer **************************************************************************** ** X-NetConsulting GmbH Internet <http://www.x-netconsulting.ch/> http://www.x-netconsulting.ch Nauenstrasse 49 E-Mail <mailto:p.studer@x-netconsulting.ch> p.studer(a)x-netconsulting.ch CH-4052 Basel Telefon +41 61 315 85 55 Schweiz Fax +41 61 315 85 59 **************************************************************************** **

4 4

Re: [swinog] Rack mounting Switch/Routers in Cold and Hot Isle DC
by Jerome.Tissieres＠swisscom.com 04 Aug '16

04 Aug '16

Hi Patrick, In many datacenter switches, at least the good ones, you can choose the fan direction (front-to-back or back-to-front) and this solve this problem. Cheers, Jerome From: swinog-bounces(a)lists.swinog.ch [mailto:swinog-bounces@lists.swinog.ch] On Behalf Of Patrick Studer Sent: Thursday, 4. August 2016 09:17 To: swinog(a)swinog.ch Subject: [swinog] Rack mounting Switch/Routers in Cold and Hot Isle DC Hi I'm interested, how swinog members mount their (switch/router/firewall) equipment in a hot/cold isle environment. In theory, one should mount the switches/routers in front (toward cold isle) of the rack to have an optimal airflow, but then cabling get a little bit messy. If this type of equipment is mounted in the back (toward hot isle), the cabling can be done much cleaner, but the airflow isn't optimal and in worst case, switches and routes take in hot air from other devices. How to you solve this issue? Thanks for you valuable input. Kind regards Patrick Studer ****************************************************************************** X-NetConsulting GmbH Internet http://www.x-netconsulting.ch<http://www.x-netconsulting.ch/> Nauenstrasse 49 E-Mail p.studer(a)x-netconsulting.ch<mailto:p.studer@x-netconsulting.ch> CH-4052 Basel Telefon +41 61 315 85 55 Schweiz Fax +41 61 315 85 59 ******************************************************************************

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

swinog