From mgalante at ripe.net Tue Jun 2 12:03:25 2015 From: mgalante at ripe.net (Michela Galante) Date: Tue, 2 Jun 2015 12:03:25 +0200 Subject: [atlas] COMSATS Internet Services (Pakistan) has joined RIPE Atlas anchors Message-ID: <4A93C2BE-D69C-4181-925E-0DDE92943FAC@ripe.net> Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called pk-isb-as7590 and it is hosted by COMSATS Internet Services in Islamabad, Pakistan, and sponsored by APNIC. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team atlas at ripe.net -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2612 bytes Desc: not available URL: From arsaeed at comsats.net.pk Thu Jun 4 06:50:06 2015 From: arsaeed at comsats.net.pk (Abdul Rehman Saeed(COMSATS)) Date: Thu, 04 Jun 2015 09:50:06 +0500 Subject: [atlas] COMSATS Internet Services (Pakistan) has joined RIPE Atlas anchors In-Reply-To: <4A93C2BE-D69C-4181-925E-0DDE92943FAC@ripe.net> References: <4A93C2BE-D69C-4181-925E-0DDE92943FAC@ripe.net> Message-ID: <20150604095006.978935oaih1fqq04@isbmail.comsats.net.pk> Thanks RIPE NCC team and congratulations also to you and atlas community. Best Regards Quoting Michela Galante : > Dear RIPE Atlas users, > > We're happy to announce that another RIPE Atlas anchor has joined > the network and is now available as a target for probe hosts > conducting their own user-defined measurements. > > The new anchor is called pk-isb-as7590 and it is hosted by COMSATS > Internet Services in Islamabad, Pakistan, and sponsored by APNIC. > > Anchoring measurements (ping, ping6, traceroute and traceroute6) are > scheduled towards this anchor from all the other anchors as well as > several hundred probes, providing a continual overview of regional > reachability. Results of these measurements are available as raw > data in JSON format, and visualised on the map and "seismograph" > with many configurable features. > > You can access the anchoring measurements for all anchors at: > https://atlas.ripe.net/anchors/list/ > > Learn more about RIPE Atlas anchors at: > https://atlas.ripe.net/about/anchors/ > > Thank you for participating in RIPE Atlas! > > Kind Regards, > > RIPE Atlas Team > atlas at ripe.net -- Abdul Rehman Saeed General Manager(Technical) COMSATS Internet Services 051-9208781 03008336681 From mgalante at ripe.net Thu Jun 4 16:43:31 2015 From: mgalante at ripe.net (Michela Galante) Date: Thu, 4 Jun 2015 16:43:31 +0200 Subject: [atlas] ASTI (Philippines) has joined RIPE Atlas anchors Message-ID: Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called ph-qzt-as9821 and it is hosted by ASTI in Quezon City, Philippines, and sponsored by APNIC. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team atlas at ripe.net -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2612 bytes Desc: not available URL: From elane at ripe.net Mon Jun 8 11:45:43 2015 From: elane at ripe.net (Eamonn Lane) Date: Mon, 8 Jun 2015 11:45:43 +0200 Subject: [atlas] Conova Communications GmbH, Salzburg, Austria has joined RIPE Atlas anchors Message-ID: <59FD0AF1-9500-41C8-89DE-A6948EE12824@ripe.net> Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called at-szg-as5404 and is hosted by : Conova Communications GmbH in Salzburg, Austria . Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, RIPE Atlas Team RIPE NCC atlas at ripe.net -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2598 bytes Desc: not available URL: From elane at ripe.net Mon Jun 8 11:53:12 2015 From: elane at ripe.net (Eamonn Lane) Date: Mon, 8 Jun 2015 11:53:12 +0200 Subject: [atlas] ADP, Saint-Denis, France has joined RIPE Atlas anchors Message-ID: <9DF15EF2-C756-49C1-BAAB-8ABE1B355BED@ripe.net> Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called fr-ysd-as201958 and is hosted by : ADP, Saint-Denis, in France. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, RIPE Atlas Team RIPE NCC atlas at ripe.net -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2598 bytes Desc: not available URL: From lists at eckel-edv.de Wed Jun 10 07:55:28 2015 From: lists at eckel-edv.de (Peter Eckel) Date: Wed, 10 Jun 2015 07:55:28 +0200 Subject: [atlas] Notifications for unreachable probes Message-ID: <8AF3B1F5-91FE-40BA-886B-C963ACABFEC1@eckel-edv.de> Hi, I have set up a notification if my probe 10293 is down for more than 15 minutes. Since my main mail address is located on a server likely to be unavailable if the probe is down, the notification was set to a different mail address not in the same network. Unfortunately it seems that the notification address is ignored, and the notification is sent to the reporting address instead. Does anyone else see that problem as well? Regards, Peter. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 203 bytes Desc: Message signed with OpenPGP using GPGMail URL: From jterbeest at ripe.net Wed Jun 10 11:15:03 2015 From: jterbeest at ripe.net (Johan ter Beest) Date: Wed, 10 Jun 2015 11:15:03 +0200 Subject: [atlas] Notifications for unreachable probes In-Reply-To: <8AF3B1F5-91FE-40BA-886B-C963ACABFEC1@eckel-edv.de> References: <8AF3B1F5-91FE-40BA-886B-C963ACABFEC1@eckel-edv.de> Message-ID: <55780017.8050804@ripe.net> Hi Peter, On 10/06/15 07:55, Peter Eckel wrote: > Hi, > > I have set up a notification if my probe 10293 is down for more than 15 minutes. Since my main mail address is located on a server likely to be unavailable if the probe is down, the notification was set to a different mail address not in the same network. > > Unfortunately it seems that the notification address is ignored, and the notification is sent to the reporting address instead. Does anyone else see that problem as well? This was indeed a bug. It's fixed now and will be deployed next week. Thanks for reporting it! Regards, Johan ter Beest RIPE Atlas team > > Regards, > > Peter. From ben.ohara at bomboratech.com.au Mon Jun 15 07:52:29 2015 From: ben.ohara at bomboratech.com.au (Ben O'Hara) Date: Mon, 15 Jun 2015 05:52:29 +0000 Subject: [atlas] Atlas Anchors and LogJam Message-ID: <4730FB40-26D0-4934-B335-3356EB60664E@bomboratech.com.au> Hi, We host an Atlas Anchor, but our network monitoring still shows it being vulnerable to Logjam. Can you please let us know when this will be upgraded to fix the vulnerability? Cheers BEN O'HARA Senior Network and Systems Engineer P +61 9866 3710 [Bombora Technologies Logo] www.bomboratech.com.au Follow us on Twitter The Bombora Technologies group of companies includes AusRegistry, ARI Registry Services, AusRegistry International and ZOAK Solutions. The information contained in this communication is intended for the named recipients only. It is subject to copyright and may contain legally privileged and confidential information and if you are not an intended recipient you must not use, copy, distribute or take any action in reliance on it. If you have received this communication in error, please delete all copies from your system and notify us immediately. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image8e91e6.PNG Type: image/png Size: 29012 bytes Desc: image8e91e6.PNG URL: From romeo.zwart at ripe.net Mon Jun 15 11:09:14 2015 From: romeo.zwart at ripe.net (Romeo Zwart) Date: Mon, 15 Jun 2015 11:09:14 +0200 Subject: [atlas] Atlas Anchors and LogJam In-Reply-To: <4730FB40-26D0-4934-B335-3356EB60664E@bomboratech.com.au> References: <4730FB40-26D0-4934-B335-3356EB60664E@bomboratech.com.au> Message-ID: <557E963A.9020608@ripe.net> Hi Ben, On 15/06/15 07:52 , Ben O'Hara wrote: > Hi, > > We host an Atlas Anchor, but our network monitoring still shows it being > vulnerable to Logjam. That is correct. Since the information served over https from the Atlas anchors is fully public anyway, our assessment was that this vulnerability is not a very sensitive one on the anchors. > Can you please let us know when this will be upgraded to fix the > vulnerability? This will most likely happen within the coming two weeks. Kind regards, Romeo > Cheers > > BEN O'HARA > Senior Network and Systems Engineer > P +61 9866 3710 > > > Bombora Technologies Logo > www.bomboratech.com.au > Follow us on Twitter > > The Bombora Technologies group of companies includes AusRegistry, ARI > Registry Services, AusRegistry International and ZOAK Solutions. > > The information contained in this communication is intended for the > named recipients only. It is subject to copyright and may contain > legally privileged and confidential information and if you are not an > intended recipient you must not use, copy, distribute or take any action > in reliance on it. If you have received this communication in error, > please delete all copies from your system and notify us immediately. From BECHA at ripe.net Wed Jun 17 10:14:00 2015 From: BECHA at ripe.net (Vesna Manojlovic) Date: Wed, 17 Jun 2015 10:14:00 +0200 Subject: [atlas] HTTP Measurements with RIPE Atlas In-Reply-To: <558044F8.2030000@ripe.net> References: <558044F8.2030000@ripe.net> Message-ID: <55812C48.50203@ripe.net> Dear colleagues, After a discussion with the community about HTTP measurements, RIPE NCC will start implementing this as a publicly available measurement type. Please find some more information on RIPE Labs: https://labs.ripe.net/Members/kistel/http-measurements-with-ripe-atlas Kind regards, Vesna Manojlovic RIPE NCC From pk at DENIC.DE Wed Jun 17 10:21:20 2015 From: pk at DENIC.DE (Peter Koch) Date: Wed, 17 Jun 2015 10:21:20 +0200 Subject: [atlas] HTTP Measurements with RIPE Atlas In-Reply-To: <55812C48.50203@ripe.net> References: <558044F8.2030000@ripe.net> <55812C48.50203@ripe.net> Message-ID: <20150617082120.GR27702@x28.adm.denic.de> On Wed, Jun 17, 2015 at 10:14:00AM +0200, Vesna Manojlovic wrote: > After a discussion with the community about HTTP measurements, > RIPE NCC will start implementing this as a publicly available > measurement type. > > Please find some more information on RIPE Labs: > https://labs.ripe.net/Members/kistel/http-measurements-with-ripe-atlas clarifying question: does this literally mean "http", i.e., TCP port 80 only, no TLS? Thanks, Peter From robert at ripe.net Wed Jun 17 10:26:45 2015 From: robert at ripe.net (Robert Kisteleki) Date: Wed, 17 Jun 2015 10:26:45 +0200 Subject: [atlas] HTTP Measurements with RIPE Atlas In-Reply-To: <20150617082120.GR27702@x28.adm.denic.de> References: <558044F8.2030000@ripe.net> <55812C48.50203@ripe.net> <20150617082120.GR27702@x28.adm.denic.de> Message-ID: <55812F45.6070304@ripe.net> On 2015-06-17 10:21, Peter Koch wrote: > On Wed, Jun 17, 2015 at 10:14:00AM +0200, Vesna Manojlovic wrote: > >> After a discussion with the community about HTTP measurements, >> RIPE NCC will start implementing this as a publicly available >> measurement type. >> >> Please find some more information on RIPE Labs: >> https://labs.ripe.net/Members/kistel/http-measurements-with-ripe-atlas > > clarifying question: does this literally mean "http", i.e., TCP port 80 > only, no TLS? > > Thanks, > Peter Yes, it does. Cheers, Robert From bjorn at mork.no Wed Jun 17 13:38:59 2015 From: bjorn at mork.no (=?utf-8?Q?Bj=C3=B8rn_Mork?=) Date: Wed, 17 Jun 2015 13:38:59 +0200 Subject: [atlas] atlas anchor DANE records Message-ID: <87zj3y7eek.fsf@nemi.mork.no> Hello, I just noticed "We also generate a DANE record for each anchor" in the docs and became instantly curious. There aren't that many DANE records out there in the wild :) The records seem to be pointing to a self signed certificate (as documented), but with 'usage' = 1 instead of 3 as expected. At least the two records I looked at had this - I assume they are all created the same way. Is this intentional? It makes 'normal' verification fail: bjorn at canardo:~$ tlsa --debug --verify nl-ams-as3333.anchors.atlas.ripe.net Received the following record for name _443._tcp.nl-ams-as3333.anchors.atlas.ripe.net.: Usage: 1 (End-Entity Constraint + chain to CA) Selector: 0 (Certificate) Matching Type: 1 (SHA-256) Certificate for Association: 88422d55424ca8f6f74e165016851cb195fc0919f82f8762574a4d71868964e9 This record is valid (well-formed). Attempting to verify the record with the TLS service... Got the following IP: 193.0.19.107 FAIL (Usage 1): Certificate offered by the server matches the one mentioned in the TLSA record but the following error was raised during PKIX validation: X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT The matched certificate has Subject: /C=nl/ST=ams/L=ams/O=as3333/CN=nl-ams-as3333.anchors.atlas.ripe.net Got the following IP: 2001:67c:2e8:11::c100:136b FAIL (Usage 1): Certificate offered by the server matches the one mentioned in the TLSA record but the following error was raised during PKIX validation: X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT The matched certificate has Subject: /C=nl/ST=ams/L=ams/O=as3333/CN=nl-ams-as3333.anchors.atlas.ripe.net bjorn at canardo:~$ tlsa --debug --verify se-sto-as8674.anchors.atlas.ripe.net Received the following record for name _443._tcp.se-sto-as8674.anchors.atlas.ripe.net.: Usage: 1 (End-Entity Constraint + chain to CA) Selector: 0 (Certificate) Matching Type: 1 (SHA-256) Certificate for Association: 2d92e341d2181011c520ad92229155e1350fc4f7b9e628198be1f9589ec7a53f This record is valid (well-formed). Attempting to verify the record with the TLS service... Got the following IP: 185.42.136.158 FAIL (Usage 1): Certificate offered by the server matches the one mentioned in the TLSA record but the following error was raised during PKIX validation: X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT The matched certificate has Subject: /O=AS8674/L=STO/C=SE/CN=se-sto-as8674.anchors.atlas.ripe.net Got the following IP: 2a01:3f0:0:60::5 FAIL (Usage 1): Certificate offered by the server matches the one mentioned in the TLSA record but the following error was raised during PKIX validation: X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT The matched certificate has Subject: /O=AS8674/L=STO/C=SE/CN=se-sto-as8674.anchors.atlas.ripe.net What is the intended use of these records? And why doesn't https://atlas.ripe.net/ have a DANE record as well? :) Bj?rn From BECHA at ripe.net Thu Jun 18 16:55:08 2015 From: BECHA at ripe.net (Vesna Manojlovic) Date: Thu, 18 Jun 2015 16:55:08 +0200 Subject: [atlas] Join our new webinar on "Advanced RIPE Atlas Usage" In-Reply-To: <5582BF84.7050402@ripe.net> References: <5582BF84.7050402@ripe.net> Message-ID: <5582DBCC.4070906@ripe.net> Dear colleagues, We are pleased to announce our new webinar: Advanced RIPE Atlas Usage, aiming to teach LIRs how to use RIPE Atlas measurements for network monitoring and troubleshooting. https://www.ripe.net/support/training/learn-online/webinars/advanced-ripe-atlas-usage-webinar It's part of the series of interactive on-line learning sessions, that give you the opportunity to learn and interact with trainers without leaving your desk, as well as for hands-on practice, and to get your questions answered by developers. Learn how to: - Use RIPE Atlas measurements for network monitoring and troubleshooting - Use API calls for measurement creation - Integrate RIPE Atlas with existing monitoring systems There are three dates scheduled: 2nd July, 27th August & 17th September. Webinars start at 11:30 UTC, and take about one hour. Register now at: https://www.ripe.net/support/training/learn-online/webinars We look forward to seeing you online. Kind regards, Vesna Manojlovic RIPE NCC From BECHA at ripe.net Fri Jun 19 14:44:22 2015 From: BECHA at ripe.net (Vesna Manojlovic) Date: Fri, 19 Jun 2015 14:44:22 +0200 Subject: [atlas] Enabling Data Compression in RIPE Atlas In-Reply-To: <55840C7B.5080403@ripe.net> References: <55840C7B.5080403@ripe.net> Message-ID: <55840EA6.6020509@ripe.net> Dear colleagues, We?d like to enable gzip compression on all of RIPE Atlas' measurement API calls ? but thanks to the BREACH vulnerability, doing so could mean that some enterprising individual with an obscene amount of time on their hands might be able read the contents of the responses. This means measurement results as well as metadata for measurements ? including the small number of measurements not marked as ?public?. We believe the drawbacks are negligible, but we?re looking for community support. Find out more in this RIPE Labs article: https://labs.ripe.net/Members/daniel_quinn_39/enabling-data-compression-in-ripe-atlas Regards, Vesna Manojlovic From colinj at mx5.org.uk Sun Jun 21 21:40:03 2015 From: colinj at mx5.org.uk (Colin Johnston) Date: Sun, 21 Jun 2015 20:40:03 +0100 Subject: [atlas] Fwd: Probe 2317 is down (home fibre) References: <20150621193007.16430.61386@janus.atlas.ripe.net> Message-ID: <09619879-9C86-4020-8156-9F06D9A1C6EA@mx5.org.uk> seems fine to me ? dont have connectivity to ripe site though from BT network range in uk what is telia upto ? Colins-iMac:~ colinj$ traceroute www.ripe.net traceroute to www.ripe.net (193.0.6.139), 64 hops max, 52 byte packets 1 bthomehub (192.168.1.254) 1.913 ms 1.078 ms 1.078 ms 2 * * * 3 * * * 4 31.55.185.196 (31.55.185.196) 16.187 ms 15.477 ms 15.443 ms 5 195.99.127.142 (195.99.127.142) 15.557 ms 195.99.127.130 (195.99.127.130) 16.274 ms 195.99.127.128 (195.99.127.128) 16.602 ms 6 vhsaccess2-pos1-0.faraday.fixed.bt.net (195.99.127.9) 16.979 ms 16.611 ms 195.99.127.25 (195.99.127.25) 17.097 ms 7 166-49-211-240.eu.bt.net (166.49.211.240) 16.413 ms 166-49-211-236.eu.bt.net (166.49.211.236) 16.225 ms 166-49-211-238.eu.bt.net (166.49.211.238) 15.821 ms 8 213.248.82.249 (213.248.82.249) 16.880 ms 15.785 ms 15.470 ms 9 ldn-bb2-link.telia.net (62.115.137.194) 16.633 ms 213.248.82.249 (213.248.82.249) 15.631 ms 15.400 ms 10 ldn-bb3-link.telia.net (80.91.248.90) 15.776 ms ldn-bb2-link.telia.net (213.155.136.62) 16.815 ms adm-bb4-link.telia.net (62.115.142.221) 22.936 ms 11 adm-b2-link.telia.net (62.115.141.51) 25.759 ms adm-b2-link.telia.net (80.91.253.182) 22.263 ms adm-b2-link.telia.net (62.115.141.17) 21.979 ms 12 adm-b2-link.telia.net (80.91.253.182) 22.481 ms adm-b2-link.telia.net (62.115.141.9) 22.344 ms adm-b2-link.telia.net (62.115.141.63) 27.606 ms Colin > Begin forwarded message: > > From: RIPE Atlas (no reply) > Subject: Probe 2317 is down (home fibre) > Date: 21 June 2015 20:30:07 BST > To: colinj at mx5.org.uk > > Dear Dear colin johnston, > > Your probe 2317 has been disconnected since 2015-06-21 18:49:16 UTC. > > This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe becomes disconnected for more than 30 minutes. > > If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/probes/2317/, and click the "edit" button under "Notifications". > > Kind regards, > > RIPE Atlas Team > atlas at ripe.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From tom at hetmer.cz Sun Jun 21 21:57:40 2015 From: tom at hetmer.cz (=?iso-8859-2?B?VG9t4bkgSGV0bWVy?=) Date: Sun, 21 Jun 2015 21:57:40 +0200 Subject: [atlas] Fwd: Probe 2317 is down (home fibre) In-Reply-To: <09619879-9C86-4020-8156-9F06D9A1C6EA@mx5.org.uk> References: <20150621193007.16430.61386@janus.atlas.ripe.net>, <09619879-9C86-4020-8156-9F06D9A1C6EA@mx5.org.uk> Message-ID: Confirmed, I got the same email, ripe.net is down here (AS5610). ERR_CONNECTION_TIMED_OUT WINDOWS POWERSHELLCOPYRIGHT (C) 2014 MICROSOFT CORPORATION. ALL RIGHTS RESERVED. PS C:\USERS\TOM??> TRACERT ATLAS.RIPE.NET TRACING ROUTE TO ATLAS-UI.RIPE.NET [193.0.6.158]OVER A MAXIMUM OF 30 HOPS: 1 <1 MS <1 MS <1 MS 192.168.19.1 2 1 MS 1 MS 1 MS 10.55.0.1 3 4 MS 4 MS 4 MS 80.188.14.41 4 13 MS 10 MS 10 MS 80.74.43.1 5 14 MS 11 MS 13 MS 194.228.190.153 6 12 MS 10 MS 11 MS 194.228.190.193 7 * 9 MS 10 MS CESKY-1-0-0-0-100-GRTPRACH1.NET.TELEFONICAGLOBALSOLUTIONS.COM [5.53.0.25] 8 39 MS 39 MS 39 MS XE0-0-0-0-GRTPAREQ1.RED.TELEFONICA-WHOLESALE.NET [94.142.120.78] 9 30 MS 30 MS 30 MS PRS-B8-LINK.TELIA.NET [80.239.192.73] 10 30 MS 30 MS 30 MS PRS-BB2-LINK.TELIA.NET [62.115.138.138] 11 41 MS 42 MS 45 MS ADM-BB4-LINK.TELIA.NET [213.155.137.156] 12 43 MS 40 MS 41 MS ADM-B2-LINK.TELIA.NET [62.115.141.11] 13 * * RIPE-IC-300331-ADM-B4.C.TELIA.NET [62.115.12.202] REPORTS: DESTINATION NET UNREACHABLE. TRACE COMPLETE.PS C:\USERS\TOM??> Best regardsTom?? Hetmer From: colinj at mx5.org.uk Date: Sun, 21 Jun 2015 20:40:03 +0100 To: ripe-atlas at ripe.net; atlas at ripe.net Subject: [atlas] Fwd: Probe 2317 is down (home fibre) seems fine to me ? dont have connectivity to ripe site though from BT network range in uk what is telia upto ?Colins-iMac:~ colinj$ traceroute www.ripe.nettraceroute to www.ripe.net (193.0.6.139), 64 hops max, 52 byte packets 1 bthomehub (192.168.1.254) 1.913 ms 1.078 ms 1.078 ms 2 * * * 3 * * * 4 31.55.185.196 (31.55.185.196) 16.187 ms 15.477 ms 15.443 ms 5 195.99.127.142 (195.99.127.142) 15.557 ms 195.99.127.130 (195.99.127.130) 16.274 ms 195.99.127.128 (195.99.127.128) 16.602 ms 6 vhsaccess2-pos1-0.faraday.fixed.bt.net (195.99.127.9) 16.979 ms 16.611 ms 195.99.127.25 (195.99.127.25) 17.097 ms 7 166-49-211-240.eu.bt.net (166.49.211.240) 16.413 ms 166-49-211-236.eu.bt.net (166.49.211.236) 16.225 ms 166-49-211-238.eu.bt.net (166.49.211.238) 15.821 ms 8 213.248.82.249 (213.248.82.249) 16.880 ms 15.785 ms 15.470 ms 9 ldn-bb2-link.telia.net (62.115.137.194) 16.633 ms 213.248.82.249 (213.248.82.249) 15.631 ms 15.400 ms10 ldn-bb3-link.telia.net (80.91.248.90) 15.776 ms ldn-bb2-link.telia.net (213.155.136.62) 16.815 ms adm-bb4-link.telia.net (62.115.142.221) 22.936 ms11 adm-b2-link.telia.net (62.115.141.51) 25.759 ms adm-b2-link.telia.net (80.91.253.182) 22.263 ms adm-b2-link.telia.net (62.115.141.17) 21.979 ms12 adm-b2-link.telia.net (80.91.253.182) 22.481 ms adm-b2-link.telia.net (62.115.141.9) 22.344 ms adm-b2-link.telia.net (62.115.141.63) 27.606 ms Colin Begin forwarded message:From: RIPE Atlas (no reply) Subject: Probe 2317 is down (home fibre) Date: 21 June 2015 20:30:07 BST To: colinj at mx5.org.uk Dear Dear colin johnston, Your probe 2317 has been disconnected since 2015-06-21 18:49:16 UTC. This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe becomes disconnected for more than 30 minutes. If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/probes/2317/, and click the "edit" button under "Notifications". Kind regards, RIPE Atlas Team atlas at ripe.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From colinj at mx5.org.uk Sun Jun 21 22:18:15 2015 From: colinj at mx5.org.uk (Colin Johnston) Date: Sun, 21 Jun 2015 21:18:15 +0100 Subject: [atlas] Fwd: Probe 2317 is down (home fibre) In-Reply-To: References: <20150621193007.16430.61386@janus.atlas.ripe.net> <09619879-9C86-4020-8156-9F06D9A1C6EA@mx5.org.uk> Message-ID: now seems connected again :) hope all are having a nice summer sunday Colin > On 21 Jun 2015, at 20:57, Tom?? Hetmer wrote: > > Confirmed, I got the same email, ripe.net is down here (AS5610). > > ERR_CONNECTION_TIMED_OUT > > WINDOWS POWERSHELL > COPYRIGHT (C) 2014 MICROSOFT CORPORATION. ALL RIGHTS RESERVED. > > PS C:\USERS\TOM??> TRACERT ATLAS.RIPE.NET > > TRACING ROUTE TO ATLAS-UI.RIPE.NET [193.0.6.158] > OVER A MAXIMUM OF 30 HOPS: > > 1 <1 MS <1 MS <1 MS 192.168.19.1 > 2 1 MS 1 MS 1 MS 10.55.0.1 > 3 4 MS 4 MS 4 MS 80.188.14.41 > 4 13 MS 10 MS 10 MS 80.74.43.1 > 5 14 MS 11 MS 13 MS 194.228.190.153 > 6 12 MS 10 MS 11 MS 194.228.190.193 > 7 * 9 MS 10 MS CESKY-1-0-0-0-100-GRTPRACH1.NET.TELEFONICAGLOBALSOLUTIONS.COM [5.53.0.25] > 8 39 MS 39 MS 39 MS XE0-0-0-0-GRTPAREQ1.RED.TELEFONICA-WHOLESALE.NET [94.142.120.78] > 9 30 MS 30 MS 30 MS PRS-B8-LINK.TELIA.NET [80.239.192.73] > 10 30 MS 30 MS 30 MS PRS-BB2-LINK.TELIA.NET [62.115.138.138] > 11 41 MS 42 MS 45 MS ADM-BB4-LINK.TELIA.NET [213.155.137.156] > 12 43 MS 40 MS 41 MS ADM-B2-LINK.TELIA.NET [62.115.141.11] > 13 * * RIPE-IC-300331-ADM-B4.C.TELIA.NET [62.115.12.202] REPORTS: DESTINATION NET UNREACHABLE. > > TRACE COMPLETE. > PS C:\USERS\TOM??> > > Best regards > Tom?? Hetmer > > From: colinj at mx5.org.uk > Date: Sun, 21 Jun 2015 20:40:03 +0100 > To: ripe-atlas at ripe.net ; atlas at ripe.net > Subject: [atlas] Fwd: Probe 2317 is down (home fibre) > > seems fine to me ? > > dont have connectivity to ripe site though from BT network range in uk > > what is telia upto ? > Colins-iMac:~ colinj$ traceroute www.ripe.net > traceroute to www.ripe.net (193.0.6.139), 64 hops max, 52 byte packets > 1 bthomehub (192.168.1.254) 1.913 ms 1.078 ms 1.078 ms > 2 * * * > 3 * * * > 4 31.55.185.196 (31.55.185.196) 16.187 ms 15.477 ms 15.443 ms > 5 195.99.127.142 (195.99.127.142) 15.557 ms > 195.99.127.130 (195.99.127.130) 16.274 ms > 195.99.127.128 (195.99.127.128) 16.602 ms > 6 vhsaccess2-pos1-0.faraday.fixed.bt.net (195.99.127.9) 16.979 ms 16.611 ms > 195.99.127.25 (195.99.127.25) 17.097 ms > 7 166-49-211-240.eu.bt.net (166.49.211.240) 16.413 ms > 166-49-211-236.eu.bt.net (166.49.211.236) 16.225 ms > 166-49-211-238.eu.bt.net (166.49.211.238) 15.821 ms > 8 213.248.82.249 (213.248.82.249) 16.880 ms 15.785 ms 15.470 ms > 9 ldn-bb2-link.telia.net (62.115.137.194) 16.633 ms > 213.248.82.249 (213.248.82.249) 15.631 ms 15.400 ms > 10 ldn-bb3-link.telia.net (80.91.248.90) 15.776 ms > ldn-bb2-link.telia.net (213.155.136.62) 16.815 ms > adm-bb4-link.telia.net (62.115.142.221) 22.936 ms > 11 adm-b2-link.telia.net (62.115.141.51) 25.759 ms > adm-b2-link.telia.net (80.91.253.182) 22.263 ms > adm-b2-link.telia.net (62.115.141.17) 21.979 ms > 12 adm-b2-link.telia.net (80.91.253.182) 22.481 ms > adm-b2-link.telia.net (62.115.141.9) 22.344 ms > adm-b2-link.telia.net (62.115.141.63) 27.606 ms > > > Colin > > > Begin forwarded message: > > From: RIPE Atlas (no reply) > > Subject: Probe 2317 is down (home fibre) > Date: 21 June 2015 20:30:07 BST > To: colinj at mx5.org.uk > > Dear Dear colin johnston, > > Your probe 2317 has been disconnected since 2015-06-21 18:49:16 UTC. > > This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe becomes disconnected for more than 30 minutes. > > If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/probes/2317/ , and click the "edit" button under "Notifications". > > Kind regards, > > RIPE Atlas Team > atlas at ripe.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert at ripe.net Mon Jun 22 09:18:15 2015 From: robert at ripe.net (Robert Kisteleki) Date: Mon, 22 Jun 2015 09:18:15 +0200 Subject: [atlas] Fwd: Probe 2317 is down (home fibre) In-Reply-To: References: <20150621193007.16430.61386@janus.atlas.ripe.net> <09619879-9C86-4020-8156-9F06D9A1C6EA@mx5.org.uk> Message-ID: <5587B6B7.2040301@ripe.net> Hi, One of the NCC's border routers had a hardware issue around this time, which is the likely cause for this. Around 30% of the probes disconnected for a short while. Regards, Robert On 2015-06-21 22:18, Colin Johnston wrote: > now seems connected again :) > > hope all are having a nice summer sunday > > Colin > >> On 21 Jun 2015, at 20:57, Tom?? Hetmer > > wrote: >> >> Confirmed, I got the same email, ripe.net is down here >> (AS5610). >> >> ERR_CONNECTION_TIMED_OUT >> >> WINDOWS POWERSHELL >> COPYRIGHT (C) 2014 MICROSOFT CORPORATION. ALL RIGHTS RESERVED. >> >> PS C:\USERS\TOM??> TRACERT ATLAS.RIPE.NET >> >> TRACING ROUTE TO ATLAS-UI.RIPE.NET [193.0.6.158] >> OVER A MAXIMUM OF 30 HOPS: >> >> 1 <1 MS <1 MS <1 MS 192.168.19.1 >> 2 1 MS 1 MS 1 MS 10.55.0.1 >> 3 4 MS 4 MS 4 MS 80.188.14.41 >> 4 13 MS 10 MS 10 MS 80.74.43.1 >> 5 14 MS 11 MS 13 MS 194.228.190.153 >> 6 12 MS 10 MS 11 MS 194.228.190.193 >> 7 * 9 MS 10 MS >> CESKY-1-0-0-0-100-GRTPRACH1.NET.TELEFONICAGLOBALSOLUTIONS.COM >> [5.53.0.25] >> 8 39 MS 39 MS 39 MS >> XE0-0-0-0-GRTPAREQ1.RED.TELEFONICA-WHOLESALE.NET >> [94.142.120.78] >> 9 30 MS 30 MS 30 MS PRS-B8-LINK.TELIA.NET >> [80.239.192.73] >> 10 30 MS 30 MS 30 MS PRS-BB2-LINK.TELIA.NET >> [62.115.138.138] >> 11 41 MS 42 MS 45 MS ADM-BB4-LINK.TELIA.NET >> [213.155.137.156] >> 12 43 MS 40 MS 41 MS ADM-B2-LINK.TELIA.NET >> [62.115.141.11] >> 13 * * RIPE-IC-300331-ADM-B4.C.TELIA.NET >> [62.115.12.202] REPORTS: >> DESTINATION NET UNREACHABLE. >> >> TRACE COMPLETE. >> PS C:\USERS\TOM??> >> >> Best regards >> Tom?? Hetmer >> >> ---------------------------------------------------------------------------- >> From: colinj at mx5.org.uk >> Date: Sun, 21 Jun 2015 20:40:03 +0100 >> To: ripe-atlas at ripe.net ; atlas at ripe.net >> >> Subject: [atlas] Fwd: Probe 2317 is down (home fibre) >> >> seems fine to me ? >> >> dont have connectivity to ripe site though from BT network range in uk >> >> what is telia upto ? >> Colins-iMac:~ colinj$ traceroute www.ripe.net >> traceroute to www.ripe.net (193.0.6.139), 64 hops >> max, 52 byte packets >> 1 bthomehub (192.168.1.254) 1.913 ms 1.078 ms 1.078 ms >> 2 * * * >> 3 * * * >> 4 31.55.185.196 (31.55.185.196) 16.187 ms 15.477 ms 15.443 ms >> 5 195.99.127.142 (195.99.127.142) 15.557 ms >> 195.99.127.130 (195.99.127.130) 16.274 ms >> 195.99.127.128 (195.99.127.128) 16.602 ms >> 6 vhsaccess2-pos1-0.faraday.fixed.bt.net >> (195.99.127.9) 16.979 >> ms 16.611 ms >> 195.99.127.25 (195.99.127.25) 17.097 ms >> 7 166-49-211-240.eu.bt.net >> (166.49.211.240) 16.413 ms >> 166-49-211-236.eu.bt.net >> (166.49.211.236) 16.225 ms >> 166-49-211-238.eu.bt.net >> (166.49.211.238) 15.821 ms >> 8 213.248.82.249 (213.248.82.249) 16.880 ms 15.785 ms 15.470 ms >> 9 ldn-bb2-link.telia.net >> (62.115.137.194) 16.633 ms >> 213.248.82.249 (213.248.82.249) 15.631 ms 15.400 ms >> 10 ldn-bb3-link.telia.net >> (80.91.248.90) 15.776 ms >> ldn-bb2-link.telia.net >> (213.155.136.62) 16.815 ms >> adm-bb4-link.telia.net >> (62.115.142.221) 22.936 ms >> 11 adm-b2-link.telia.net (62.115.141.51) >> 25.759 ms >> adm-b2-link.telia.net (80.91.253.182) >> 22.263 ms >> adm-b2-link.telia.net (62.115.141.17) >> 21.979 ms >> 12 adm-b2-link.telia.net (80.91.253.182) >> 22.481 ms >> adm-b2-link.telia.net (62.115.141.9) >> 22.344 ms >> adm-b2-link.telia.net (62.115.141.63) >> 27.606 ms >> >> >> Colin >> >> >> Begin forwarded message: >> >> *From: *RIPE Atlas (no reply) > > >> *Subject: **Probe 2317 is down (home fibre)* >> *Date: *21 June 2015 20:30:07 BST >> *To: *colinj at mx5.org.uk >> >> Dear Dear colin johnston, >> >> Your probe 2317 has been disconnected since 2015-06-21 18:49:16 UTC. >> >> This is an automatically generated email from RIPE Atlas. It was sent >> to you because you asked to be notified if your probe becomes >> disconnected for more than 30 minutes. >> >> If you want to change this, or disable this notification altogether, >> please go to https://atlas.ripe.net/probes/2317/, and click the "edit" >> button under "Notifications". >> >> Kind regards, >> >> RIPE Atlas Team >> atlas at ripe.net > From colinj at mx5.org.uk Mon Jun 22 09:20:10 2015 From: colinj at mx5.org.uk (Colin Johnston) Date: Mon, 22 Jun 2015 08:20:10 +0100 Subject: [atlas] Fwd: Probe 2317 is down (home fibre) In-Reply-To: <5587B6B7.2040301@ripe.net> References: <20150621193007.16430.61386@janus.atlas.ripe.net> <09619879-9C86-4020-8156-9F06D9A1C6EA@mx5.org.uk> <5587B6B7.2040301@ripe.net> Message-ID: <137DCAD9-A0D8-4BAF-BA19-EE6A79B92BC8@mx5.org.uk> Thanks Robert, does explain what happened, Hopefully ripe atlas added to the info to help debug. Seems border routers did not failover ? Colin > On 22 Jun 2015, at 08:18, Robert Kisteleki wrote: > > Hi, > > One of the NCC's border routers had a hardware issue around this time, which > is the likely cause for this. Around 30% of the probes disconnected for a > short while. > > Regards, > Robert > > > On 2015-06-21 22:18, Colin Johnston wrote: >> now seems connected again :) >> >> hope all are having a nice summer sunday >> >> Colin >> >>> On 21 Jun 2015, at 20:57, Tom?? Hetmer >> > wrote: >>> >>> Confirmed, I got the same email, ripe.net is down here >>> (AS5610). >>> >>> ERR_CONNECTION_TIMED_OUT >>> >>> WINDOWS POWERSHELL >>> COPYRIGHT (C) 2014 MICROSOFT CORPORATION. ALL RIGHTS RESERVED. >>> >>> PS C:\USERS\TOM??> TRACERT ATLAS.RIPE.NET >>> >>> TRACING ROUTE TO ATLAS-UI.RIPE.NET [193.0.6.158] >>> OVER A MAXIMUM OF 30 HOPS: >>> >>> 1 <1 MS <1 MS <1 MS 192.168.19.1 >>> 2 1 MS 1 MS 1 MS 10.55.0.1 >>> 3 4 MS 4 MS 4 MS 80.188.14.41 >>> 4 13 MS 10 MS 10 MS 80.74.43.1 >>> 5 14 MS 11 MS 13 MS 194.228.190.153 >>> 6 12 MS 10 MS 11 MS 194.228.190.193 >>> 7 * 9 MS 10 MS >>> CESKY-1-0-0-0-100-GRTPRACH1.NET.TELEFONICAGLOBALSOLUTIONS.COM >>> [5.53.0.25] >>> 8 39 MS 39 MS 39 MS >>> XE0-0-0-0-GRTPAREQ1.RED.TELEFONICA-WHOLESALE.NET >>> [94.142.120.78] >>> 9 30 MS 30 MS 30 MS PRS-B8-LINK.TELIA.NET >>> [80.239.192.73] >>> 10 30 MS 30 MS 30 MS PRS-BB2-LINK.TELIA.NET >>> [62.115.138.138] >>> 11 41 MS 42 MS 45 MS ADM-BB4-LINK.TELIA.NET >>> [213.155.137.156] >>> 12 43 MS 40 MS 41 MS ADM-B2-LINK.TELIA.NET >>> [62.115.141.11] >>> 13 * * RIPE-IC-300331-ADM-B4.C.TELIA.NET >>> [62.115.12.202] REPORTS: >>> DESTINATION NET UNREACHABLE. >>> >>> TRACE COMPLETE. >>> PS C:\USERS\TOM??> >>> >>> Best regards >>> Tom?? Hetmer >>> >>> ---------------------------------------------------------------------------- >>> From: colinj at mx5.org.uk >>> Date: Sun, 21 Jun 2015 20:40:03 +0100 >>> To: ripe-atlas at ripe.net ; atlas at ripe.net >>> >>> Subject: [atlas] Fwd: Probe 2317 is down (home fibre) >>> >>> seems fine to me ? >>> >>> dont have connectivity to ripe site though from BT network range in uk >>> >>> what is telia upto ? >>> Colins-iMac:~ colinj$ traceroute www.ripe.net >>> traceroute to www.ripe.net (193.0.6.139), 64 hops >>> max, 52 byte packets >>> 1 bthomehub (192.168.1.254) 1.913 ms 1.078 ms 1.078 ms >>> 2 * * * >>> 3 * * * >>> 4 31.55.185.196 (31.55.185.196) 16.187 ms 15.477 ms 15.443 ms >>> 5 195.99.127.142 (195.99.127.142) 15.557 ms >>> 195.99.127.130 (195.99.127.130) 16.274 ms >>> 195.99.127.128 (195.99.127.128) 16.602 ms >>> 6 vhsaccess2-pos1-0.faraday.fixed.bt.net >>> (195.99.127.9) 16.979 >>> ms 16.611 ms >>> 195.99.127.25 (195.99.127.25) 17.097 ms >>> 7 166-49-211-240.eu.bt.net >>> (166.49.211.240) 16.413 ms >>> 166-49-211-236.eu.bt.net >>> (166.49.211.236) 16.225 ms >>> 166-49-211-238.eu.bt.net >>> (166.49.211.238) 15.821 ms >>> 8 213.248.82.249 (213.248.82.249) 16.880 ms 15.785 ms 15.470 ms >>> 9 ldn-bb2-link.telia.net >>> (62.115.137.194) 16.633 ms >>> 213.248.82.249 (213.248.82.249) 15.631 ms 15.400 ms >>> 10 ldn-bb3-link.telia.net >>> (80.91.248.90) 15.776 ms >>> ldn-bb2-link.telia.net >>> (213.155.136.62) 16.815 ms >>> adm-bb4-link.telia.net >>> (62.115.142.221) 22.936 ms >>> 11 adm-b2-link.telia.net (62.115.141.51) >>> 25.759 ms >>> adm-b2-link.telia.net (80.91.253.182) >>> 22.263 ms >>> adm-b2-link.telia.net (62.115.141.17) >>> 21.979 ms >>> 12 adm-b2-link.telia.net (80.91.253.182) >>> 22.481 ms >>> adm-b2-link.telia.net (62.115.141.9) >>> 22.344 ms >>> adm-b2-link.telia.net (62.115.141.63) >>> 27.606 ms >>> >>> >>> Colin >>> >>> >>> Begin forwarded message: >>> >>> *From: *RIPE Atlas (no reply) >> > >>> *Subject: **Probe 2317 is down (home fibre)* >>> *Date: *21 June 2015 20:30:07 BST >>> *To: *colinj at mx5.org.uk >>> >>> Dear Dear colin johnston, >>> >>> Your probe 2317 has been disconnected since 2015-06-21 18:49:16 UTC. >>> >>> This is an automatically generated email from RIPE Atlas. It was sent >>> to you because you asked to be notified if your probe becomes >>> disconnected for more than 30 minutes. >>> >>> If you want to change this, or disable this notification altogether, >>> please go to https://atlas.ripe.net/probes/2317/, and click the "edit" >>> button under "Notifications". >>> >>> Kind regards, >>> >>> RIPE Atlas Team >>> atlas at ripe.net >> From jzp-ripe at rsuc.gweep.net Mon Jun 22 14:34:52 2015 From: jzp-ripe at rsuc.gweep.net (Joe Provo) Date: Mon, 22 Jun 2015 08:34:52 -0400 Subject: [atlas] Fwd: Probe 2317 is down (home fibre) In-Reply-To: <137DCAD9-A0D8-4BAF-BA19-EE6A79B92BC8@mx5.org.uk> References: <20150621193007.16430.61386@janus.atlas.ripe.net> <09619879-9C86-4020-8156-9F06D9A1C6EA@mx5.org.uk> <5587B6B7.2040301@ripe.net> <137DCAD9-A0D8-4BAF-BA19-EE6A79B92BC8@mx5.org.uk> Message-ID: <20150622123452.GA16433@gweep.net> On Mon, Jun 22, 2015 at 08:20:10AM +0100, Colin Johnston wrote: > Thanks Robert, does explain what happened, > Hopefully ripe atlas added to the info to help debug. > Seems border routers did not failover ? I expect we'll see a blog post on the failure impact. Note that 'hardware issue' can cover a broad range of things, so it might have been blackholing traffic, etc. Cheers! Joe -- RSUC / GweepNet / Spunk / FnB / CotSG / Usenix / NANOG From colinj at gt86car.org.uk Mon Jun 22 15:03:52 2015 From: colinj at gt86car.org.uk (Colin Johnston) Date: Mon, 22 Jun 2015 14:03:52 +0100 Subject: [atlas] vm image for ripe atlas probe ? Message-ID: any news on vm image for ripe atlas probe ? would be great to use as could monitor vm farms much better ? Colin. From budiwijaya at ipv6.or.id Mon Jun 22 16:37:17 2015 From: budiwijaya at ipv6.or.id (Budiwijaya) Date: Mon, 22 Jun 2015 21:37:17 +0700 Subject: [atlas] vm image for ripe atlas probe ? In-Reply-To: References: Message-ID: I definitely would give it a try! Thank you Budiwijaya On Mon, Jun 22, 2015 at 8:03 PM, Colin Johnston wrote: > any news on vm image for ripe atlas probe ? > would be great to use as could monitor vm farms much better ? > > Colin. > > From mathias at houngbo.net Mon Jun 22 16:43:05 2015 From: mathias at houngbo.net (Mathias HOUNGBO) Date: Mon, 22 Jun 2015 15:43:05 +0100 Subject: [atlas] vm image for ripe atlas probe ? In-Reply-To: References: Message-ID: <55881EF9.6060101@houngbo.net> +1 Le 22/06/2015 14:03, Colin Johnston a ?crit : > any news on vm image for ripe atlas probe ? > would be great to use as could monitor vm farms much better ? > > Colin. > > Open source is not limited to software and it is not limited to english either! Mefies toi de la m?diocrit?, c'est la moisissure de l'esprit -- Made in B?nin - http://mathias.houngbo.net Pr?sident ONG IGBANet - http://www.igbanet.org/ System and Network Administrator at BCEAO B?nin CTO & Co-Founder at STARSOFT INFORMATIQUE -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From matteo at bonora.eu Mon Jun 22 22:17:17 2015 From: matteo at bonora.eu (Matteo Bonora) Date: Mon, 22 Jun 2015 22:17:17 +0200 Subject: [atlas] vm image for ripe atlas probe ? In-Reply-To: <55881EF9.6060101@houngbo.net> References: <55881EF9.6060101@houngbo.net> Message-ID: I'm interested as well! +1 -- | *Matteo Bonora* On Mon, Jun 22, 2015 at 4:43 PM, Mathias HOUNGBO wrote: > +1 > > Le 22/06/2015 14:03, Colin Johnston a ?crit : > > any news on vm image for ripe atlas probe ? > > would be great to use as could monitor vm farms much better ? > > > > Colin. > > > > > > Open source is not limited to software and it is not limited to english > either! > Mefies toi de la m?diocrit?, c'est la moisissure de l'esprit > > -- > Made in B?nin - http://mathias.houngbo.net > Pr?sident ONG IGBANet - http://www.igbanet.org/ > System and Network Administrator at BCEAO B?nin > CTO & Co-Founder at STARSOFT INFORMATIQUE > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From laurent.dumont at coldnorthadmin.com Tue Jun 23 00:37:48 2015 From: laurent.dumont at coldnorthadmin.com (Laurent Dumont) Date: Mon, 22 Jun 2015 18:37:48 -0400 Subject: [atlas] Probe question - Issue Message-ID: <55888E3C.6050001@coldnorthadmin.com> Hi gents, After some delay, I'm trying to setup the probe I received. Unfortunately, it seems that something is not quite working. Once it's plugged in and powered, there is no activity. There is no DHCP request for the probe so I can't see anything on the network side. Could something be wrong with the usb key? Is there a way I could reflash the usb key with the OS files? Thanks Laurent Dumont -- Laurent Dumont coldnorthadmin.com From daniel.karrenberg at ripe.net Tue Jun 23 08:38:49 2015 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Tue, 23 Jun 2015 08:38:49 +0200 Subject: [atlas] Probe question - Issue In-Reply-To: <55888E3C.6050001@coldnorthadmin.com> References: <55888E3C.6050001@coldnorthadmin.com> Message-ID: <5588FEF9.7080405@ripe.net> Hi Laurent, while I am not in charge of customer support .... I can tell you that the USB Flash only stores results, the OS is on the internal flash and that the most common problem is insufficient or unstable USB power to the unit. I hope this helps until the pros arrive at the office. Daniel On 23.06.15 0:37 , Laurent Dumont wrote: > Hi gents, > > After some delay, I'm trying to setup the probe I received. > Unfortunately, it seems that something is not quite working. Once it's > plugged in and powered, there is no activity. There is no DHCP request > for the probe so I can't see anything on the network side. > > Could something be wrong with the usb key? Is there a way I could > reflash the usb key with the OS files? > > Thanks > > Laurent Dumont > From philip.homburg at ripe.net Tue Jun 23 12:24:17 2015 From: philip.homburg at ripe.net (Philip Homburg) Date: Tue, 23 Jun 2015 12:24:17 +0200 Subject: [atlas] Probe question - Issue In-Reply-To: <5588FEF9.7080405@ripe.net> References: <55888E3C.6050001@coldnorthadmin.com> <5588FEF9.7080405@ripe.net> Message-ID: <558933D1.4080104@ripe.net> On 2015/06/23 8:38 , Daniel Karrenberg wrote: > I can tell you that the USB Flash only stores results, the OS is on the > internal flash > > and that the most common problem is insufficient or unstable USB power > to the unit. > > I hope this helps until the pros arrive at the office. Hi, It is a bit more complex than that. The internal flash is not big enough to contain all programs needed by the probe. So what we did was to move the main Atlas code to the USB stick and put the code for booting (including the kernel) and flashing the USB stick on the internal flash. If the probe is running from internal flash than the LED next to the power LED is blinking. If the probe is running from the USB stick then LEDs 3 and 4 (counting the power LED as 1) are blinking or solid. Philip From elane at ripe.net Tue Jun 23 13:42:06 2015 From: elane at ripe.net (Eamonn Lane) Date: Tue, 23 Jun 2015 13:42:06 +0200 Subject: [atlas] FHE3 Gmbh, Frankfurt Am Main, Germany has joined RIPE Atlas anchors Message-ID: Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called de-fra-as49024 and is hosted by FHE3 Gmbh, Frankfurt Am Main, Germany. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, RIPE Atlas Team RIPE NCC atlas at ripe.net -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2598 bytes Desc: not available URL: From elane at ripe.net Tue Jun 23 13:47:03 2015 From: elane at ripe.net (Eamonn Lane) Date: Tue, 23 Jun 2015 13:47:03 +0200 Subject: [atlas] Netzwerge Hamburg eK, Hamburg, Germany has joined RIPE Atlas anchors Message-ID: <08C56442-C71E-4B4B-97F4-7939F6F5BE76@ripe.net> Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called de-ham-as201709 and is hosted by Netzwerge Hamburg eK, Hamburg, Germany. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, RIPE Atlas Team RIPE NCC atlas at ripe.net -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2598 bytes Desc: not available URL: From daniel.karrenberg at ripe.net Tue Jun 23 14:06:16 2015 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Tue, 23 Jun 2015 14:06:16 +0200 Subject: [atlas] Probe question - Issue In-Reply-To: <558933D1.4080104@ripe.net> References: <55888E3C.6050001@coldnorthadmin.com> <5588FEF9.7080405@ripe.net> <558933D1.4080104@ripe.net> Message-ID: <55894BB8.6040607@ripe.net> Ah, nobody tells me anything anymore around here ;-). So does this mean you can no longer just change the USB stick anymore like you used to? Daniel On 23.06.15 12:24 , Philip Homburg wrote: > On 2015/06/23 8:38 , Daniel Karrenberg wrote: >> I can tell you that the USB Flash only stores results, the OS is on the >> internal flash >> >> and that the most common problem is insufficient or unstable USB power >> to the unit. >> >> I hope this helps until the pros arrive at the office. > > Hi, > > It is a bit more complex than that. The internal flash is not big enough > to contain all programs needed by the probe. So what we did was to move > the main Atlas code to the USB stick and put the code for booting > (including the kernel) and flashing the USB stick on the internal flash. > > If the probe is running from internal flash than the LED next to the > power LED is blinking. If the probe is running from the USB stick then > LEDs 3 and 4 (counting the power LED as 1) are blinking or solid. > > Philip > > From philip.homburg at ripe.net Tue Jun 23 14:16:34 2015 From: philip.homburg at ripe.net (Philip Homburg) Date: Tue, 23 Jun 2015 14:16:34 +0200 Subject: [atlas] Probe question - Issue In-Reply-To: <55894BB8.6040607@ripe.net> References: <55888E3C.6050001@coldnorthadmin.com> <5588FEF9.7080405@ripe.net> <558933D1.4080104@ripe.net> <55894BB8.6040607@ripe.net> Message-ID: <55894E22.2060706@ripe.net> On 2015/06/23 14:06 , Daniel Karrenberg wrote: > Ah, nobody tells me anything anymore around here ;-). > So does this mean you can no longer just change the USB stick anymore > like you used to? This behavior is unchanged since the v3 probes were first introduced. Assuming no static network configuration, you can just plug in an empty USB stick. The code on the internal flash will fetch a copy of the Atlas firmware from the controller, write it to the USB stick and reboot to start running from the USB stick. Philip From laurent.dumont at coldnorthadmin.com Tue Jun 23 19:52:50 2015 From: laurent.dumont at coldnorthadmin.com (Laurent Dumont) Date: Tue, 23 Jun 2015 13:52:50 -0400 Subject: [atlas] Probe update Message-ID: <55899CF2.6050907@coldnorthadmin.com> Hi gents, Small update on the probe status. I've tried a 2A usb power adapter and no dice. The Power and WPS led come on and a ethernet link seems to be active between the probe and the switch. Unfortunately, there is no DHCP discover or any kind of network activity from the probe. Anything else I can try to troubleshoot this? Is there a LED guide somewhere? -- Laurent Dumont coldnorthadmin.com From matteo at bonora.eu Tue Jun 23 20:05:05 2015 From: matteo at bonora.eu (Matteo Bonora) Date: Tue, 23 Jun 2015 20:05:05 +0200 Subject: [atlas] Probe update In-Reply-To: <55899CF2.6050907@coldnorthadmin.com> References: <55899CF2.6050907@coldnorthadmin.com> Message-ID: Hi, when I had problems with my probe I was been able to fix them leaving the probe powered and connected to the network without the USB stick for at least 10 minutes and then plugging in the USB stick. At this point the probe should start formatting the USB stick and reinstalling the Atlas software, hopefully solving your issues. You can find an info table about the LEDs at this page: https://atlas.ripe.net/about/faq/ I hope this is useful. Matteo On Tue, Jun 23, 2015 at 7:52 PM, Laurent Dumont < laurent.dumont at coldnorthadmin.com> wrote: > Hi gents, > > Small update on the probe status. > > I've tried a 2A usb power adapter and no dice. The Power and WPS led come > on and a ethernet link seems to be active between the probe and the switch. > Unfortunately, there is no DHCP discover or any kind of network activity > from the probe. Anything else I can try to troubleshoot this? > > Is there a LED guide somewhere? > > -- > Laurent Dumont > coldnorthadmin.com > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.ohara at bomboratech.com.au Thu Jun 25 02:12:35 2015 From: ben.ohara at bomboratech.com.au (Ben O'Hara) Date: Thu, 25 Jun 2015 00:12:35 +0000 Subject: [atlas] Active probes Message-ID: <16472540-E7A1-4400-9C75-4A78F6A2C6AA@bomboratech.com.au> Hi, We currently pull https://atlas.ripe.net/contrib/active_probes.json as part of some analysis of atlas data, this seems to have gone missing since yesterday and now returns a 404. Is this known? Should it work? Will it come back? Cheers Ben BEN O'HARA Senior Network and Systems Engineer P +61 9866 3710 [Bombora Technologies Logo] www.bomboratech.com.au Follow us on Twitter The Bombora Technologies group of companies includes AusRegistry, ARI Registry Services, AusRegistry International and ZOAK Solutions. The information contained in this communication is intended for the named recipients only. It is subject to copyright and may contain legally privileged and confidential information and if you are not an intended recipient you must not use, copy, distribute or take any action in reliance on it. If you have received this communication in error, please delete all copies from your system and notify us immediately. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: imagea1dc27.PNG Type: image/png Size: 29012 bytes Desc: imagea1dc27.PNG URL: From robert at ripe.net Thu Jun 25 14:33:05 2015 From: robert at ripe.net (Robert Kisteleki) Date: Thu, 25 Jun 2015 14:33:05 +0200 Subject: [atlas] Active probes In-Reply-To: <16472540-E7A1-4400-9C75-4A78F6A2C6AA@bomboratech.com.au> References: <16472540-E7A1-4400-9C75-4A78F6A2C6AA@bomboratech.com.au> Message-ID: <558BF501.3020407@ripe.net> On 2015-06-25 2:12, Ben O'Hara wrote: > Hi, > > We currently pull https://atlas.ripe.net/contrib/active_probes.json as part > of some analysis of atlas data, this seems to have gone missing since > yesterday and now returns a 404. > > Is this known? Should it work? Will it come back? > > Cheers > > Ben Hello, The above URL is/was an internal one to supply data to the UI -- for public consumption we have the APIs. It'd be useful to know what information you are after; depending on that, the probe API or the probe archive API is the way to go. Cheers, Robert From ben.ohara at bomboratech.com.au Thu Jun 25 16:36:06 2015 From: ben.ohara at bomboratech.com.au (Ben O'Hara) Date: Thu, 25 Jun 2015 14:36:06 +0000 Subject: [atlas] Active probes In-Reply-To: <558BF501.3020407@ripe.net> References: <16472540-E7A1-4400-9C75-4A78F6A2C6AA@bomboratech.com.au> <558BF501.3020407@ripe.net> Message-ID: Cheers Robert, I saw its 'contrib', buts its littered in code over github. I just use it to pass geo location ips and asn for a list of probes from measurements im doing about anycast. Pretty sure I can replicate in the api, I'll have a look. Ben On 25/06/2015 22:33, "Robert Kisteleki" wrote: > >On 2015-06-25 2:12, Ben O'Hara wrote: >> Hi, >> >> We currently pull https://atlas.ripe.net/contrib/active_probes.json as part >> of some analysis of atlas data, this seems to have gone missing since >> yesterday and now returns a 404. >> >> Is this known? Should it work? Will it come back? >> >> Cheers >> >> Ben > >Hello, > >The above URL is/was an internal one to supply data to the UI -- for public >consumption we have the APIs. It'd be useful to know what information you >are after; depending on that, the probe API or the probe archive API is the >way to go. > >Cheers, >Robert BEN O'HARA Senior Network and Systems Engineer P +61 9866 3710 www.bomboratech.com.au Follow us on https://twitter.com/BomboraTech The Bombora Technologies group of companies includes AusRegistry, ARI Registry Services, AusRegistry International and ZOAK Solutions. The information contained in this communication is intended for the named recipients only. It is subject to copyright and may contain legally privileged and confidential information and if you are not an intended recipient you must not use, copy, distribute or take any action in reliance on it. If you have received this communication in error, please delete all copies from your system and notify us immediately. From robert at ripe.net Tue Jun 30 12:20:53 2015 From: robert at ripe.net (Robert Kisteleki) Date: Tue, 30 Jun 2015 12:20:53 +0200 Subject: [atlas] vm image for ripe atlas probe ? In-Reply-To: References: Message-ID: <55926D85.5030808@ripe.net> On 2015-06-22 15:03, Colin Johnston wrote: > any news on vm image for ripe atlas probe ? > would be great to use as could monitor vm farms much better ? > > Colin. Dear all, We understand that some people asked for this feature. At the moment we're evaluating it, and plan to come back to the community with a plan of action before the end of August. It's possible that we'll post a couple of clarification questions in the meantime. Regards, Robert From mgalante at ripe.net Tue Jun 30 14:28:50 2015 From: mgalante at ripe.net (Michela Galante) Date: Tue, 30 Jun 2015 14:28:50 +0200 Subject: [atlas] DHIRAAGU (Maldives) has joined RIPE Atlas anchors Message-ID: <37B45CF0-193B-4F23-AC41-1C5C0DD14ECB@ripe.net> Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called mv-mle-as7642 and it is hosted by DHIRAAGU in Male, Maldives, and sponsored by APNIC. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team atlas at ripe.net -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2612 bytes Desc: not available URL: From colinj at gt86car.org.uk Tue Jun 30 14:07:59 2015 From: colinj at gt86car.org.uk (Colin Johnston) Date: Tue, 30 Jun 2015 13:07:59 +0100 Subject: [atlas] vm image for ripe atlas probe ? In-Reply-To: <55926C55.8060303@ripe.net> References: <55926C55.8060303@ripe.net> Message-ID: low vm disk use is priority low vm memory is priority colin Sent from my iPhone > On 30 Jun 2015, at 11:15, RIPE Atlas wrote: > >> On 2015-06-22 15:03, Colin Johnston wrote: >> any news on vm image for ripe atlas probe ? >> would be great to use as could monitor vm farms much better ? >> >> Colin. > > Dear all, > > We understand that some people asked for this feature. At the moment we're > evaluating it, and plan to come back to the community with a plan of action > before the end of August. It's possible that we'll post a couple of > clarification questions in the meantime. > > Regards, > Robert