swinog

swinog@lists.swinog.ch

3 participants
2941 discussions

GMX Mail
by Rony Spitzer 03 Apr '18

03 Apr '18

Hello Everybody Someone here from gmx that can contact me offlist ? Its about an email issue with one domain from our server. Thank you Kind Regards datastrom.ch We connect you datastrom.ch / Rony Spitzer Rony Spitzer Grieshalde 5 8253 Diessenhofen https://www.datastrom.ch<https://www.datastrom.ch/> UID : CHE-158-893-161 ASN 52177 as52177.net Rackspace for Education ? http://www.giganet.ch<http://www.giganet.ch/>

1 0

Re: [swinog] VDSL Standards behind BBCS Profile > 100 Mbit/s
by Simon Ryf 27 Mar '18

27 Mar '18

Hi Patrick Swisscom is using Huawei MA5811S for those installations. They’re doing G.fast with it – not VDSL. If your devices support G.9701 you don’t need to worry. Br Simon From: <swinog-bounces(a)lists.swinog.ch> on behalf of Patrick Studer <p.studer(a)x-netconsulting.ch> Date: Tuesday, 27 March 2018 at 16:52 To: "swinog(a)swinog.ch" <swinog(a)swinog.ch> Subject: [swinog] VDSL Standards behind BBCS Profile > 100 Mbit/s Hi Today, we had a customer with a line upgrade. Before the upgrade, he had a naked VDSL 20/2. After Swisscom attached Building to the Fibre (FTTB), the are able to order max. 500/120. Fibre is only in the basement of the building, where it’s „converted“ to copper. It did see the Swisscom equipment, and it looks like the equipment, they normally put in the street curb. They order an upgrade to 300/60. Current Equipment „only“ Support VDSL Profile 17a (which maxout around 100 Mbit/s downstream). ISP tell us, they can setup a profile 17a or VDSL Fast/G.Fast. But G.Fast isn’t VDSL (I know about this new standard/successor for VDSL). But never heard about VDSL Fast and could find anything on the internet or in device specification from Cisco/Zyxel. IMHO, VDSL is normally reference by ITU G.993.x or profiles like 17a, 30a, 35b etc.). Even the BBCS Approved List isn’t very specific. It only mention VDSL2 and V-VDSL2. To be able to offer the right device, we should know the exact standard behind this 300/60 Profile (G. Fast or VDSL Profile 35b or something else). So, I hoped, someone from the swinog could perhaps help. Thanks for you inputs. Kind Regards Patrick Studer ****************************************************************************** X-NetConsulting GmbH Internet http://www.x-netconsulting.ch Mischelistrasse 29 E-Mail p.studer(a)x-netconsulting.ch CH-4153 Reinach Telefon +41 61 315 85 55 Schweiz Fax +41 61 315 85 59 ****************************************************************************** _______________________________________________ swinog mailing list swinog(a)lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog

1 0

VDSL Standards behind BBCS Profile > 100 Mbit/s
by Patrick Studer 27 Mar '18

27 Mar '18

Hi Today, we had a customer with a line upgrade. Before the upgrade, he had a naked VDSL 20/2. After Swisscom attached Building to the Fibre (FTTB), the are able to order max. 500/120. Fibre is only in the basement of the building, where it’s „converted“ to copper. It did see the Swisscom equipment, and it looks like the equipment, they normally put in the street curb. They order an upgrade to 300/60. Current Equipment „only“ Support VDSL Profile 17a (which maxout around 100 Mbit/s downstream). ISP tell us, they can setup a profile 17a or VDSL Fast/G.Fast. But G.Fast isn’t VDSL (I know about this new standard/successor for VDSL). But never heard about VDSL Fast and could find anything on the internet or in device specification from Cisco/Zyxel. IMHO, VDSL is normally reference by ITU G.993.x or profiles like 17a, 30a, 35b etc.). Even the BBCS Approved List isn’t very specific. It only mention VDSL2 and V-VDSL2. To be able to offer the right device, we should know the exact standard behind this 300/60 Profile (G. Fast or VDSL Profile 35b or something else). So, I hoped, someone from the swinog could perhaps help. Thanks for you inputs. Kind Regards Patrick Studer ****************************************************************************** X-NetConsulting GmbH Internet http://www.x-netconsulting.ch <http://www.x-netconsulting.ch/> Mischelistrasse 29 E-Mail p.studer(a)x-netconsulting.ch <mailto:p.studer@x-netconsulting.ch> CH-4153 Reinach Telefon +41 61 315 85 55 Schweiz Fax +41 61 315 85 59 ******************************************************************************

