swinog November 2017

swinog@lists.swinog.ch

16 participants
10 discussions

contact request swisscom messaging (bluewin)

by Patrick Landolt

Hi Can someone from bluewin (swisscom messaging) please contact me off-list to resolve an issue regarding mail delivery reputation? Various contact information can be found below. Our mailserver is getting "You are not allowed to send us mail. Please see https://www.swisscom.ch/en/res/hilfe/ip-blacklist.html”. I already submitted information on the mentioned form yesterday but unfortunately did not receive any response yet. Best regards, Patrick Landolt -------------------------------------- Patrick Landolt Leiter Softwareentwicklung Mitglied der Geschäftsleitung mailXpert GmbH Schulstrasse 37 8050 Zürich Tel: +41 44 222 22 14 Fax: +41 44 222 22 13 Mail: patrick.landolt(a)mailXpert.ch Web: https://www.mailXpert.ch -------------------------------------- www.mailXpert.ch Professionelles E-Mail Marketing von ARTACK WebLab GmbH

5 years, 3 months

GCSC critical infrastructure protection questions: your input needed.

by Bill Woodcock

One of PCH’s long-term efforts has been to encourage governments to restrict their use of offensive cyber attacks against civilian networks. We've successfully gotten that effort out of the U.N., where it was floundering, and into a well-supported stand-alone commission. It’s being taken seriously by governments, and will be one of the main topics under discussion at the Global Conference on Cyberspace in Delhi next week. The work has been divided into two working-groups: one is addressing the question of what a norm should say (i.e. “Governments shouldn’t cyber-attack X”). The other is addressing the question of what infrastructures should be protected (i.e. what is the X that shouldn’t be attacked). I’m chairing that second working group. The main thing we’re delivering in Delhi is the result of a survey of what infrastructure people think should be protected. That survey is still open, and we’d like as many people to respond as possible. So, please consider doing so. It’ll only take a couple of minutes, and it’s a critical part of an admittedly very lengthy process to make your life easier. https://www.surveymonkey.com/r/criticalinfrastructure Much appreciated, -Bill Links in case you want to pursue further reading on the things I’ve mentioned above: https://en.wikipedia.org/wiki/Eligible_Receiver_97 https://lawfareblog.com/un-gge-failed-international-law-cyberspace-doomed-w… https://cyberstability.org/about/ https://gccs2017.in https://en.wikipedia.org/wiki/Global_Conference_on_CyberSpace -Bill

5 years, 4 months

google.ch high latency

by Kägi Adrian

Hi all We’re face high latency of google.ch (and other European tlds) from our AS203732 $ ping www.google.ch 95ms $ ping www.google.fr 80ms $ ping www.google.de<http://www.google.de> 90ms -> % traceroute www.google.ch traceroute to www.google.ch (216.58.205.131), 30 hops max, 60 byte packets 1 192.168.11.1 (192.168.11.1) 0.116 ms 0.151 ms 0.124 ms 2 dvbnre01-po8-2g.dvbern.ch (185.125.164.2) 0.456 ms 0.568 ms 0.889 ms 3 i64beb-011-ten0-2-0-2x136.bb.ip-plus.net (193.247.169.41) 1.622 ms 1.312 ms 1.354 ms 4 i64beb-010-ten2-5.bb.ip-plus.net (138.187.157.36) 1.179 ms i64beb-000-ten2-5.bb.ip-plus.net (138.187.157.22) 1.057 ms i64beb-010-ten2-5.bb.ip-plus.net (138.187.157.36) 0.877 ms 5 i79zhb-005-ten0-5-0-4-7.bb.ip-plus.net (138.187.130.46) 3.332 ms i62bsw-025-ten0-1-0-5.bb.ip-plus.net (138.187.130.44) 5.882 ms i79zhb-005-ten0-5-0-4-7.bb.ip-plus.net (138.187.130.46) 3.312 ms 6 i00mil-005-ae1.bb.ip-plus.net (138.187.129.27) 7.605 ms i00dcx-005-hun2-0-0.bb.ip-plus.net (138.187.129.83) 6.340 ms i00mil-005-ae1.bb.ip-plus.net (138.187.129.27) 6.922 ms 7 de-cix.fra.google.com (80.81.192.108) 8.945 ms google.mix-it.net (217.29.66.96) 45.949 ms de-cix.fra.google.com (80.81.192.108) 8.862 ms 8 108.170.251.208 (108.170.251.208) 8.786 ms 108.170.251.144 (108.170.251.144) 16.055 ms 108.170.252.19 (108.170.252.19) 8.986 ms 9 108.170.229.168 (108.170.229.168) 9.417 ms 209.85.242.79 (209.85.242.79) 9.364 ms 216.239.42.13 (216.239.42.13) 56.092 ms 10 mil04s27-in-f131.1e100.net (216.58.205.131) 58.975 ms 59.013 ms 209.85.254.61 (209.85.254.61) 14.983 ms Providers: Swisscom, UPC, Cyberlink Does anyone facing same issues? Cheers Adrian Adrian Kägi Senior System Engineer DV Bern AG | Nussbaumstrasse 21 | Postfach 106 | CH-3000 Bern 22 T +41 31 378 24 24 | D +41 31 378 24 60 www.dvbern.ch<http://www.dvbern.ch>

