From mgalante at ripe.net Mon Dec 1 11:26:05 2014 From: mgalante at ripe.net (Michela Galante) Date: Mon, 1 Dec 2014 11:26:05 +0100 Subject: [atlas] Wikimedia Foundation (San Francisco, US) has joined RIPE Atlas anchors Message-ID: <0CE54AA8-0748-4CA0-8A83-D77E4092B618@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 us-sfo-as14907 and it is hosted by Wikimedia Foundation in San Francisco, United States. Congratulations to Wikimedia Foundation for their third anchor online! 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2612 bytes Desc: not available URL: From modonovan at btireland.net Mon Dec 1 12:36:36 2014 From: modonovan at btireland.net (Mick O'Donovan) Date: Mon, 01 Dec 2014 11:36:36 +0000 Subject: [atlas] Many thanks :) In-Reply-To: <201411292219280835.008F4CEA@smtp.24cl.home> References: <201411292219280835.008F4CEA@smtp.24cl.home> Message-ID: <547C52C4.3030502@btireland.net> +1 to that... I've done similar too many times after home LAN maintenance.... On 30/11/2014 03:19, Mike. wrote: > A short note to say 'thank-you' for the ability to configure the > origination of an email message when the probe under my supervision > has been offline for a short while. > > I was doing some work on my firewall today, and I neglected to > re-plug the probe back into the USB port for power. > > The email informed me of my transgression. :) > > Mike. > > From colinj at mx5.org.uk Mon Dec 1 12:59:01 2014 From: colinj at mx5.org.uk (Colin Johnston) Date: Mon, 1 Dec 2014 11:59:01 +0000 Subject: [atlas] Many thanks :) In-Reply-To: <547C52C4.3030502@btireland.net> References: <201411292219280835.008F4CEA@smtp.24cl.home> <547C52C4.3030502@btireland.net> Message-ID: <80EAA2CF-26C1-4481-851F-65488EE60682@mx5.org.uk> yes i found useful as well pluged into backup lan by mistake.. colin Sent from my iPhone > On 1 Dec 2014, at 11:36, Mick O'Donovan wrote: > > +1 to that... I've done similar too many times after home LAN maintenance.... > > >> On 30/11/2014 03:19, Mike. wrote: >> A short note to say 'thank-you' for the ability to configure the >> origination of an email message when the probe under my supervision >> has been offline for a short while. >> >> I was doing some work on my firewall today, and I neglected to >> re-plug the probe back into the USB port for power. >> >> The email informed me of my transgression. :) >> >> Mike. > > From mgalante at ripe.net Wed Dec 3 13:29:14 2014 From: mgalante at ripe.net (Michela Galante) Date: Wed, 3 Dec 2014 13:29:14 +0100 Subject: [atlas] openmirrors.asia (SG) has joined RIPE Atlas anchors Message-ID: <5D8DFAE3-2BAC-494F-9EBD-51903500497A@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 sg-sin-as45494 and it is hosted by openmirrors.asia in Singapore City, Singapore, 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 astracha at ripe.net Thu Dec 4 09:41:58 2014 From: astracha at ripe.net (Alastair Strachan) Date: Thu, 4 Dec 2014 09:41:58 +0100 Subject: [atlas] Liquid Web Inc. (Lansing Charter Township, US) 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 us-lan-as32244 and it is hosted by Liquid Web Inc in Lansing Charter Township, United States. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jared at puck.nether.net Fri Dec 5 13:31:19 2014 From: jared at puck.nether.net (Jared Mauch) Date: Fri, 5 Dec 2014 07:31:19 -0500 Subject: [atlas] Credits In-Reply-To: References: <28FF9195-3DC2-45BF-8D01-EAAA33232DBF@puck.nether.net> Message-ID: <5C44BD9A-8280-434F-BCD7-8FFFB1BC1746@puck.nether.net> I have ~60 million credits that I would be willing to share with those who need some. - Jared > On Nov 29, 2014, at 2:37 AM, Shahin Gharghi wrote: > > Thank you Jared > > I actually have 10 Million credits. That was just a suggestion. > > On Fri, Nov 28, 2014 at 3:41 PM, Jared Mauch wrote: > Do you need credits? Happy to share some that I have. > > Jared Mauch > > On Nov 26, 2014, at 9:17 AM, Shahin Gharghi wrote: > >> Hi >> The RIPE Atlas hosts earn credit for the time their probes remain connected. I think it could be better to receive additional credit whenever someone uses that probe to make measurement. >> And if crowded probes be more expensive, we can distribute the load between same probes better. >> >> -- >> Shahin Gharghi > > > > -- > Shahin Gharghi From florian at inet.tu-berlin.de Fri Dec 5 15:11:40 2014 From: florian at inet.tu-berlin.de (Florian Streibelt) Date: Fri, 05 Dec 2014 15:11:40 +0100 Subject: [atlas] Dead Atlas Probe (TP-Link) Message-ID: <5481BD1C.5070104@inet.tu-berlin.de> Hi, I got a probe returned that was not able to connect to the Atlas network. The probe was doint nothing for 2 days, only the leftmost LED (Power) was on, nothing else seems to happen. I also had to learn, that after the probe was not working, the user cleared the USB-Stick. Is there a way to resurrect the probe? Also the probe should be re-added to my ambassador account, if possible. Greetings, Florian -- Florian Streibelt, Dipl.-Inf. building MAR, 4th floor, room 4.004 Fachgebiet INET - Sekr. MAR 4-4 phone: +49 30 314 757 33 Technische Universit?t Berlin gpg-fp: 5BE7 F008 8B83 9357 1108 Marchstrasse 23 - 10587 Berlin 984A 3B8E A41F 82F6 1240 From remaker at gmail.com Mon Dec 8 10:37:08 2014 From: remaker at gmail.com (Phillip Remaker) Date: Mon, 8 Dec 2014 10:37:08 +0100 Subject: [atlas] Dead Atlas Probe (TP-Link) In-Reply-To: <5481BD1C.5070104@inet.tu-berlin.de> References: <5481BD1C.5070104@inet.tu-berlin.de> Message-ID: I have found that the Sandisk USB disks will fail, especially under low voltage conditions (underpowered adapter, for example). Alistair gave me instructions when mine failed. - Power off the RIPE Atlas Probe - Remove the USB stick - Power on the tp-link and connect it to the network - Wait for 5 minutes - Insert the USB stick while the RIPE Atlas Probe is powered. If that doesn't work, try a new 4GB USB drive instead. SanDisk was good about replacing the failed USB drive, but I think I'd use a different brand than can tolerate lower power. On Fri, Dec 5, 2014 at 3:11 PM, Florian Streibelt wrote: > Hi, > > I got a probe returned that was not able to connect to the Atlas > network. The probe was doint nothing for 2 days, only the leftmost LED > (Power) was on, nothing else seems to happen. > > I also had to learn, that after the probe was not working, the user > cleared the USB-Stick. > > Is there a way to resurrect the probe? Also the probe should be re-added > to my ambassador account, if possible. > > Greetings, > Florian > > -- > Florian Streibelt, Dipl.-Inf. building MAR, 4th floor, room 4.004 > Fachgebiet INET - Sekr. MAR 4-4 phone: +49 30 314 757 33 > Technische Universit?t Berlin gpg-fp: 5BE7 F008 8B83 9357 1108 > Marchstrasse 23 - 10587 Berlin 984A 3B8E A41F 82F6 1240 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From philip.homburg at ripe.net Mon Dec 8 12:00:24 2014 From: philip.homburg at ripe.net (Philip Homburg) Date: Mon, 08 Dec 2014 12:00:24 +0100 Subject: [atlas] Dead Atlas Probe (TP-Link) In-Reply-To: <5481BD1C.5070104@inet.tu-berlin.de> References: <5481BD1C.5070104@inet.tu-berlin.de> Message-ID: <548584C8.1030604@ripe.net> Hi Florian, > I got a probe returned that was not able to connect to the Atlas > network. The probe was doint nothing for 2 days, only the leftmost LED > (Power) was on, nothing else seems to happen. > > I also had to learn, that after the probe was not working, the user > cleared the USB-Stick. Can you please re-send this to atlas at ripe.net and please also include the probe id. Philip From wolfgang at garf.de Mon Dec 8 11:49:02 2014 From: wolfgang at garf.de (Wolfgang Tremmel) Date: Mon, 08 Dec 2014 11:49:02 +0100 Subject: [atlas] Dead Atlas Probe (TP-Link) In-Reply-To: References: <5481BD1C.5070104@inet.tu-berlin.de> Message-ID: <5485821E.2030709@garf.de> On 08.12.14 10:37, Phillip Remaker wrote: > If that doesn't work, try a new 4GB USB drive instead. what solved the problem for me was using a good USB power supply instead of the USB port of my server. Wolfgang From robert at ripe.net Tue Dec 9 10:52:22 2014 From: robert at ripe.net (Robert Kisteleki) Date: Tue, 09 Dec 2014 10:52:22 +0100 Subject: [atlas] MAT-WG proposal for WLAN measurements on RIPE Atlas In-Reply-To: References: <5477369502000001000503A2@gwroute.colegsirgar.ac.uk> <54773D67.5000606@ripe.net> Message-ID: <5486C656.6020406@ripe.net> Hi, > I'm sure a future hardware platform for RIPE Atlas (v4, v5) will support > 5GHz while mainting the competitve pricing of the current hardware. Picking up on this: we're always on the lookout for potential new hardware generations, and we are testing new devices as we learn about them. Recently we checked out the ASUS WL-330NUL and the Edimax BR-6258 Mini. While these are small and sexy enough (like the v1/v2 probes were; it looks like we basically invented the form factor (*) :-), their hardware is too constrained for our purposes. Please let us know if you know about new devices that we should evaluate. The primary requirements are price (should be off-the-shelf, most likely), capabilities (RAM and local storage needs 32MB minimum, the more the better) and form factor (see the above candidates; home router sized boxes are not really ideal). Regards, Robert (*) interesting historical artefact from our archives: the attached image is the "concept art" of how a probe could look like, dated mid-2010 -------------- next part -------------- A non-text attachment was scrubbed... Name: pic12168.jpg Type: image/jpeg Size: 20942 bytes Desc: not available URL: From astracha at ripe.net Tue Dec 9 12:15:28 2014 From: astracha at ripe.net (Alastair Strachan) Date: Tue, 9 Dec 2014 12:15:28 +0100 Subject: [atlas] PRT Systems Ltd (London, UK) has joined RIPE Atlas Anchors Message-ID: <7085E1B2-24AE-48D0-A994-D1131C882BC4@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 uk-lon-as8676 and it is hosted by PRT Systems Ltd in London, UK. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeroen at dckd.nl Tue Dec 9 13:03:12 2014 From: jeroen at dckd.nl (Jeroen van der Ham) Date: Tue, 9 Dec 2014 13:03:12 +0100 Subject: [atlas] MAT-WG proposal for WLAN measurements on RIPE Atlas In-Reply-To: <5486C656.6020406@ripe.net> References: <5477369502000001000503A2@gwroute.colegsirgar.ac.uk> <54773D67.5000606@ripe.net> <5486C656.6020406@ripe.net> Message-ID: Hi, > On 09 Dec 2014, at 10:52, Robert Kisteleki wrote: > > Hi, > >> I'm sure a future hardware platform for RIPE Atlas (v4, v5) will support >> 5GHz while mainting the competitve pricing of the current hardware. > Please let us know if you know about new devices that we should evaluate. > The primary requirements are price (should be off-the-shelf, most likely), > capabilities (RAM and local storage needs 32MB minimum, the more the better) > and form factor (see the above candidates; home router sized boxes are not > really ideal). Have you looked at the Vocore? http://vocore.io Jeroen. From astracha at ripe.net Wed Dec 10 10:11:11 2014 From: astracha at ripe.net (Alastair Strachan) Date: Wed, 10 Dec 2014 10:11:11 +0100 Subject: [atlas] =?iso-8859-1?q?N=FAcleo_de_Informa=E7=E3o_e_Coordena=E7?= =?iso-8859-1?q?=E3o_do_Ponto_BR_=28Sao_Paulo=2C_Brazil=29_has_joined_RIPE?= =?iso-8859-1?q?_Atlas_Anchors?= Message-ID: <57BD06F0-E260-47C7-BDAB-2FE13B3E46A8@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 br-sao-as22548 and it is hosted by N?cleo de Informa??o e Coordena??o do Ponto BR (Sao Paulo, Brazil) 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From colinj at mx5.org.uk Wed Dec 10 10:19:45 2014 From: colinj at mx5.org.uk (Colin Johnston) Date: Wed, 10 Dec 2014 09:19:45 +0000 Subject: [atlas] PRT Systems Ltd (London, UK) has joined RIPE Atlas Anchors In-Reply-To: <7085E1B2-24AE-48D0-A994-D1131C882BC4@ripe.net> References: <7085E1B2-24AE-48D0-A994-D1131C882BC4@ripe.net> Message-ID: <76F0B73D-D276-425D-9724-9ABEEB22926D@mx5.org.uk> When done to Paul at PRT :) Another good tracepoint for UK connectivity testing :) Colin > On 9 Dec 2014, at 11:15, Alastair Strachan wrote: > > 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 uk-lon-as8676 and it is hosted by PRT Systems Ltd in London, UK. > > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From schofield at terena.org Wed Dec 10 13:59:54 2014 From: schofield at terena.org (Brook Schofield) Date: Wed, 10 Dec 2014 16:59:54 +0400 Subject: [atlas] MAT-WG proposal for WLAN measurements on RIPE Atlas In-Reply-To: References: Message-ID: This thread seems to have gone off track and started to talk about a platform for RIPE Atlas v4 hardware. While I encourage that discussion I'm wondering if anyone has any comments on WLAN authentication testing and tests being run over the /current/ Atlas platform? Anything left out in my 5 points below? -Brook On 27 November 2014 at 17:52, Brook Schofield wrote: > MAT-WG, > > thankyou for giving me the opportunity to present on "The Value of WLAN > Measurements for the R&E Community" at the Measurement and Tools Working > Group at RIPE69. > > You can find my presentation and stenography logs at: > https://ripe69.ripe.net/presentations/91-eduroam-and-Atlas-RIPE69.pdf > https://ripe69.ripe.net/archives/steno/40 > > > To progress this work within the RIPE NCC Atlas development team I'd like > your input into the following five (5) points: > > > #1: For "opt-in" WLAN measurements to be enabled on RIPE Atlas > > As a point of clarification (and reiterated by Daniel Karrenberg) the > intention is that ALL v3 probes will be capable of WLAN measurements - but > measurements will ONLY be turned on by a probe host. > > > #2: WLAN measurements will support associating to an "open" or 802.1X > protected network for the purposes of performing a measurement > > As an active monitoring network the Atlas probes WILL NOT scan and report > on all/available SSIDs. It will ONLY associate with EXPLICITLY defined > SSIDs listed in the measurement. > > For eduroam quality purposes the success/failure of an 802.1X associations > is initially the most interesting part of the measurement in determining > whether sites are correctly deploying this service. There will be results > related to the authentication process. > > > #3: Any measurements performed over the wireless interface are aligned > with a request to associate/authenticate to a particular network. > > The wireless interface will be connected only for particular tests bundled > with the association to an SSID. All other tests will be performed via the > wired interface as is currently the case. > > > #4: The schedule for implementation will be determined by the RIPE NCC R&D > team > > ...but hopefully your support for this work will allow them to prioritise > this work while not jeopardising the other commitments the team has made > to the community. > > > #5: This proposal is inline with your understanding of "WiFi measurements" > on the Atlas roadmap > > I'd be particularly interested in your feedback on whether you thought > that the WiFi Measurements listed in the > http://roadmap.ripe.net/ripe-atlas/ would accomplish the above or > something completely different. > > > My feeling from the room was that the above was largely accepted. I'd > appreciate those that voiced their support to also do this on the mailing > list again. If there's any confusion I'm willing to clarify further. > > Thanks, > > -Brook > -- > =================================================== > Brook Schofield, Project Development Officer > G?ANT Association, Singel 468 D, 1017 AW Amsterdam, The Netherlands > Tel +31 20 530 4488 Fax +31 20 530 4499 Mob +31 65 155 3991 > www.g?ant.org > -- =================================================== Brook Schofield, Project Development Officer G?ANT Association, Singel 468 D, 1017 AW Amsterdam, The Netherlands Tel +31 20 530 4488 Fax +31 20 530 4499 Mob +31 65 155 3991 www.g?ant.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From mgalante at ripe.net Wed Dec 10 15:49:52 2014 From: mgalante at ripe.net (Michela Galante) Date: Wed, 10 Dec 2014 15:49:52 +0100 Subject: [atlas] ARIN (US) has joined RIPE Atlas anchors Message-ID: <809B542C-46DD-4F55-AA30-403D3532AE70@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 us-qas-as10745 and is hosted by ARIN in Ashburn, United States on behalf of the RIPE NCC. We?re very pleased that, with this latest addition, all five Regional Internet Registries are now hosting a RIPE Atlas anchor! 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: 2612 bytes Desc: not available URL: From woeber at cc.univie.ac.at Wed Dec 10 17:23:23 2014 From: woeber at cc.univie.ac.at (Wilfried Woeber) Date: Wed, 10 Dec 2014 17:23:23 +0100 Subject: [atlas] [mat-wg] MAT-WG proposal for WLAN measurements on RIPE Atlas In-Reply-To: References: Message-ID: <5488737B.1030001@cc.univie.ac.at> On 2014-12-10 13:59, Brook Schofield wrote: [...] > Anything left out in my 5 points below? Maybe :-) What would be the management model for those probes? I presume that both the "eduroam" operators would want to have access to the probes' data (and management?) as well as the organisations where the probes are plugged in. Which may bring the issue of a *simple* shared access and/or management capability back to the table. > -Brook Wilfried. From brak at gameservers.com Wed Dec 10 18:00:51 2014 From: brak at gameservers.com (Brian Rak) Date: Wed, 10 Dec 2014 12:00:51 -0500 Subject: [atlas] Embed links in Beta UI Message-ID: <54887C43.7060002@gameservers.com> The embed option in the Beta UI is *very* handy, thanks for that! From robert at ripe.net Wed Dec 10 18:10:53 2014 From: robert at ripe.net (Robert Kisteleki) Date: Wed, 10 Dec 2014 18:10:53 +0100 Subject: [atlas] [mat-wg] MAT-WG proposal for WLAN measurements on RIPE Atlas In-Reply-To: <5488737B.1030001@cc.univie.ac.at> References: <5488737B.1030001@cc.univie.ac.at> Message-ID: <54887E9D.4090904@ripe.net> On 2014-12-10 17:23, Wilfried Woeber wrote: > What would be the management model for those probes? > I presume that both the "eduroam" operators would want to have access to the probes' > data (and management?) as well as the organisations where the probes are plugged in. The idea is that the probe that will/may do wifi (such as eduroam) in the future has to first function as a regular probe, ie. connected over a wired connection, working properly, have a host, etc. *Then* the host can allow wifi measurements on the probe. This also allows existing hosts to opt-in into such measurements. > Which may bring the issue of a *simple* shared access and/or management capability > back to the table. No, not really. It'd be bad is someone else other than the host could manage this. Regards, Robert From BECHA at ripe.net Wed Dec 10 22:15:47 2014 From: BECHA at ripe.net (Vesna Manojlovic) Date: Wed, 10 Dec 2014 22:15:47 +0100 Subject: [atlas] Coming soon: RIPE Atlas data visualization hackathon! Message-ID: <5488B803.1040809@ripe.net> Dear all, we are happy to invite you to the first RIPE Atlas open data hackathon! In short: various groups will come together during the long weekend in Amsterdam, to make new visualisations (or modify existing ones) based on RIPE Atlas data, and to give that SW back to the community. We are inviting: programers, designers, operators, data-lovers, hackers, students... help us spread the word! Comcast is generously offering prizes and some coverage for travel expenses for several people -- to be awarded/selected by a jury. Dates: 27-28-29 March 2015 (Friday to Sunday) How to apply: https://www.ripe.net/s/XUJy More information, as always, in the RIPE Labs article: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-hackathon-2015 Hope to see you there! Regards, Vesna From sebastian at nzrs.net.nz Sun Dec 14 22:28:13 2014 From: sebastian at nzrs.net.nz (Sebastian Castro) Date: Mon, 15 Dec 2014 10:28:13 +1300 Subject: [atlas] Bug on credit expenditure? Message-ID: <548E00ED.5060609@nzrs.net.nz> Hi: I've created 12 one-off traceroute measurements today, each measurement requesting 38 probes. According to the results page, the number of credits per measurement is 60, at 38 probes, we got 2280 credits. Any further attempt to create new measurements returned error 104: "Executing this measurement request would violate your maximum daily spending limit of 2200000.0 credits" Unless my math is horribly wrong, or the message is incorrect, I'm well under the 2.2 million credits daily limit. Is there a bug somewhere that's miscounting the usage of credits? I have enough credits in my account to pamper myself with measurements :) Cheers, -- Sebastian Castro Technical Research Manager .nz Registry Services (New Zealand Domain Name Registry Limited) desk: +64 4 495 2337 mobile: +64 21 400535 From vnaumov at ripe.net Tue Dec 16 09:45:08 2014 From: vnaumov at ripe.net (Viktor Naumov) Date: Tue, 16 Dec 2014 09:45:08 +0100 Subject: [atlas] Bug on credit expenditure? In-Reply-To: <548E00ED.5060609@nzrs.net.nz> References: <548E00ED.5060609@nzrs.net.nz> Message-ID: <548FF114.5030304@ripe.net> Hi Sebastian, You're right indeed. I'm tracing the cost estimation routines at this moment. The fix will be out there shortly. I will keep you updated. Thank you! /vty On 12/14/14, 10:28 PM, Sebastian Castro wrote: > Hi: > > I've created 12 one-off traceroute measurements today, each measurement > requesting 38 probes. According to the results page, the number of > credits per measurement is 60, at 38 probes, we got 2280 credits. > > Any further attempt to create new measurements returned error 104: > "Executing this measurement request would violate your maximum daily > spending limit of 2200000.0 credits" Unless my math is horribly wrong, > or the message is incorrect, I'm well under the 2.2 million credits > daily limit. > > Is there a bug somewhere that's miscounting the usage of credits? I have > enough credits in my account to pamper myself with measurements :) > > Cheers, From astracha at ripe.net Thu Dec 18 11:10:48 2014 From: astracha at ripe.net (Alastair Strachan) Date: Thu, 18 Dec 2014 11:10:48 +0100 Subject: [atlas] Liquid Web (Phoenix, US) has joined RIPE Atlas Anchors. Message-ID: <8DE3AC98-B811-4119-A80C-94A51EB8F924@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 us-phx-as53824 and it is hosted by Liquid Web in Phoenix, United States. Congratulations to Liquid Web for their second anchor online! 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From vnaumov at ripe.net Fri Dec 19 11:11:26 2014 From: vnaumov at ripe.net (Viktor Naumov) Date: Fri, 19 Dec 2014 11:11:26 +0100 Subject: [atlas] Bug on credit expenditure? In-Reply-To: <548FF114.5030304@ripe.net> References: <548E00ED.5060609@nzrs.net.nz> <548FF114.5030304@ripe.net> Message-ID: <5493F9CE.2050101@ripe.net> The cost estimation should be ok now. /vty On 12/16/14, 9:45 AM, Viktor Naumov wrote: > Hi Sebastian, > > You're right indeed. I'm tracing the cost estimation routines at this > moment. The fix will be out there shortly. > I will keep you updated. > > Thank you! > > /vty > > On 12/14/14, 10:28 PM, Sebastian Castro wrote: >> Hi: >> >> I've created 12 one-off traceroute measurements today, each measurement >> requesting 38 probes. According to the results page, the number of >> credits per measurement is 60, at 38 probes, we got 2280 credits. >> >> Any further attempt to create new measurements returned error 104: >> "Executing this measurement request would violate your maximum daily >> spending limit of 2200000.0 credits" Unless my math is horribly wrong, >> or the message is incorrect, I'm well under the 2.2 million credits >> daily limit. >> >> Is there a bug somewhere that's miscounting the usage of credits? I have >> enough credits in my account to pamper myself with measurements :) >> >> Cheers, > > From lukasz at trabinski.net Mon Dec 22 13:30:40 2014 From: lukasz at trabinski.net (Lukasz Trabinski) Date: Mon, 22 Dec 2014 13:30:40 +0100 (CET) Subject: [atlas] Sharing measurement Message-ID: hi It's possible to share (graphical) measurement from my ripe probe without login to my account? From dquinn at ripe.net Mon Dec 22 14:16:27 2014 From: dquinn at ripe.net (Daniel Quinn) Date: Mon, 22 Dec 2014 14:16:27 +0100 Subject: [atlas] Sharing measurement In-Reply-To: References: Message-ID: <549819AB.5020808@ripe.net> I think I'm going to need more clarification on what you need: are you talking about a measurement page like this: https://atlas.ripe.net/measurements/1000192/ Or a probe page like this? https://atlas.ripe.net/probes/10006/ The easiest way to share a measurement page is to mark the measurement public, and then just give out the URL for the page as I have above. No account sharing required. Similarly, you can mark a probe public and then give that probe's URL to the person. If however, you don't want to make your measurement public, the only way to give people access to it without giving up your account is to give them an API key and let them access the data via the API -- though this is of course not graphical. As for non-public probes, we do allow limited sharing if you belong to an LIR. You can allow probe management by other members of your LIR by going to "Management Sharing" on the probe page when you're logged in and filling out the form there. If you don't see a section with that name, you're probably not a member of an LIR, which means you're only able to share probes that are marked "public". If however you want to share non-public measurements, On 22/12/14 13:30, Lukasz Trabinski wrote: > hi > > It's possible to share (graphical) measurement from my ripe probe > without login to my account? > From lukasz at trabinski.net Mon Dec 22 14:37:53 2014 From: lukasz at trabinski.net (=?utf-8?Q?=C5=81ukasz_Tr=C4=85bi=C5=84ski?=) Date: Mon, 22 Dec 2014 14:37:53 +0100 Subject: [atlas] Sharing measurement In-Reply-To: <549819AB.5020808@ripe.net> References: <549819AB.5020808@ripe.net> Message-ID: Hi My probe is marked as public https://atlas.ripe.net/probes/16736 but when I?m not login in I can?t see for example "Results from Built-in Measurements?. I would like show / share it to everyone. > Wiadomo?? napisana przez Daniel Quinn w dniu 22 gru 2014, o godz. 14:16: > > I think I'm going to need more clarification on what you need: are you > talking about a measurement page like this: > > https://atlas.ripe.net/measurements/1000192/ > > Or a probe page like this? > > https://atlas.ripe.net/probes/10006/ > > The easiest way to share a measurement page is to mark the measurement > public, and then just give out the URL for the page as I have above. No > account sharing required. Similarly, you can mark a probe public and > then give that probe's URL to the person. > > If however, you don't want to make your measurement public, the only way > to give people access to it without giving up your account is to give > them an API key and let them access the data via the API -- though this > is of course not graphical. > > As for non-public probes, we do allow limited sharing if you belong to > an LIR. You can allow probe management by other members of your LIR by > going to "Management Sharing" on the probe page when you're logged in > and filling out the form there. If you don't see a section with that > name, you're probably not a member of an LIR, which means you're only > able to share probes that are marked "public". > > If however you want to share non-public measurements, > > On 22/12/14 13:30, Lukasz Trabinski wrote: >> hi >> >> It's possible to share (graphical) measurement from my ripe probe >> without login to my account? >> > From dquinn at ripe.net Mon Dec 22 15:05:17 2014 From: dquinn at ripe.net (Daniel Quinn) Date: Mon, 22 Dec 2014 15:05:17 +0100 Subject: [atlas] Sharing measurement In-Reply-To: References: <549819AB.5020808@ripe.net> Message-ID: <5498251D.7070606@ripe.net> Ah, for that, all you need to know is that all of the graphs on that page are coming from RIPEStat. Once you know this, you can figure out how to share the charts: 1. While logged in, find your probe and click on ?Results from Built-in Measurements? 2. Under the chart you want to share, click the little little square button with the two arrows on it. If you hold your mouse over the button, you should get a little tooltip that says ?Enlarge?. I?ve attached a screenshot of the button I?m talking about. 3. An overlay will appear with a larger version of the chart, and below that is a button labelled ?See this on RIPEStat?. Click that button. 4. You?ll be directed to a page that looks like this . This is a RIPEStat widget page that?s publicly available for your probe that you can share with whomever you like. We?re working on making things like this easier, but for the moment, this should get you what you need. ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: arrows.png Type: image/png Size: 1365 bytes Desc: not available URL: From jared at puck.Nether.net Mon Dec 22 19:36:07 2014 From: jared at puck.Nether.net (Jared Mauch) Date: Mon, 22 Dec 2014 13:36:07 -0500 Subject: [atlas] Sharing measurement In-Reply-To: References: Message-ID: <20141222183607.GD30063@puck.nether.net> What i've done is tell people to create an account (free) and give them the direct link to the msm in the past. eg: https://atlas.ripe.net/atlas/udm.html?msm_id=1665596#!tab-seismograph1665596 It would be nice if there was an easier way to link to the interface without them creating an account but that's sometimes not feasible. - Jared On Mon, Dec 22, 2014 at 01:30:40PM +0100, Lukasz Trabinski wrote: > hi > > It's possible to share (graphical) measurement from my ripe probe without > login to my account? -- Jared Mauch | pgp key available via finger from jared at puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine. From dquinn at ripe.net Tue Dec 23 11:24:51 2014 From: dquinn at ripe.net (Daniel Quinn) Date: Tue, 23 Dec 2014 11:24:51 +0100 Subject: [atlas] Sharing measurement In-Reply-To: <20141222183607.GD30063@puck.nether.net> References: <20141222183607.GD30063@puck.nether.net> Message-ID: <549942F3.4060603@ripe.net> It would be nice if there was an easier way to link to the interface without them creating an account but that?s sometimes not feasible. It?s absolutely possible. Public measurements are available publicly (read: no login required) now via the new interface. To use your measurement ID for example: https://atlas.ripe.net/measurements/1665596/#!seismograph Note that the new measurement pages will replace the old ones in the new year, but until then both are available. They?re right next to each other in the navigation: old on the left, new on the right. ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From lukasz at trabinski.net Tue Dec 23 14:18:16 2014 From: lukasz at trabinski.net (=?utf-8?Q?=C5=81ukasz_Tr=C4=85bi=C5=84ski?=) Date: Tue, 23 Dec 2014 14:18:16 +0100 Subject: [atlas] Sharing measurement In-Reply-To: <5498251D.7070606@ripe.net> References: <549819AB.5020808@ripe.net> <5498251D.7070606@ripe.net> Message-ID: <3850EE95-AC22-4FF6-8009-FE7B3088AE6A@trabinski.net> Thank?s. It?s works. But I would like have on one link all graphs. > Wiadomo?? napisana przez Daniel Quinn w dniu 22 gru 2014, o godz. 15:05: > > Ah, for that, all you need to know is that all of the graphs on that page are coming from RIPEStat. Once you know this, you can figure out how to share the charts: > > ? While logged in, find your probe and click on ?Results from Built-in Measurements? > ? Under the chart you want to share, click the little little square button with the two arrows on it. If you hold your mouse over the button, you should get a little tooltip that says ?Enlarge?. I?ve attached a screenshot of the button I?m talking about. > ? An overlay will appear with a larger version of the chart, and below that is a button labelled ?See this on RIPEStat?. Click that button. > ? You?ll be directed to a page that looks like this. This is a RIPEStat widget page that?s publicly available for your probe that you can share with whomever you like. > We?re working on making things like this easier, but for the moment, this should get you what you need. > > From dquinn at ripe.net Tue Dec 23 14:19:04 2014 From: dquinn at ripe.net (Daniel Quinn) Date: Tue, 23 Dec 2014 14:19:04 +0100 Subject: [atlas] Sharing measurement In-Reply-To: <3850EE95-AC22-4FF6-8009-FE7B3088AE6A@trabinski.net> References: <549819AB.5020808@ripe.net> <5498251D.7070606@ripe.net> <3850EE95-AC22-4FF6-8009-FE7B3088AE6A@trabinski.net> Message-ID: <54996BC8.3050104@ripe.net> Duely noted. We'll see if we can make that work in future releases. From d.baeza at tvt-datos.es Sun Dec 28 10:59:33 2014 From: d.baeza at tvt-datos.es (d.baeza at tvt-datos.es) Date: Sun, 28 Dec 2014 10:59:33 +0100 Subject: [atlas] Open IP Map, crowdsourced geolocation Message-ID: <23d70616b56f89af6190fdc04a421347@tvt-datos.es> Hi All! I know is in Beta, but only say when I try to submit[ok button] a Geolocation of a IP/Hostname, it keeps "loading" forever. Should I use any special set of code? Im trying City,Province,XX (XX = Country Code, in my case: ES) Thanks in advance! --Daniel From d.baeza at tvt-datos.es Sun Dec 28 11:13:22 2014 From: d.baeza at tvt-datos.es (d.baeza at tvt-datos.es) Date: Sun, 28 Dec 2014 11:13:22 +0100 Subject: [atlas] Open IP Map, crowdsourced geolocation In-Reply-To: <23d70616b56f89af6190fdc04a421347@tvt-datos.es> References: <23d70616b56f89af6190fdc04a421347@tvt-datos.es> Message-ID: <787edb626e9e0c74955afab6bd8ab408@tvt-datos.es> It saves the geoloc, even if it keeps "loading". El 2014-12-28 10:59, d.baeza at tvt-datos.es escribi?: > Hi All! > > I know is in Beta, but only say when I try to submit[ok button] a > Geolocation of a IP/Hostname, it keeps "loading" forever. > > Should I use any special set of code? Im trying City,Province,XX (XX > = Country Code, in my case: ES) > > Thanks in advance! > > --Daniel From d.baeza at tvt-datos.es Sun Dec 28 13:38:59 2014 From: d.baeza at tvt-datos.es (d.baeza at tvt-datos.es) Date: Sun, 28 Dec 2014 13:38:59 +0100 Subject: [atlas] Open IP Map, crowdsourced geolocation In-Reply-To: <787edb626e9e0c74955afab6bd8ab408@tvt-datos.es> References: <23d70616b56f89af6190fdc04a421347@tvt-datos.es> <787edb626e9e0c74955afab6bd8ab408@tvt-datos.es> Message-ID: <55d88a9c04c991796d714405641638eb@tvt-datos.es> OK, I founded the problem. If you dont write exactly, it will geolocate it for you. Thats the loading. By the way, It is possible to geolocate even if there isnt reverse host? I mean, I know where an IP is, but it doesnt have any reverse. --Daniel El 2014-12-28 11:13, d.baeza at tvt-datos.es escribi?: > It saves the geoloc, even if it keeps "loading". > > El 2014-12-28 10:59, d.baeza at tvt-datos.es escribi?: >> Hi All! >> I know is in Beta, but only say when I try to submit[ok button] a >> Geolocation of a IP/Hostname, it keeps "loading" forever. >> Should I use any special set of code? Im trying City,Province,XX (XX >> = Country Code, in my case: ES) >> Thanks in advance! >> --Daniel From emile.aben at ripe.net Sun Dec 28 22:35:17 2014 From: emile.aben at ripe.net (Emile Aben) Date: Sun, 28 Dec 2014 22:35:17 +0100 Subject: [atlas] Open IP Map, crowdsourced geolocation In-Reply-To: <55d88a9c04c991796d714405641638eb@tvt-datos.es> References: <23d70616b56f89af6190fdc04a421347@tvt-datos.es> <787edb626e9e0c74955afab6bd8ab408@tvt-datos.es> <55d88a9c04c991796d714405641638eb@tvt-datos.es> Message-ID: <54A07795.1050800@ripe.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hola Daniel, Thanks for your interest in OpenIPMap. On 28/12/14 13:38, d.baeza at tvt-datos.es wrote: > OK, I founded the problem. If you dont write exactly, it will > geolocate it for you. Thats the loading. I'm to blame for that. OpenIPMap is developed separately from RIPE Atlas and its development team (me) doesn't have the same user-interface expertise the RIPE Atlas team has. That said, OpenIPMap-source code is available on github: https://github.com/emileaben/django-openipmap (the tracemap is at templates/oim/tracemap.html) and would happily accept pull requests specifically for improving the UI robustness/user-friendliness. As this is prototype code, please contact me directly if somebody is interested in contributing code there, to help kick-start that. > By the way, It is possible to geolocate even if there isnt reverse > host? Currently not via the UI that is exposed via the RIPE Atlas website, but there is a rudimentary form for uploading IP prefix info at: https://marmot.ripe.net/openipmap/bulk-upload/ hope this helps, Emile > > I mean, I know where an IP is, but it doesnt have any reverse. > > --Daniel > > El 2014-12-28 11:13, d.baeza at tvt-datos.es escribi?: >> It saves the geoloc, even if it keeps "loading". >> >> El 2014-12-28 10:59, d.baeza at tvt-datos.es escribi?: >>> Hi All! I know is in Beta, but only say when I try to submit[ok >>> button] a Geolocation of a IP/Hostname, it keeps "loading" >>> forever. Should I use any special set of code? Im trying >>> City,Province,XX (XX = Country Code, in my case: ES) Thanks in >>> advance! --Daniel > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUoHeUAAoJEKxthF6wloMO+q0P/ilYiDz7y0qY5n3PzUVTcMTe M3XY5d8HQMLQSUgZNrJEGYkh2FK1gPE8W0JeFO9G50KKNqYck3LDu0XKldL25XQD pNdhN3mCf3HbEi06paEgyxq8K/8StRU5B0xWw+qKfax6nw7YQFHfzIcVRYDaNRUm ZxR38PIzTDxdqG6+K7aFmVOaFQAdLNp0n6RYwVH5KkQX131dgRSO03VB/Hj+7wEq FWvBGaQ7nMr0BBbGdgeOh2LOgT9oaTDoIOY1+gJXWU0n4zZ2uO1zgUY7kb2ywpzd 5FzpnbTP80X1Zct/ud5LssTwhC95xqQgQBLpmzq3BaR5l1oNS5bvayO3yKda8Q1J AKyV9YXLosIWAG2e0l0jOfZ5L7dnE7yGYjtm9R23HYLvMDwvgye6xMT1xFZ84+K5 ICoptide/GGQ8UR6bokG+ASCixlfPnXySuzYD4jobQhBwcUI3JPW5SXMFVo+mVsM J6y7xU98S/sNMTvDkkRvW+k92H0UXXK76V/4rqSwgT7inIhXEXJ8eVTsBISAiZ8D RkC5hlmW8tQehlTkv/YP85fCO8i668DSTLlLBSLGnJoMoqtAXnGXNkiWvYgd2BZV uOj7wL3nSPyXekf5baAZUSjH1pP+jnDMqxOdK8+nDSNG4VjauDcjLToulwhbQ5qK HYOat7xSBZYwpIVN6Hng =vpMP -----END PGP SIGNATURE-----