1 0

Swinog-BE165 - Beer Event 165 @ Kings Cave / ZH
by Viktor Steinmann 27 Mar '18

27 Mar '18

Dear SwiNOGers, This is the rebirth of the legendary SwiNOG Beer Event. We'll have some nice meat (the John Stone Entrecote is fantastic) and of course a nice beer. Details for the next event: ----------------------------------------------- Event: Swinog-BE165 - Beer Event 165 When? Monday, 9th April 2018 19:00 Where? Kings Cave Central 1, 8001 Zürich http://central.ch/portfolio_page/kings-cave/ (GoogleMaps Link: http://goo.gl/maps/H1ez7HeF6x72) Places avaiable? 10 !! Please sign up if you're really coming - because the seats are limited! !! ----------------------------------------------- Registration: Start: Tuesday, 27th March 2018 - 15:00 Stop: Thursday, 5th April 2018 - 14:00 Reg-URL: http://swinog.be/ ----------------------------------------------- Since we have to make reservations, I need to know who's coming and who not. If you can't attend and you're registered please inform me ASAP (078 602 95 18). Kind regards, Viktor Steinmann (aka Stony)

1 0

Swisscom Hosted problem / domain not removed
by DUCHET Rémy 16 Mar '18

16 Mar '18

Hi @ll, We have some issues on some domain hosted at Swisscom. We have migrate some client out of Swisscom servers, and now we have some issues. Some domain sender are rejected because there are not loggedin.. For example : mail.hostcenter.com Remote Server returned '554 5.7.1 <mail.hostcenter.com #5.7.1 smtp; 553 5.7.1 <xxxx(a)sqships.ch>: Sender address rejected: not logged in>' dig mx sqships.ch @ns2.hostcenter.com ;; ANSWER SECTION: sqships.ch. 86400 IN MX 10 mail.hostcenter.com. But this is wrong. Domain was moved last week, and this is incorrect response. Can someone from Swisscom contact us off list, or help us ? Thanks, Rémy

1 0

Beer Events 2018
by Viktor Steinmann 13 Mar '18

13 Mar '18

Dear fellow SwiNOGers I have decided, to organize some Beer Events in the Zurich area for 2018, as the tradition must live on... Here are the dates for 2018: Monday, 9. April 2018 Monday, 4. June 2018 Monday, 3. September 2018 Monday, 1. October 2018 Monday, 3. December 2018 As you can see, we'll have only 5 events, but that's still better than nul. The invitation for the individual event will pop up about 10 days before the actual event on this list. Stay tuned! Kind regards, Viktor

1 0

IRR and trust
by Vincent Bernat 12 Mar '18

12 Mar '18

Hey! I am peering with Atlantic Metro at DE-CIX. Their IRR record is "AS-AMC". I have noticed recently some invalid prefixes: $ bgpq3 -4 -R 24 -m 24 -A -J -E AS-AMC [...] route-filter 1.0.0.0/24 exact; route-filter 1.1.1.0/24 exact; I didn't check which members of the macro pulled those prefixes (is there an easy way to get where it comes from?) but I thought information from IRR records were veted by RIR. It seems this is not the case. Is it because some RIR don't check anything or just because there is no way to secure such a macro? In this case, what is the best practice when peering with such a transit provider? Thanks! -- It were not best that we should all think alike; it is difference of opinion that makes horse-races. -- Mark Twain, "Pudd'nhead Wilson's Calendar"

5 7

##### SwiNOG #33 - RegOpen & CFP #####
by Simon Ryf 01 Mar '18

01 Mar '18