5 years, 4 months

Selling Cisco 7206 VXR NPEG1 - good price

by Hofer Ruedi

Dear all I am selling 3 x Cisco 7206 VXR / NPEG1 / dual power supply They were bought in 2003 and used until recently. They are in good condition and clean. See tech spec below for details. Price: CHF33.30/piece (bid >0 welcome;) - No guarantee No Support - No Lasers - No Cables - No Shipping, pickup at our premises only, see address below - Cash-only payment First come first served. Please contact me offlist if interestet. mailto:ruedi.hofer@ewb.ch Freundliche Grüsse Ruedi Hofer Leiter Telecom Center Energie Wasser Bern Monbijoustrasse 11, Postfach, 3001 Bern ruedi.hofer(a)ewb.ch<mailto:ruedi.hofer@ewb.ch>, ewb.ch<http://www.ewb.ch/> Summary : - Cisco 7206VXR, 6-slot chassis - NPE-G1 / 512MB RAM / 64MB Flash Card - 3x1GB Interface Web Refrence : https://www.cisco.com/c/en/us/td/docs/routers/7200/install_and_upgrade/netw… ####################################### RAW DATA ################################################## ewb-ch-emc-brn01-rm-01#sh inventory raw NAME: "Chassis", DESCR: "Cisco 7206VXR, 6-slot chassis" PID: CISCO7206VXR , VID: , SN: 30827013 NAME: "I/O and CPU Slot 0", DESCR: "I/O and Processor Slot Container" PID: , VID: , SN: NAME: "NPE-G1 0", DESCR: "Cisco 7200 Series Network Processing Engine NPE-G1" PID: NPE-G1 , VID: , SN: 31248843 NAME: "GBIC Port Container 0/1", DESCR: "GBIC Port Container" PID: , VID: , SN: NAME: "GigabitEthernet0/1", DESCR: "BCM1250 Internal MAC" PID: , VID: , SN: NAME: "GBIC Port Container 0/2", DESCR: "GBIC Port Container" PID: , VID: , SN: NAME: "GigabitEthernet0/2", DESCR: "BCM1250 Internal MAC" PID: , VID: , SN: NAME: "GBIC Port Container 0/3", DESCR: "GBIC Port Container" PID: , VID: , SN: NAME: "GigabitEthernet0/3", DESCR: "BCM1250 Internal MAC" PID: , VID: , SN: NAME: "Flash Card Slot Container CPU", DESCR: "Flash Card Slot Container CPU" PID: , VID: , SN: NAME: "disk2", DESCR: "64MB Compact Flash Disk for NPE-G1" PID: MEM-NPE-G1-FLD64 , VID: , SN: NAME: "NPE Inlet Temperature 0", DESCR: "NPE Inlet Temperature Sensor" PID: , VID: , SN: NAME: "NPE Outlet Temperature 0", DESCR: "NPE Outlet Temperature Sensor" PID: , VID: , SN: NAME: "+3.45 V Voltage 0", DESCR: "+3.45 V Voltage Sensor" PID: , VID: , SN: NAME: "+5.15 V Voltage 0", DESCR: "+5.15 V Voltage Sensor" PID: , VID: , SN: NAME: "+12.15 V Voltage 0", DESCR: "+12.15 V Voltage Sensor" PID: , VID: , SN: NAME: "-11.95 V Voltage 0", DESCR: "-11.95 V Voltage Sensor" PID: , VID: , SN: NAME: "Gi0/1", DESCR: "BCM1250 Internal MAC RJ45" PID: , VID: , SN: NAME: "Gi0/2", DESCR: "BCM1250 Internal MAC RJ45" PID: , VID: , SN: NAME: "Gi0/3", DESCR: "BCM1250 Internal MAC RJ45" PID: , VID: , SN: NAME: "PA Slot 1", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PA Slot 2", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PA Slot 3", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PA Slot 4", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PA Slot 5", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PA Slot 6", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PEM 0", DESCR: "Power Supply Container" PID: , VID: , SN: NAME: "Power Supply 0", DESCR: "Cisco 7200 AC Power Supply" PID: PWR-7200-AC , VID: , SN: NAME: "PEM 1", DESCR: "Power Supply Container" PID: , VID: , SN: NAME: "Power Supply 1", DESCR: "Cisco 7200 AC Power Supply" PID: PWR-7200-AC , VID: , SN: ewb-ch-emc-brn01-rm-01#sh ver ewb-ch-emc-brn01-rm-01#sh version Cisco IOS Software, 7200 Software (C7200-JK9O3S-M), Version 12.4(8c), RELEASE SOFTWARE (fc3) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2006 by Cisco Systems, Inc. Compiled Tue 12-Dec-06 03:30 by prod_rel_team ROM: System Bootstrap, Version 12.2(8r)B, RELEASE SOFTWARE (fc1) BOOTLDR: 7200 Software (C7200-KBOOT-M), Version 12.2(15)B, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) System image file is "disk2:c7200-jk9o3s-mz.124-8c.bin" Last reload reason: Reload Command This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately. A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html If you require further assistance please contact us by sending email to export(a)cisco.com<mailto:export@cisco.com>. Cisco 7206VXR (NPE-G1) processor (revision A) with 491520K/32768K bytes of memory. Processor board ID 30827013 SB-1 CPU at 700MHz, Implementation 1025, Rev 0.2, 512KB L2 Cache 6 slot VXR midplane, Version 2.7 Last reset from power-on PCI bus mb1 (Slots 1, 3 and 5) has a capacity of 600 bandwidth points. Current configuration on bus mb1 has a total of 0 bandwidth points. This configuration is within the PCI bus capacity and is supported. PCI bus mb2 (Slots 2, 4 and 6) has a capacity of 600 bandwidth points. Current configuration on bus mb2 has a total of 0 bandwidth points. This configuration is within the PCI bus capacity and is supported. Please refer to the following document "Cisco 7200 Series Port Adaptor Hardware Configuration Guidelines" on Cisco.com <http://www.cisco.com> for c7200 bandwidth points oversubscription and usage guidelines. 3 Gigabit Ethernet interfaces 509K bytes of NVRAM. 62976K bytes of ATA PCMCIA card at slot 2 (Sector size 512 bytes). 16384K bytes of Flash internal SIMM (Sector size 256K). Configuration register is 0x2102

