From Woeber at CC.UniVie.ac.at Fri Mar 2 23:14:43 2012 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Fri, 02 Mar 2012 22:14:43 +0000 Subject: [atlas] probe 466 running unattended Message-ID: <4F514653.70607@CC.UniVie.ac.at> Dear Atlas-Team! I am almost on my way to Costa Rica for the next ICANN meeting, and taking some time off before, and - more extensively :-) - after. Thus my probe at home, #466, may go offline if there's an environmental or ISP-upstream problem, that prevents its automatic recovery. I am scheduled to be back home around the Easter weekend, probably on Sunday, April 8th. Also, the probe in my office, #414, runs unattended during that period, but you are welcome to contact for hands and eyes to get it back up, just in case. Best regards, Wilfried. From bortzmeyer at nic.fr Mon Mar 5 11:24:37 2012 From: bortzmeyer at nic.fr (Stephane Bortzmeyer) Date: Mon, 5 Mar 2012 11:24:37 +0100 Subject: [atlas] probe 466 running unattended In-Reply-To: <4F514653.70607@CC.UniVie.ac.at> References: <4F514653.70607@CC.UniVie.ac.at> Message-ID: <20120305102437.GA28637@nic.fr> On Fri, Mar 02, 2012 at 10:14:43PM +0000, Wilfried Woeber, UniVie/ACOnet wrote a message of 17 lines which said: > Thus my probe at home, #466, may go offline if there's an environmental > or ISP-upstream problem, that prevents its automatic recovery. How many Atlas probes are running? Imagine what will happen if every manager tells the whole list about his trips :-) From simon at josefsson.org Wed Mar 14 10:05:05 2012 From: simon at josefsson.org (Simon Josefsson) Date: Wed, 14 Mar 2012 10:05:05 +0100 Subject: [atlas] ghostgraz.com Message-ID: <878vj3tuwu.fsf@latte.josefsson.org> I was debugging my local DNS resolver when I noticed peculiar lookups from the Atlas probe for 'ghostgraz.com'. It seems to happen once in a while. Does anyone have any idea what this is? I don't see it in the list of built-in measurements, and I don't recall configuring anything related to that site myself. /Simon 14-Mar-2012 08:55:36.732 client 192.168.1.48#58740: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 08:55:36.734 client 192.168.1.48#40389: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 08:55:36.737 client 192.168.1.48#44142: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 08:55:36.740 client 192.168.1.48#59254: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 08:55:36.742 client 192.168.1.48#56991: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 08:55:36.745 client 192.168.1.48#59319: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 08:55:36.769 client 192.168.1.48#55435: query: ghostgraz.com IN A + (192.168.1.47) 14-Mar-2012 08:55:56.001 client 192.168.1.48#49742: query: caldwell.atlas.ripe.net IN AAAA + (192.168.1.47) 14-Mar-2012 08:55:56.146 client 192.168.1.48#34211: query: caldwell.atlas.ripe.net IN A + (192.168.1.47) 14-Mar-2012 08:58:38.199 client 192.168.1.48#42327: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 08:58:38.202 client 192.168.1.48#53097: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 08:58:38.204 client 192.168.1.48#54101: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 08:58:38.207 client 192.168.1.48#52439: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 08:58:38.210 client 192.168.1.48#37104: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 08:58:38.212 client 192.168.1.48#59275: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 08:58:38.216 client 192.168.1.48#49299: query: ghostgraz.com IN A + (192.168.1.47) 14-Mar-2012 09:01:28.778 client 192.168.1.48#58887: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 09:01:28.781 client 192.168.1.48#52689: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 09:01:28.784 client 192.168.1.48#40593: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 09:01:28.787 client 192.168.1.48#51568: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 09:01:28.790 client 192.168.1.48#36493: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 09:01:28.792 client 192.168.1.48#33057: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 09:01:28.796 client 192.168.1.48#49588: query: ghostgraz.com IN A + (192.168.1.47) 14-Mar-2012 09:01:34.977 client 192.168.1.48#35392: query: www.ripe.net IN A + (192.168.1.47) From philip.homburg at ripe.net Wed Mar 14 10:32:20 2012 From: philip.homburg at ripe.net (Philip Homburg) Date: Wed, 14 Mar 2012 10:32:20 +0100 Subject: [atlas] ghostgraz.com In-Reply-To: <878vj3tuwu.fsf@latte.josefsson.org> References: <878vj3tuwu.fsf@latte.josefsson.org> Message-ID: <4F6065A4.40004@ripe.net> On 3/14/12 10:05 , Simon Josefsson wrote: > I was debugging my local DNS resolver when I noticed peculiar lookups > from the Atlas probe for 'ghostgraz.com'. It seems to happen once in a > while. Does anyone have any idea what this is? I don't see it in the > list of built-in measurements, and I don't recall configuring anything > related to that site myself. > > /Simon > > 14-Mar-2012 08:55:36.732 client 192.168.1.48#58740: query: ghostgraz.com IN AAAA + (192.168.1.47) > That seems to be a UDM that scheduled on your probe. Unfortunately, at the moment probes host don't have a means to find out what measurements are running on their probes. From robert at ripe.net Wed Mar 14 10:40:33 2012 From: robert at ripe.net (Robert Kisteleki) Date: Wed, 14 Mar 2012 10:40:33 +0100 Subject: [atlas] ghostgraz.com In-Reply-To: <4F6065A4.40004@ripe.net> References: <878vj3tuwu.fsf@latte.josefsson.org> <4F6065A4.40004@ripe.net> Message-ID: <4F606791.50709@ripe.net> On 2012.03.14. 10:32, Philip Homburg wrote: > On 3/14/12 10:05 , Simon Josefsson wrote: >> I was debugging my local DNS resolver when I noticed peculiar lookups >> from the Atlas probe for 'ghostgraz.com'. It seems to happen once in a >> while. Does anyone have any idea what this is? I don't see it in the >> list of built-in measurements, and I don't recall configuring anything >> related to that site myself. >> >> /Simon >> >> 14-Mar-2012 08:55:36.732 client 192.168.1.48#58740: query: ghostgraz.com >> IN AAAA + (192.168.1.47) >> > That seems to be a UDM that scheduled on your probe. Unfortunately, at the > moment probes host don't have a means to find out what measurements are > running on their probes. On a positive note: since this is interesting and useful information, we'll show the list of the ongoing measurements on for each probe on the "probe status" page. This is most likely going to happen when we go live with UDMs. Regards, Robert From simon at josefsson.org Wed Mar 14 10:50:14 2012 From: simon at josefsson.org (Simon Josefsson) Date: Wed, 14 Mar 2012 10:50:14 +0100 Subject: [atlas] ghostgraz.com In-Reply-To: <4F606791.50709@ripe.net> (Robert Kisteleki's message of "Wed, 14 Mar 2012 10:40:33 +0100") References: <878vj3tuwu.fsf@latte.josefsson.org> <4F6065A4.40004@ripe.net> <4F606791.50709@ripe.net> Message-ID: <874ntrtstl.fsf@latte.josefsson.org> Robert Kisteleki writes: > On 2012.03.14. 10:32, Philip Homburg wrote: >> On 3/14/12 10:05 , Simon Josefsson wrote: >>> I was debugging my local DNS resolver when I noticed peculiar lookups >>> from the Atlas probe for 'ghostgraz.com'. It seems to happen once in a >>> while. Does anyone have any idea what this is? I don't see it in the >>> list of built-in measurements, and I don't recall configuring anything >>> related to that site myself. >>> >>> /Simon >>> >>> 14-Mar-2012 08:55:36.732 client 192.168.1.48#58740: query: ghostgraz.com >>> IN AAAA + (192.168.1.47) >>> >> That seems to be a UDM that scheduled on your probe. Unfortunately, at the >> moment probes host don't have a means to find out what measurements are >> running on their probes. > > On a positive note: since this is interesting and useful information, we'll > show the list of the ongoing measurements on for each probe on the "probe > status" page. This is most likely going to happen when we go live with UDMs. Thanks for feedback -- I was mostly concerned that the probe might had been hijacked. /Simon From carsten at schiefner.de Wed Mar 14 10:46:53 2012 From: carsten at schiefner.de (Carsten Schiefner) Date: Wed, 14 Mar 2012 10:46:53 +0100 Subject: [atlas] ghostgraz.com In-Reply-To: <4F6065A4.40004@ripe.net> References: <878vj3tuwu.fsf@latte.josefsson.org> <4F6065A4.40004@ripe.net> Message-ID: <4F60690D.6040008@schiefner.de> Hi Philipp, could I - and maybe others, too - be enlighted what "UDM" stands for, please? The usual acronym finders don't help me here. Thanks, -C. On 14.03.2012 10:32, Philip Homburg wrote: > On 3/14/12 10:05 , Simon Josefsson wrote: >> I was debugging my local DNS resolver when I noticed peculiar lookups >> from the Atlas probe for 'ghostgraz.com'. It seems to happen once in a >> while. Does anyone have any idea what this is? I don't see it in the >> list of built-in measurements, and I don't recall configuring anything >> related to that site myself. >> >> /Simon >> >> 14-Mar-2012 08:55:36.732 client 192.168.1.48#58740: query: >> ghostgraz.com IN AAAA + (192.168.1.47) >> > That seems to be a UDM that scheduled on your probe. Unfortunately, at > the moment probes host don't have a means to find out what measurements > are running on their probes. From philip.homburg at ripe.net Wed Mar 14 11:25:50 2012 From: philip.homburg at ripe.net (Philip Homburg) Date: Wed, 14 Mar 2012 11:25:50 +0100 Subject: [atlas] ghostgraz.com In-Reply-To: <4F60690D.6040008@schiefner.de> References: <878vj3tuwu.fsf@latte.josefsson.org> <4F6065A4.40004@ripe.net> <4F60690D.6040008@schiefner.de> Message-ID: <4F60722E.60302@ripe.net> On 3/14/12 10:46 , Carsten Schiefner wrote: > > could I - and maybe others, too - be enlighted what "UDM" stands for, > please? The usual acronym finders don't help me here. > Google 'atlas udm' :-) It stands for User Defined Measurements -------------- next part -------------- An HTML attachment was scrubbed... URL: From carsten at schiefner.de Wed Mar 14 11:30:15 2012 From: carsten at schiefner.de (Carsten Schiefner) Date: Wed, 14 Mar 2012 11:30:15 +0100 Subject: [atlas] ghostgraz.com In-Reply-To: <4F60722E.60302@ripe.net> References: <878vj3tuwu.fsf@latte.josefsson.org> <4F6065A4.40004@ripe.net> <4F60690D.6040008@schiefner.de> <4F60722E.60302@ripe.net> Message-ID: <4F607337.4050900@schiefner.de> Thanks, Philipp. On 14.03.2012 11:25, Philip Homburg wrote: > On 3/14/12 10:46 , Carsten Schiefner wrote: >> >> could I - and maybe others, too - be enlighted what "UDM" stands for, >> please? The usual acronym finders don't help me here. >> > Google 'atlas udm' :-) > > It stands for User Defined Measurements From robert at ripe.net Fri Mar 16 13:19:31 2012 From: robert at ripe.net (Robert Kisteleki) Date: Fri, 16 Mar 2012 13:19:31 +0100 Subject: [atlas] Small changes deployed on this Wednesday Message-ID: <4F632FD3.8060108@ripe.net> Dear Atlas Users, On Wednesday we've deployed some changes to the UI. The most notable change is that from now on the download format of your probe's measurement data is JSON. The actual syntax is pretty much self-explanatory. The DNS anycast map now visualises server versions and SOA serials too. We made further changes to the way we show static network configuration of a probe on the "probe status" page. We also did some preparations to include Atlas in RIPE NCC Access, the RIPE NCC Single Sign On system. Regards, Robert, for the RIPE Atlas team From colinj at mx5.org.uk Sun Mar 18 20:15:27 2012 From: colinj at mx5.org.uk (Colin Johnston) Date: Sun, 18 Mar 2012 19:15:27 +0000 Subject: [atlas] Fwd: Probe 2317 is down References: <20120318140001.24187.79532@Debian-50-lenny-64-minimal> Message-ID: hey no idea why probe is down, powered it on and off. defo has comms and dynamic ip also connectivity seems good as well ? Any ideas ? Col Begin forwarded message: > From: RIPE Atlas > Date: 18 March 2012 14:00:01 GMT > To: colin johnston > Subject: Probe 2317 is down > > Dear colin, > > Your probe 2317 is down since 2012-03-18 13:11:17 UTC > > This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe goes is down for more than 30 minutes. > > If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/atlas/myprobes.html, click on probe 2317, in the opened tab select Probe's Settings -> Notifications and change your settings. > > Atlas team -------------- next part -------------- An HTML attachment was scrubbed... URL: From astrikos at ripe.net Mon Mar 19 13:47:44 2012 From: astrikos at ripe.net (Andreas Strikos) Date: Mon, 19 Mar 2012 13:47:44 +0100 Subject: [atlas] Fwd: Probe 2317 is down In-Reply-To: References: <20120318140001.24187.79532@Debian-50-lenny-64-minimal> Message-ID: <4F672AF0.5070908@ripe.net> Hi Col, Yesterday during an internal maintenance we had some network problems which confused one of our controllers and few (7) probes had problems to connect to it. All of them should be ok now. Regards, Andreas On 3/18/12 8:15 PM, Colin Johnston wrote: > > hey > no idea why probe is down, powered it on and off. > > defo has comms and dynamic ip > > also connectivity seems good as well ? > > Any ideas ? > > Col > > > Begin forwarded message: > >> *From: *RIPE Atlas > >> *Date: *18 March 2012 14:00:01 GMT >> *To: *colin johnston > >> *Subject: **Probe 2317 is down* >> >> Dear colin, >> >> Your probe 2317 is down since 2012-03-18 13:11:17 UTC >> >> This is an automatically generated email from RIPE Atlas. It was >> sent to you because you asked to be notified if your probe goes is >> down for more than 30 minutes. >> >> If you want to change this, or disable this notification altogether, >> please go to https://atlas.ripe.net/atlas/myprobes.html, click on >> probe 2317, in the opened tab select Probe's Settings -> >> Notifications and change your settings. >> >> Atlas team > -------------- next part -------------- An HTML attachment was scrubbed... URL: From colinj at mx5.org.uk Mon Mar 19 15:22:36 2012 From: colinj at mx5.org.uk (Colin Johnston) Date: Mon, 19 Mar 2012 14:22:36 +0000 Subject: [atlas] Fwd: Probe 2317 is down In-Reply-To: <4F672AF0.5070908@ripe.net> References: <20120318140001.24187.79532@Debian-50-lenny-64-minimal> <4F672AF0.5070908@ripe.net> Message-ID: <5A03CF06-CB75-4E80-BA0E-096BD185ABF6@mx5.org.uk> Thanks for resolving Colin On 19 Mar 2012, at 12:47, Andreas Strikos wrote: > Hi Col, > > Yesterday during an internal maintenance we had some network problems which confused one of our controllers and few (7) probes had problems to connect to it. > All of them should be ok now. > > Regards, > Andreas > On 3/18/12 8:15 PM, Colin Johnston wrote: >> >> >> hey >> no idea why probe is down, powered it on and off. >> >> defo has comms and dynamic ip >> >> also connectivity seems good as well ? >> >> Any ideas ? >> >> Col >> >> >> Begin forwarded message: >> >>> From: RIPE Atlas >>> Date: 18 March 2012 14:00:01 GMT >>> To: colin johnston >>> Subject: Probe 2317 is down >>> >>> Dear colin, >>> >>> Your probe 2317 is down since 2012-03-18 13:11:17 UTC >>> >>> This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe goes is down for more than 30 minutes. >>> >>> If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/atlas/myprobes.html, click on probe 2317, in the opened tab select Probe's Settings -> Notifications and change your settings. >>> >>> Atlas team >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert at ripe.net Mon Mar 19 17:51:34 2012 From: robert at ripe.net (Robert Kisteleki) Date: Mon, 19 Mar 2012 17:51:34 +0100 Subject: [atlas] Request to test TCP and UDP to the root servers separately. In-Reply-To: <20120226153649.GA85511@ussenterprise.ufp.org> References: <20120224204130.GA86727@ussenterprise.ufp.org> <4F48AE90.2000507@ripe.net> <20120226153649.GA85511@ussenterprise.ufp.org> Message-ID: <4F676416.30105@ripe.net> Hello, This is an older thread, but since we made some enhancements in the meantime, it could be worth picking it up again. On 2012.02.26. 16:36, Leo Bicknell wrote: > In a message written on Sat, Feb 25, 2012 at 10:49:04AM +0100, Philip Homburg wrote: >> On 2/24/12 21:41 , Leo Bicknell wrote: >>> Would it be of interest to the Atlas community to have the probes >>> try and query "." via both UDP and TDP from each of the 13 root >>> servers (perhaps v4 and v6 separately), report back that data, and >>> then generate a report on the results? I would be happy to assist >>> in preparing or presenting a report on the results! >>> >> The probes are already measuring this. I don't think we made any graphs >> of the results. In case you've missed the recent announcement: we're now visualising more of the "latest DNS root measurements" here: https://atlas.ripe.net/contrib/root_anycast.html?msm_id=1 Basically, we do queries from all the probes for the serial in the SOA to all root servers, over IPv4 and IPv6, using UDP and TCP. The above visualisation now shows these too. We also have all the historical results of these. Taking this into account: > I'm not sure a graph would be the best representation of this data. The > interesting questions to me are: > > - Compare Failure Levels > - What is the overall level of UDP failure? > - What is the overall level of UDP+EDNS0 failure? > - What is the overall level of TCP failure? TCP+UDP are possible, EDNS0 not yet. > - Exploring the differences in the ecosystem > - Is there a statistical difference in the failure rate between IPv4 and > IPv6? (Are we getting better or worse) > - Is there a statistical difference in the failure rate between two > different root servers? (Does the root server deployment model > matter) > - What is the difference in response time of TCP queries compared to UDP > queries? (What's the penalty to fall back to TCP) These are also possible. It's not trivial, as there are some artefacts to be taken into consideration (anycast instance switches, some nodes not responding to some queries, etc.), but it is possible in general. We're not yet ready with the Atlas data sharing facility, but the data is available on request. Let us know if you're really interested in doing this analysis. We can also discuss this at the upcoming RIPE meeting, with whoever is there :-) Cheers, Robert From bicknell at ufp.org Fri Mar 23 15:30:15 2012 From: bicknell at ufp.org (Leo Bicknell) Date: Fri, 23 Mar 2012 07:30:15 -0700 Subject: [atlas] Request to test TCP and UDP to the root servers separately. In-Reply-To: <4F676416.30105@ripe.net> References: <20120224204130.GA86727@ussenterprise.ufp.org> <4F48AE90.2000507@ripe.net> <20120226153649.GA85511@ussenterprise.ufp.org> <4F676416.30105@ripe.net> Message-ID: <20120323143015.GB85652@ussenterprise.ufp.org> In a message written on Mon, Mar 19, 2012 at 05:51:34PM +0100, Robert Kisteleki wrote: > In case you've missed the recent announcement: we're now visualising more of > the "latest DNS root measurements" here: > https://atlas.ripe.net/contrib/root_anycast.html?msm_id=1 Yep, awesome stuff. A third data set would be very interesting for the map, which is for all probes that have both IPv4 and IPv6 connectivity plot "IPv6 RTT - IPv4 RTT". In an ideal world it would be a bunch of zero's, but we don't live in that world yet! > We're not yet ready with the Atlas data sharing facility, but the data is > available on request. Let us know if you're really interested in doing this > analysis. We can also discuss this at the upcoming RIPE meeting, with > whoever is there :-) I would be interested in digging in deeper, there are some specific questions we would like to know the answers to as the operators of F-Root, and the community may be interested in some of the same questions. I'm not going to be at RIPE this time around, so you'll have to let me know what to do in e-mail. :) -- Leo Bicknell - bicknell at ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/ From BECHA at ripe.net Mon Mar 26 13:40:42 2012 From: BECHA at ripe.net (Vesna Manojlovic) Date: Mon, 26 Mar 2012 13:40:42 +0200 Subject: [atlas] Altas switching to "RIPE NCC Access" Message-ID: <4F7055BA.5000707@ripe.net> Dear Atlas people, Tomorrow during the day we'll switch RIPE Atlas to use RIPE NCC Access, our Single-Sing-On mechanism. Maintenance will happen during our working hours (9-5, Amsterdam time), and it will last between 1 and 3 hours. During this, Atlas login will be disabled. The Atlas web site will have limited functionality. After the completed maintenance, the "log in" link on Atlas web site will be re-directed to the RIPE NCC Access log-in page. For other possible outcomes on this migration, please read Robert's article: https://labs.ripe.net/Members/kistel/preparing-ripe-atlas-for-ripe-ncc-access Single-Sign-On functionality will enable us to share Atlas with the users of other RIPE NCC services; it will make the user-experience smoother for everyone who is accessing multiple services from the RIPE NCC (such as LIR Portal, RIPE Labs or RIPEstat), and will enable many new personalized features in the future. If you have any questions, please let us know. Thank you, Vesna From carsten at schiefner.de Mon Mar 26 14:25:46 2012 From: carsten at schiefner.de (Carsten Schiefner) Date: Mon, 26 Mar 2012 14:25:46 +0200 Subject: [atlas] Altas switching to "RIPE NCC Access" In-Reply-To: <4F7055BA.5000707@ripe.net> References: <4F7055BA.5000707@ripe.net> Message-ID: <4F70604A.7080108@schiefner.de> Hi Vesna, On 26.03.2012 13:40, Vesna Manojlovic wrote: > Dear Atlas people, > > Tomorrow during the day we'll switch RIPE Atlas to use RIPE NCC Access, > our Single-Sing-On mechanism. "Single-Sing-On"... as opposite to being part of a chorus? ;-) Best, -C. From BECHA at ripe.net Mon Mar 26 14:46:57 2012 From: BECHA at ripe.net (Vesna Manojlovic) Date: Mon, 26 Mar 2012 14:46:57 +0200 Subject: [atlas] Altas switching to "RIPE NCC Access" In-Reply-To: <4F70604A.7080108@schiefner.de> References: <4F7055BA.5000707@ripe.net> <4F70604A.7080108@schiefner.de> Message-ID: <4F706541.3030901@ripe.net> Hi, it's Monday.. very early start of the week.. and the switch to "Summer Time"... so please be gentle to me & my spelling mistakes... On 3/26/12 2:25 PM, Carsten Schiefner wrote: > Hi Vesna, > > On 26.03.2012 13:40, Vesna Manojlovic wrote: >> Dear Atlas people, >> >> Tomorrow during the day we'll switch RIPE Atlas to use RIPE NCC Access, >> our Single-Sing-On mechanism. > > "Single-Sing-On"... as opposite to being part of a chorus? ;-) Oh! I did notice, but too late :( It's a single siGN on, of course... as opposed to not being single ;-) Also: in the subject line, I was wondering why is the spell-checker showing red ... and it says "aLtas" instead of Atlas... Ah well ;-) Vesna From rbarnes at bbn.com Mon Mar 26 14:40:57 2012 From: rbarnes at bbn.com (Richard L. Barnes) Date: Mon, 26 Mar 2012 14:40:57 +0200 Subject: [atlas] Altas switching to "RIPE NCC Access" In-Reply-To: <4F70604A.7080108@schiefner.de> References: <4F7055BA.5000707@ripe.net> <4F70604A.7080108@schiefner.de> Message-ID: <4F7063D9.2040606@bbn.com> Much better authentication scheme than passwords! On 3/26/12 2:25 PM, Carsten Schiefner wrote: > Hi Vesna, > > On 26.03.2012 13:40, Vesna Manojlovic wrote: >> Dear Atlas people, >> >> Tomorrow during the day we'll switch RIPE Atlas to use RIPE NCC Access, >> our Single-Sing-On mechanism. > > "Single-Sing-On"... as opposite to being part of a chorus? ;-) > > Best, > > -C. > From colinj at mx5.org.uk Tue Mar 27 20:10:56 2012 From: colinj at mx5.org.uk (Colin Johnston) Date: Tue, 27 Mar 2012 19:10:56 +0100 Subject: [atlas] Altas switching to "RIPE NCC Access" In-Reply-To: <4F7055BA.5000707@ripe.net> References: <4F7055BA.5000707@ripe.net> Message-ID: <4708C145-D909-415F-B069-F6A7FDE879FE@mx5.org.uk> seemed to work well this evening and updated password fine Colin On 26 Mar 2012, at 12:40, Vesna Manojlovic wrote: > Dear Atlas people, > > Tomorrow during the day we'll switch RIPE Atlas to use RIPE NCC Access, our Single-Sing-On mechanism. > > Maintenance will happen during our working hours (9-5, Amsterdam time), and it will last between 1 and 3 hours. > > During this, Atlas login will be disabled. > The Atlas web site will have limited functionality. > > After the completed maintenance, the "log in" link on Atlas web site will be re-directed to the RIPE NCC Access log-in page. > > For other possible outcomes on this migration, > please read Robert's article: > https://labs.ripe.net/Members/kistel/preparing-ripe-atlas-for-ripe-ncc-access > > Single-Sign-On functionality will enable us to share Atlas with the users of other RIPE NCC services; it will make the user-experience smoother for everyone who is accessing multiple services from the RIPE NCC (such as LIR Portal, RIPE Labs or RIPEstat), and will enable many new personalized features in the future. > > If you have any questions, please let us know. > > Thank you, > Vesna > > > From ttsak at hotmail.com Thu Mar 29 21:45:24 2012 From: ttsak at hotmail.com (Thanos Tsakalos) Date: Thu, 29 Mar 2012 22:45:24 +0300 Subject: [atlas] change ownership of probe Message-ID: Hello to all, Is there a way to change the ownership of a probe? Will it be ok if the probe is re-registered under the new email address (mac and pin are known) ? Or is there any other method to do it properly? Thank you, Triantafyllos -------------- next part -------------- An HTML attachment was scrubbed... URL: From colinj at mx5.org.uk Sat Mar 31 10:05:21 2012 From: colinj at mx5.org.uk (Colin Johnston) Date: Sat, 31 Mar 2012 09:05:21 +0100 Subject: [atlas] Probe 2317 is down In-Reply-To: <20120331073002.27416.85460@Debian-50-lenny-64-minimal> References: <20120331073002.27416.85460@Debian-50-lenny-64-minimal> Message-ID: fixed internal network :) Can a request for enhancement be made for notification of probe goes up to the owner email ? Colin On 31 Mar 2012, at 08:30, RIPE Atlas wrote: > Dear colin, > > Your probe 2317 is down since 2012-03-31 06:56:49 UTC > > This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe goes is down for more than 30 minutes. > > If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/atlas/myprobes.html, click on probe 2317, in the opened tab select Probe's Settings -> Notifications and change your settings. > > Atlas team