Dear SwiNOG supporter, Registration for SwiNOG #33 is open and we’re looking for Papers https://register.swinog.ch If you register until 11.05.2018 there will be a special surprise for you :-) Call for Paper!! this is the official Call for Paper email. Please send your proposal to swinog-core(a)swinog.ch The 33rd meeting of the Swiss Network Operators Group (SwiNOG) will be held in Berne on top of the Gurten on Thursday May 24th 2018. Important Dates for SwiNOG#33 01.03.2018 Call for Papers 01.03.2018 Registration opens 30.04.2018 Call for Papers closing 11.05.2018 Final publication of agenda 19.05.2018 Registration closes 22.05.2018 Deadline for all slides 24.05.2018 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>: * 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/swinog33 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 resources (domain, web, mailing-lists, etc..) and organises SwiNOG meetings. Contact: SwiNOG Organisation 8000 Zurich Switzerland

1 0

DNSSEC Training with PowerDNS
by Michael Hausding 28 Feb '18

28 Feb '18

Dear all SWITCH is organising a one day DNSSEC training together with PowerDNS The training will be given at the following dates: 9.4. Zurich, SWITCH 10.4. Bern, Uni 11.4. Carouge HESGE The one day training will give you an introduction into DNSSEC and show you how to sign DNS zones on an autoritative DNS server. We will use PowerDNS for the practical and hands on part. PowerDNS contains support for DNSSEC, enabling the easy serving of DNSSEC secured data, with minimal administrative overhead. Agenda: • Short introduction to DNSSEC • how DNSSEC works • keys / signatures / NSEC / NSEC3 • Working with DNSSEC and the PowerDNS Authoritative server • Short overview over PowerDNS Authoritative server backends (MySQL, PostgreSQL, BIND, pipe, ...) • DNSSEC signing • Pre-signed zones • Zone transfers • Utilities (pdnsutil) • The PowerDNS ALIAS record (and its future) Required skills: Unix system administrator skills and DNS server know how. The training will be delivered in english. More information and registration here: Zurich: https://www.eventbrite.com/e/dnssec-training-zurich-tickets-43350331007 Bern: https://www.eventbrite.com/e/dnssec-training-bern-tickets-43592055010 Carouge: https://www.eventbrite.com/e/dnssec-training-carouge-tickets-43592840359 Best regards 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

4 4

Mail to CNAME a thing?
by Markus Wild 22 Feb '18

22 Feb '18

Hi there, I've just come across a weird mail reception problem of some mails from Microsoft. Our servers insist that a specified MAIL FROM address can be resolved correctly, and this usually boils down to the following checks on the domain-part of the email-address specified: - is there an MX? Does the target resolve using an A record (not a CNAME), and does it resolve to a publically reachable address (not RFC1918 or localhost etc) - if there is no MX, is there an A record that fulfils the same criteria as the MX target above? - if none of these are true, the address is considered to be invalid and mail is rejected Since about Feb 15, I've now come across mails from account-security-noreply(a)accountprotection.microsoft.com that get rejected. When I manually perform the above steps, I can see why, and I also see a first: the domain part is actually a CNAME, something I've not encountered mentioned in standards as being a legal way to perform address resolution when delivering email. But, I also don't recall reading about rules that explicitly deny this, contrary to the very explicit rules that for example deny having MX point to CNAME. The domain setup here is borked in multiple ways however: $ host -t mx accountprotection.microsoft.com Host accountprotection.microsoft.com not found: 3(NXDOMAIN) $ host -t a accountprotection.microsoft.com Host accountprotection.microsoft.com not found: 3(NXDOMAIN) BUT: $ host -t cname accountprotection.microsoft.com accountprotection.microsoft.com is an alias for mail.msa.msidentity.com. and even if we should allow use of a CNAME here, we'd have to apply the same rules as stated initially on the CNAME target, and these fail as well: $ host -t mx mail.msa.msidentity.com. Host mail.msa.msidentity.com not found: 3(NXDOMAIN) $ host -t a mail.msa.msidentity.com. Host mail.msa.msidentity.com not found: 3(NXDOMAIN) So, what's your take on this? Does someone see a legal way to resolv this sender, that I've missed? Am I right in considering these addresses to be unresolvable and thus reject these mails? Who would I have to report this to at Microsoft to have any chance of a human person looking at the issue? Cheers, Markus

6 10

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