5 years, 4 months

Re: [swinog] RIPE database and more specific routes

by Scott Weeks

: But I am concerned some people may build filters using : only exact matches, so it seems safer to have route : objects for more specifics. :: I´d suggest to create each route object for each :: announced prefix...IMHO you are very right - there are :: for sure networks out there, which will filter your :: prefixes, when you do not have a matching route object :: entry ... That seems painful when fast action is required. Say you have a /16 and someone is hijacking a /23 withing it. Before mitigating damage by announcing the two /24s you'd have to update the registry and wait for the upstream to accept it? Do you just preregister all the /24, /23, /22, etc prefix combinations in advance? scott _______________________________________________ swinog mailing list swinog(a)lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog _______________________________________________ swinog mailing list swinog(a)lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog

5 years, 4 months

Selling Cisco 7206 VXR NPEG1 - new price

by Hofer Ruedi

5 years, 4 months

RIPE database and more specific routes

by Vincent Bernat

Hey! I am updating the route/inetnum objects in the RIPE database and I am wondering if I have to create more specific route objects. For example, I have the following routes announced: - 89.145.160.0/21 - 89.145.160.0/22 (FR7) - 89.145.164.0/23 (DK2) - 89.145.166.0/23 (GV2) Each more specific route is announced in a different location. Should I create only the top route object or should I create a route object for each announce? If I look at bgpq3, I see by default, it uses exact matches: $ bgpq3 -4 -J -E AS61098 | grep 89.145 route-filter 89.145.160.0/21 exact; route-filter 89.145.160.0/22 exact; route-filter 89.145.164.0/23 exact; route-filter 89.145.166.0/23 exact; However, I use it this way: $ bgpq3 -R 24 -4 -J -E AS61098 | grep 89.145 route-filter 89.145.160.0/21 upto /24; But I am concerned some people may build filters using only exact matches, so it seems safer to have route objects for more specifics. -- If more of us valued food and cheer and song above hoarded gold, it would be a merrier world. -- J.R.R. Tolkien

5 years, 4 months

Hoodie found @ SwiNOG #32

by Steven Glogger

Who‘s missing something like this? :) greetings -steven gruss -steven

5 years, 4 months

##### SwiNOG#32 - Travel Info #####

by Simon Ryf

Dear SwiNOG Community, Please find general information about the SwiNOG #32 meeting below. Date: 09.11.2017 - Registration 08h15 - 09h15 Location: Gurtenpark, Bern: https://goo.gl/maps/kuxy4QUrcoy >From Bern main station you may take: - S-Bahn S3 Belp and exit at Wabern station - Tram 9 (Wabern) and exit at Gurtenbahn stop Then take the Gurtenbahn to the Gurtenpark. -> You DO NOT have to pay a fee, just tell you attend to the SwiNOG event. Don’t throw away the ticket - you'll need it to get back down. Map (Ground Station of the cable rail): https://goo.gl/maps/5uSKtgbianM2 Suggested trains from Geneva: 06h14 Zurich: 07h02 WIRELESS ACCESS During the meeting, you have access to free WLAN! See you at SwiNOG #32! Simon Ryf SwiNOG Organisation

5 years, 4 months

## Agenda - SwiNOG#32'ers - we're ready ##

by Simon Ryf

Dear SwiNOG community, Agenda for SwiNOG #32 on Tuesday 09.11.2017 on top of Gurten. Registration ends 03.10.2017 23:59:00, after that - please write us for late reg (with extra costs). We still have time for Lightning Talks, if you’re up for it, you’ll get a free voucher for the next event or if submitted before 06.11.2017 – for SwiNOG#32 CHF 100.- for 5 minutes (just saying…) Agenda http://www.swinog.ch/meetings/swinog32/ Sponsor Presentation / tba | tba (Extreme Networks) Free Range Routing or how we ditched OSPF for BGP unnumbered (based on RFC5549) | Manuel Schweizer (cloudscale.ch) As a contributor to the FRR project, I’m going to explain what FRR is and how we at cloudscale.ch are using it. Furthermore, I will shed some light at why we chose a certain x86-based hardware platform and provide a future outlook of where FRR is heading. Network Unit Testing with SaltStack | Urs Baumann (INS - Institute for Networked Solutions) Enabling unit testing in the network with Nuts (network unit testing system) and SaltStack. Technical presentation how the open source software Nuts uses SaltStack to test the network. colt onDemand - from visions in 2012 to reality in 2017 | Andreas Glag (Colt) SwissIX Update | Manuel Schweizer (SwissIX) SwissIX Update Flowmon DDoS Defender | Pavel Minařík (Flowmon) Flowmon DDoS Defender is a scalable anti-DDoS solution leveraging netflow data from routers or dedicated network probes for real-time detection and automated mitigation of volumetric attacks led against customer’s infrastructure. It provides the state of the art detection with automated mitigation within a minute, deep understanding of attack characteristics and a full-range of methods for successful attack mitigation ranging from alerting (e-mail, syslog, SNMP trap), traffic diversion (PBR, BGP, RTBH, Flowspec), execution of scripts, mitigation in cloud with Scrubbing centres or on-premise through specific out of-band DDoS systems. if (network == server) { magic happens } | Attilla de Groot (Cumulus Networks) Automating the network has become common practice. One thing that we don’t want to automate are operator mistakes on a fabric level. How can this be prevented by building a CI/CD environment using Cumulus, NetQ, Ansible and Gitlab. Introduction to LoRaWAN | Christian Mäder LoRaWAN is a network stack designed mostly to retrieve data from IoT sensors with limited power source. This talk will be an introduction to how this network stack works; like how it does the addressing and routing or what it's secrecy promises are. Piranha: where all the fishy routes meet... | Pascal Gloor (Quickline) Do you really know what's going on in your BGP? Analyse your BGP in realtime. Update - Communityrack.org and Community-IX.ch | Markus Meier (Communityrack.org) Community Update Social Event Looking forward to seeing all of you!!! Simon SwiNOG

5 years, 4 months

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

swinog November 2017