From robert at ripe.net Tue Nov 9 10:17:04 2010 From: robert at ripe.net (Robert Kisteleki) Date: Tue, 09 Nov 2010 10:17:04 +0100 Subject: [atlas]Upgrades today Message-ID: <4CD91190.5090200@ripe.net> Hi, We're doing some major upgrades today on the RIPE Atlas network, both on the central architecture and on the probes. It's expected that during this time probes will disconnect. Regards, Robert From robert at ripe.net Tue Nov 9 21:22:55 2010 From: robert at ripe.net (Robert Kisteleki) Date: Tue, 09 Nov 2010 21:22:55 +0100 Subject: [atlas]Upgrades today In-Reply-To: <4CD91190.5090200@ripe.net> References: <4CD91190.5090200@ripe.net> Message-ID: <4CD9AD9F.4000504@ripe.net> On 2010.11.09. 10:17, Robert Kisteleki wrote: > Hi, > > We're doing some major upgrades today on the RIPE Atlas network, both on the > central architecture and on the probes. It's expected that during this time > probes will disconnect. > > Regards, > Robert > Dear All, This upgrade is finished now. Some of the results are: 1. Your very own "probe status" page is now available! Just click on your probe in the list (well... most likely a list of one, but still) and another tab will open with more details about the probe. All the graphs are clickable on this page. They show the history of the specific item (ping measurement). 2. You can now set the probe's details (geolocation and description) using the butting in the top right corner of the probe status page. 3. All currently known probes will do an automatic firmware update somewhere in the next 12 hours. (As of now, about one third of them have already done this.) You don't have to do anything about this. The new firmware (version 3820) has: a) the ability to continuously ping the first two "hops" (as in a traceroute) on IPv4; b) improved resilience against disconnects; c) improved internal security properties. You can check if your probe has already been updated by visiting the probe status page and looking at the "firmware version" at the top. If you have questions or concerns you can write a mail to this public list, or to atlas-dev at ripe.net (developer's list). Regards, Robert -- Robert Kisteleki, Science Group Manager, RIPE NCC RIPE Atlas Team From henk at uijterwaal.nl Wed Nov 10 09:07:57 2010 From: henk at uijterwaal.nl (Henk Uijterwaal) Date: Wed, 10 Nov 2010 09:07:57 +0100 Subject: [atlas]Upgrades today In-Reply-To: <4CD9AD9F.4000504@ripe.net> References: <4CD91190.5090200@ripe.net> <4CD9AD9F.4000504@ripe.net> Message-ID: <4CDA52DD.4040105@uijterwaal.nl> Hi, > 2. You can now set the probe's details (geolocation and description) using > the butting in the top right corner of the probe status page. I'm having a problem with that. When I enter "Rozendaal", it only knows about this place in Zuid Holland, not the one where I live. I then took out my GPS and copied the coordinates from there. However, the GPS gives {N|S|E|W}degrees:minutes:seconds, how do I correctly enter that? Third attemp: move the arrow on the map. However, one can enlarge the map but not move it around. The arrow starts in the wrong place, where I live is off the map. > 3. All currently known probes will do an automatic firmware update somewhere > in the next 12 hours. (As of now, about one third of them have already done > this.) You don't have to do anything about this. The new firmware (version > 3820) has: > a) the ability to continuously ping the first two "hops" (as in a > traceroute) on IPv4; OK, so it is now probing the router (192.168.0.1) and firewall (10.0.0.138), which isn't very useful (they are in the same cabinet, +/- 1 m apart). I agree that my setup is a bit unusual, but still, I don't think that pinging 10.0.0.138 (the default of any adsl modem) is usual. Would it be an idea to exclude 192.168/16 and 10/8 from the ping list? Henk -- ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.xs4all.nl/~henku P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ I confirm today what I denied yesterday. Anonymous Politician. From robert at ripe.net Wed Nov 10 09:54:51 2010 From: robert at ripe.net (Robert Kisteleki) Date: Wed, 10 Nov 2010 09:54:51 +0100 Subject: [atlas]Upgrades today In-Reply-To: <4CDA52DD.4040105@uijterwaal.nl> References: <4CD91190.5090200@ripe.net> <4CD9AD9F.4000504@ripe.net> <4CDA52DD.4040105@uijterwaal.nl> Message-ID: <4CDA5DDB.4040208@ripe.net> On 2010.11.10. 9:07, Henk Uijterwaal wrote: > Hi, > >> 2. You can now set the probe's details (geolocation and description) using >> the butting in the top right corner of the probe status page. > > I'm having a problem with that. When I enter "Rozendaal", it only knows > about this place in Zuid Holland, not the one where I live. I then took > out my GPS and copied the coordinates from there. However, the GPS > gives {N|S|E|W}degrees:minutes:seconds, how do I correctly enter that? > Third attemp: move the arrow on the map. However, one can enlarge the > map but not move it around. The arrow starts in the wrong place, where I > live is off the map. We're using WorldDB (http://code.google.com/p/worlddb/) as a back end for this. It's a pity if it doesn't know about your town :-) For the time being you can choose a closeby town. We'll switch to a better geolocation API a bit later. In any case, you can move around the pin on the map, and the coordinates should change accordingly. Let us know (to atlas-dev at ripe.net) if they don't, so that we can figure out what the problem is. >> 3. All currently known probes will do an automatic firmware update somewhere >> in the next 12 hours. (As of now, about one third of them have already done >> this.) You don't have to do anything about this. The new firmware (version >> 3820) has: >> a) the ability to continuously ping the first two "hops" (as in a >> traceroute) on IPv4; > > OK, so it is now probing the router (192.168.0.1) and firewall (10.0.0.138), > which isn't very useful (they are in the same cabinet, +/- 1 m apart). I > agree that my setup is a bit unusual, but still, I don't think that pinging > 10.0.0.138 (the default of any adsl modem) is usual. Would it be an idea > to exclude 192.168/16 and 10/8 from the ping list? For now we're doing the first two hops, whatever they are. It' possible that later on we'll allow hosts to make such exceptions. Regards, Robert > Henk From bertietf at bwijnen.net Wed Nov 10 07:27:20 2010 From: bertietf at bwijnen.net (Bert (IETF) Wijnen) Date: Wed, 10 Nov 2010 14:27:20 +0800 Subject: [atlas]is this correct Message-ID: <4CDA3B48.4090207@bwijnen.net> looking at "Last 25 connections", I vaguely suspect that this is somehow not correct (at least not what I expected) Bert *Current status:* Up since 2010-11-09 19:23:06 UTC *Total Uptime:* 20d, 17h, 7m Show last 25 connections Hide last 25 connections *Connect at:* *Disconnect at:* 2010-11-09 19:23:06 UTC (still connected) 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: green_check2.jpg Type: image/jpeg Size: 2314 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: plus.png Type: image/png Size: 4080 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: minus.png Type: image/png Size: 4066 bytes Desc: not available URL: From daniel.karrenberg at ripe.net Wed Nov 10 09:56:02 2010 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Wed, 10 Nov 2010 09:56:02 +0100 Subject: [atlas]Upgrades today In-Reply-To: <4CDA52DD.4040105@uijterwaal.nl> References: <4CD91190.5090200@ripe.net> <4CD9AD9F.4000504@ripe.net> <4CDA52DD.4040105@uijterwaal.nl> Message-ID: <20101110085602.GU43414@reifripenet.local> On 10.11 09:07, Henk Uijterwaal wrote: > Hi, > > > 2. You can now set the probe's details (geolocation and description) using > > the butting in the top right corner of the probe status page. > > I'm having a problem with that. When I enter "Rozendaal", it only knows > about this place in Zuid Holland, not the one where I live. I then took > out my GPS and copied the coordinates from there. However, the GPS > gives {N|S|E|W}degrees:minutes:seconds, how do I correctly enter that? > Third attemp: move the arrow on the map. However, one can enlarge the > map but not move it around. The arrow starts in the wrong place, where I > live is off the map. We will improve that. My soloution was to use approximate decimal LAT/LONG and then I could use the map. BTW: My birthplace Duesseldorf, a twon with >400k people is not in there either, neither in the form of Dusseldorf or with the umlaut. > > 3. All currently known probes will do an automatic firmware update somewhere > > in the next 12 hours. (As of now, about one third of them have already done > > this.) You don't have to do anything about this. The new firmware (version > > 3820) has: > > a) the ability to continuously ping the first two "hops" (as in a > > traceroute) on IPv4; > > OK, so it is now probing the router (192.168.0.1) and firewall (10.0.0.138), > which isn't very useful (they are in the same cabinet, +/- 1 m apart). I > agree that my setup is a bit unusual, but still, I don't think that pinging > 10.0.0.138 (the default of any adsl modem) is usual. Would it be an idea > to exclude 192.168/16 and 10/8 from the ping list? We want the first couple of hops, because it will provide us with a crude way of compensating for user traffic. Daniel From astrikos at ripe.net Wed Nov 10 10:04:54 2010 From: astrikos at ripe.net (Andreas Strikos) Date: Wed, 10 Nov 2010 10:04:54 +0100 Subject: [atlas]is this correct In-Reply-To: <4CDA3B48.4090207@bwijnen.net> References: <4CDA3B48.4090207@bwijnen.net> Message-ID: <734EC826-DC1E-4849-B62E-6DE638C05C6F@ripe.net> Hi Bert, it's definitely not correct. I am trying to find out what went wrong there for your probe and i'll will let you know /Andreas On Nov 10, 2010, at 7:27 AM, Bert (IETF) Wijnen wrote: > looking at "Last 25 connections", I vaguely suspect that this > is somehow not correct (at least not what I expected) > > Bert > > Current status: Up since 2010-11-09 19:23:06 UTC > Total Uptime: 20d, 17h, 7m > Hide last 25 connections > Connect at: Disconnect at: > 2010-11-09 19:23:06 UTC (still connected) > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC -------------- next part -------------- An HTML attachment was scrubbed... URL: From astrikos at ripe.net Wed Nov 10 10:57:24 2010 From: astrikos at ripe.net (Andreas Strikos) Date: Wed, 10 Nov 2010 10:57:24 +0100 Subject: [atlas]is this correct In-Reply-To: <734EC826-DC1E-4849-B62E-6DE638C05C6F@ripe.net> References: <4CDA3B48.4090207@bwijnen.net> <734EC826-DC1E-4849-B62E-6DE638C05C6F@ripe.net> Message-ID: Fixed, we had on little exception somewhere but now everything back to normal /Andreas On Nov 10, 2010, at 10:04 AM, Andreas Strikos wrote: > Hi Bert, > > it's definitely not correct. I am trying to find out what went wrong there for your probe and i'll will let you know > > /Andreas > On Nov 10, 2010, at 7:27 AM, Bert (IETF) Wijnen wrote: > >> looking at "Last 25 connections", I vaguely suspect that this >> is somehow not correct (at least not what I expected) >> >> Bert >> >> Current status: Up since 2010-11-09 19:23:06 UTC >> Total Uptime: 20d, 17h, 7m >> Hide last 25 connections >> Connect at: Disconnect at: >> 2010-11-09 19:23:06 UTC (still connected) >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC > -------------- next part -------------- An HTML attachment was scrubbed... URL: From henk at uijterwaal.nl Wed Nov 10 11:24:54 2010 From: henk at uijterwaal.nl (Henk Uijterwaal) Date: Wed, 10 Nov 2010 11:24:54 +0100 Subject: [atlas]Upgrades today In-Reply-To: <4CDA5DDB.4040208@ripe.net> References: <4CD91190.5090200@ripe.net> <4CD9AD9F.4000504@ripe.net> <4CDA52DD.4040105@uijterwaal.nl> <4CDA5DDB.4040208@ripe.net> Message-ID: <4CDA72F6.4070803@uijterwaal.nl> Hi, > In any case, you can move around the pin on the map, and the coordinates > should change accordingly. Let us know (to atlas-dev at ripe.net) if they > don't, so that we can figure out what the problem is. Usually Google Maps has a round button that allows you to scroll the map. Not this one. I got a map with a pointer in the middle, that did not include the place where I live. If I made the map smaller, it was impossible to see where to put it. If I moved the pointer east, I reached the end of the map but then couldn't go further. (It is probably easier if we sat down in front of a computer and I could show this to you). > For now we're doing the first two hops, whatever they are. It' possible that > later on we'll allow hosts to make such exceptions. Which accomplishes what? Ping the gateway does not tell you much, in particular on home networks which are quiet most of the day. Changing to hop 2 and 3 would already be an improvement. Henk -- ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.xs4all.nl/~henku P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ I confirm today what I denied yesterday. Anonymous Politician. From astrikos at ripe.net Wed Nov 10 11:40:31 2010 From: astrikos at ripe.net (Andreas Strikos) Date: Wed, 10 Nov 2010 11:40:31 +0100 Subject: [atlas]is this correct In-Reply-To: <4CDA70A0.5030306@bwijnen.net> References: <4CDA3B48.4090207@bwijnen.net> <734EC826-DC1E-4849-B62E-6DE638C05C6F@ripe.net> <4CDA70A0.5030306@bwijnen.net> Message-ID: <90A3D5BB-1109-4DC8-9EA6-71736976D3F8@ripe.net> Yes you right, i missed some duplicates caused by the exception, after deleting them it looks better now... /Andreas On Nov 10, 2010, at 11:14 AM, Bert (IETF) Wijnen wrote: > Adreas, it looks a bit better now. But at the bottom of my > list I still see a lot of duplicates. > > I am also wondering if it would be better to sort then in > reverse chronological order. Now it looks as if there is > no (obvious) sorting sequence. > > Bert > > > On 11/10/10 5:57 PM, Andreas Strikos wrote: >> >> Fixed, >> >> we had on little exception somewhere but now everything back to normal >> >> /Andreas >> On Nov 10, 2010, at 10:04 AM, Andreas Strikos wrote: >> >>> Hi Bert, >>> >>> it's definitely not correct. I am trying to find out what went wrong there for your probe and i'll will let you know >>> >>> /Andreas >>> On Nov 10, 2010, at 7:27 AM, Bert (IETF) Wijnen wrote: >>> >>>> looking at "Last 25 connections", I vaguely suspect that this >>>> is somehow not correct (at least not what I expected) >>>> >>>> Bert >>>> >>>> Current status: Up since 2010-11-09 19:23:06 UTC >>>> Total Uptime: 20d, 17h, 7m >>>> Hide last 25 connections >>>> Connect at: Disconnect at: >>>> 2010-11-09 19:23:06 UTC (still connected) >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bertietf at bwijnen.net Wed Nov 10 11:14:56 2010 From: bertietf at bwijnen.net (Bert (IETF) Wijnen) Date: Wed, 10 Nov 2010 18:14:56 +0800 Subject: [atlas]is this correct In-Reply-To: References: <4CDA3B48.4090207@bwijnen.net> <734EC826-DC1E-4849-B62E-6DE638C05C6F@ripe.net> Message-ID: <4CDA70A0.5030306@bwijnen.net> Adreas, it looks a bit better now. But at the bottom of my list I still see a lot of duplicates. I am also wondering if it would be better to sort then in reverse chronological order. Now it looks as if there is no (obvious) sorting sequence. Bert On 11/10/10 5:57 PM, Andreas Strikos wrote: > Fixed, > > we had on little exception somewhere but now everything back to normal > > /Andreas > On Nov 10, 2010, at 10:04 AM, Andreas Strikos wrote: > >> Hi Bert, >> >> it's definitely not correct. I am trying to find out what went wrong there for your probe and i'll will let you know >> >> /Andreas >> On Nov 10, 2010, at 7:27 AM, Bert (IETF) Wijnen wrote: >> >>> looking at "Last 25 connections", I vaguely suspect that this >>> is somehow not correct (at least not what I expected) >>> >>> Bert >>> >>> *Current status:* Up since 2010-11-09 19:23:06 UTC >>> *Total Uptime:* 20d, 17h, 7m >>> >>> Show last 25 connections >>> Hide last 25 connections >>> >>> *Connect at:* *Disconnect at:* >>> 2010-11-09 19:23:06 UTC (still connected) >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> 2010-11-05 09:53:28 UTC 2010-11-05 21:53:31 UTC >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From henk at uijterwaal.nl Wed Nov 10 12:50:00 2010 From: henk at uijterwaal.nl (Henk Uijterwaal) Date: Wed, 10 Nov 2010 12:50:00 +0100 Subject: [atlas]Upgrades today In-Reply-To: <4CDA7FCC.60208@ripe.net> References: <4CD91190.5090200@ripe.net> <4CD9AD9F.4000504@ripe.net> <4CDA52DD.4040105@uijterwaal.nl> <4CDA7FCC.60208@ripe.net> Message-ID: <4CDA86E8.3050606@uijterwaal.nl> On 10/11/2010 12:19, Rene Wilhelm wrote: > On 11/10/10 9:07 AM, Henk Uijterwaal wrote: >> Hi, >> >>> 2. You can now set the probe's details (geolocation and description) using >>> the butting in the top right corner of the probe status page. >> I'm having a problem with that. When I enter "Rozendaal", it only knows >> about this place in Zuid Holland, not the one where I live. I then took >> out my GPS and copied the coordinates from there. However, the GPS >> gives {N|S|E|W}degrees:minutes:seconds, how do I correctly enter that? > Use a calculator :-) Well, I know how to convert from one system to another, I don't know what format is expected. (And, FWIW, Google maps can create a link based on entering an address that includes the Lat/Long information. Probably the easiest would be to ask people to enter their address). Henk -- ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.xs4all.nl/~henku P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ I confirm today what I denied yesterday. Anonymous Politician. From wilhelm at ripe.net Wed Nov 10 12:19:40 2010 From: wilhelm at ripe.net (Rene Wilhelm) Date: Wed, 10 Nov 2010 12:19:40 +0100 Subject: [atlas]Upgrades today In-Reply-To: <4CDA52DD.4040105@uijterwaal.nl> References: <4CD91190.5090200@ripe.net> <4CD9AD9F.4000504@ripe.net> <4CDA52DD.4040105@uijterwaal.nl> Message-ID: <4CDA7FCC.60208@ripe.net> On 11/10/10 9:07 AM, Henk Uijterwaal wrote: > Hi, > >> 2. You can now set the probe's details (geolocation and description) using >> the butting in the top right corner of the probe status page. > I'm having a problem with that. When I enter "Rozendaal", it only knows > about this place in Zuid Holland, not the one where I live. I then took > out my GPS and copied the coordinates from there. However, the GPS > gives {N|S|E|W}degrees:minutes:seconds, how do I correctly enter that? Use a calculator :-) My GPS reports coordinates in this way: N52 22.366 E4 53.308 i.e. degrees and decimal minutes (no seconds). To convert that to true decimal degrees, as expected by atlas, you divide the minutes by 60 and add that to the degrees value. So the above becomes: 52 + 22.366/60 = 52.37277 4 + 53.308/60 = 4.88847 Those would be the numbers to enter in the page for the probe at/near this location (leaving it as an excercise to the interested reader to find out where that is :) -- Rene From Woeber at CC.UniVie.ac.at Tue Nov 23 13:58:28 2010 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Tue, 23 Nov 2010 12:58:28 +0000 Subject: [atlas]warning pop-up in IE for the various atlas-related pages Message-ID: <4CEBBA74.30409@CC.UniVie.ac.at> Folks, I noticed that I have to ack a warning pop-up (served by IE7 ;-) ) for each page that is realted to the atlas stuff. IE complains about a mix of secured and unsecured components on the page. In principle I'd prefer continuing with httpS, but the warnings are a real nuisance. Anyone else seeing this? Btw, the Labs stuff shows the same behaviour. Wilfried. From Woeber at CC.UniVie.ac.at Tue Nov 23 13:55:01 2010 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Tue, 23 Nov 2010 12:55:01 +0000 Subject: [atlas]labeling the axes in the graphs Message-ID: <4CEBB9A5.2060808@CC.UniVie.ac.at> Dear probe hosts and "herders", a couple of first experiences and thoughts... While I know that RTT is measured in "time" rather than distance, I was slightly detracted in the beginning by he use of "m" as the abbreviation for milli seconds. I guess there would be enough room in the graphs to use "ms"? Maybe it is just me :-) Wilfried. From robert at ripe.net Tue Nov 23 18:37:50 2010 From: robert at ripe.net (Robert Kisteleki) Date: Tue, 23 Nov 2010 18:37:50 +0100 Subject: [atlas]warning pop-up in IE for the various atlas-related pages In-Reply-To: <4CEBBA74.30409@CC.UniVie.ac.at> References: <4CEBBA74.30409@CC.UniVie.ac.at> Message-ID: <4CEBFBEE.7020300@ripe.net> On 2010.11.23. 13:58, Wilfried Woeber, UniVie/ACOnet wrote: > Folks, I noticed that I have to ack a warning pop-up (served by IE7 ;-) ) > for each page that is realted to the atlas stuff. IE complains about a > mix of secured and unsecured components on the page. > > In principle I'd prefer continuing with httpS, but the warnings are a real > nuisance. Why are you using a browser that annoys you? :-) > Anyone else seeing this? Btw, the Labs stuff shows the same behaviour. That's in fact the case (mixed content) if you use https - some stuff comes from external sites (like Google Maps scripts) without https. Other browsers have more user friendly mechanisms though. Robert > Wilfried. From Woeber at CC.UniVie.ac.at Tue Nov 23 18:41:32 2010 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Tue, 23 Nov 2010 17:41:32 +0000 Subject: [atlas]warning pop-up in IE for the various atlas-related pages In-Reply-To: <4CEBFBEE.7020300@ripe.net> References: <4CEBBA74.30409@CC.UniVie.ac.at> <4CEBFBEE.7020300@ripe.net> Message-ID: <4CEBFCCC.7000904@CC.UniVie.ac.at> Robert Kisteleki wrote: [...] > Why are you using a browser that annoys you? :-) That was a nice one :-) >>Anyone else seeing this? Btw, the Labs stuff shows the same behaviour. Iceweasel on Debian Linux does the same, btw, just checked... > That's in fact the case (mixed content) if you use https - some stuff comes > from external sites (like Google Maps scripts) without https. Other browsers > have more user friendly mechanisms though. Suggestions? ;-) > Robert Wilfried. From daniel.karrenberg at ripe.net Tue Nov 23 18:44:35 2010 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Tue, 23 Nov 2010 18:44:35 +0100 Subject: [atlas]warning pop-up in IE for the various atlas-related pages In-Reply-To: <4CEBFCCC.7000904@CC.UniVie.ac.at> References: <4CEBBA74.30409@CC.UniVie.ac.at> <4CEBFBEE.7020300@ripe.net> <4CEBFCCC.7000904@CC.UniVie.ac.at> Message-ID: <20101123174435.GO2939@reifripenet.local> On 23.11 17:41, Wilfried Woeber, UniVie/ACOnet wrote: > Robert Kisteleki wrote: > > [...] > > Why are you using a browser that annoys you? :-) > > That was a nice one :-) > > >>Anyone else seeing this? Btw, the Labs stuff shows the same behaviour. > > Iceweasel on Debian Linux does the same, btw, just checked... > > > That's in fact the case (mixed content) if you use https - some stuff comes > > from external sites (like Google Maps scripts) without https. Other browsers > > have more user friendly mechanisms though. > > Suggestions? ;-) firefox, chrome, safari Daniel From Woeber at CC.UniVie.ac.at Tue Nov 23 18:53:26 2010 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Tue, 23 Nov 2010 17:53:26 +0000 Subject: [atlas]IPv4 and IPv6 to the same machine(s)... Message-ID: <4CEBFF96.6030209@CC.UniVie.ac.at> How much effort would it be to add a test and the graph to labs.ripe.net on IPv6? Just checked, it still has an IPv6 address. Btw, Mirjam (on bcc:), the new Labs site does no longer show the address for the incoming connection. Could this be re-instated, please? If possible it should go to somewhere in the header, like next to the login-name... On a more general aspect, I am looking for a good idea to present the measurement data for the same machine(s) for v4 and v6 either in the same graph "on top of each other" or "next to each other"... This could easily evolve into a graphical v6-sanity-check vehicle :-) Wilfried. From daniel.karrenberg at ripe.net Tue Nov 23 18:59:22 2010 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Tue, 23 Nov 2010 18:59:22 +0100 Subject: [atlas]IPv4 and IPv6 to the same machine(s)... In-Reply-To: <4CEBFF96.6030209@CC.UniVie.ac.at> References: <4CEBFF96.6030209@CC.UniVie.ac.at> Message-ID: <20101123175922.GS2939@reifripenet.local> On 23.11 17:53, Wilfried Woeber, UniVie/ACOnet wrote: > How much effort would it be to add a test and the graph to > labs.ripe.net on IPv6? Just checked, it still has an IPv6 address. The effort is minimal, however the current "design" of the firmware restricts the number of targets we can reliably ping. Bear with us for a few weeks until we have a more reliable design ready to deploy. > On a more general aspect, I am looking for a good idea to present the > measurement data for the same machine(s) for v4 and v6 either in the > same graph "on top of each other" or "next to each other"... > > This could easily evolve into a graphical v6-sanity-check vehicle :-) Makes absolute sense. We will put that on the 'idea stack'. From nuno.vieira at nfsi.pt Wed Nov 24 10:24:42 2010 From: nuno.vieira at nfsi.pt (Nuno Vieira - nfsi telecom) Date: Wed, 24 Nov 2010 09:24:42 +0000 (WET) Subject: [atlas]probe appears down on atlas.ripe.net Message-ID: <910081412.1408.1290590682943.JavaMail.root@zimbra.nfsi.pt> Hello, I have deployed one probe and it has been up since a few hours ago. I checked this morning and it was down. The thing is, i can ping properly the probe on IPv4 and IPv6, and i see traffic comming in and out. We did not changed anything on the network/firewall to prevent traffic. What could be the problem ? regards, --nvieira -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.karrenberg at ripe.net Wed Nov 24 10:39:39 2010 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Wed, 24 Nov 2010 10:39:39 +0100 Subject: [atlas]probe appears down on atlas.ripe.net In-Reply-To: <910081412.1408.1290590682943.JavaMail.root@zimbra.nfsi.pt> References: <910081412.1408.1290590682943.JavaMail.root@zimbra.nfsi.pt> Message-ID: <20101124093939.GC12202@ip212-238-47-12.hotspotsvankpn.com> On 24.11 09:24, Nuno Vieira - nfsi telecom wrote: > The thing is, i can ping properly the probe on IPv4 and IPv6, and i see traffic comming in and out. > We did not changed anything on the network/firewall to prevent traffic. > > What could be the problem ? We will look into it today. Daniel From Woeber at CC.UniVie.ac.at Wed Nov 24 11:00:19 2010 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Wed, 24 Nov 2010 10:00:19 +0000 Subject: [atlas]internal timing constraints? Message-ID: <4CECE233.9000500@CC.UniVie.ac.at> Dear Atlas folks, do you have a rough estimate or data about the internal timing of the probes, like what sort of "delay" is added by the probe itself when measuring e.g. ping RTT? The background is that I get different readings or ping RTTs from the probe, compared to the "same" thing done from a regular PC running Linux and sitting on the very same subnet, connected to the very same (small) switch. The absolute difference I see is small (sub-millisecond), but it seems to be systematic. The ping target is a "local" instance of i.root, btw. Thanks, Wilfried. From mgrigore at ripe.net Wed Nov 24 10:43:39 2010 From: mgrigore at ripe.net (Mihnea-Costin Grigore) Date: Wed, 24 Nov 2010 10:43:39 +0100 Subject: [atlas]warning pop-up in IE for the various atlas-related pages In-Reply-To: <4CEBFCCC.7000904@CC.UniVie.ac.at> References: <4CEBBA74.30409@CC.UniVie.ac.at> <4CEBFBEE.7020300@ripe.net> <4CEBFCCC.7000904@CC.UniVie.ac.at> Message-ID: <4CECDE4B.7040809@ripe.net> On 23/11/2010 18:41, Wilfried Woeber, UniVie/ACOnet wrote: > Iceweasel on Debian Linux does the same, btw, just checked... >> That's in fact the case (mixed content) if you use https - some stuff comes >> from external sites (like Google Maps scripts) without https. Other browsers >> have more user friendly mechanisms though. > Suggestions? ;-) IceWeasel is actually de-branded Firefox, so it has the same settings -- under Preferences -> Security -> Warning Messages, the last one in the list controls this. Personally I disable all except the 'low-grade encryption' one, otherwise browsing in general is painful with lots of sites giving warnings. I know this is more of a workaround, however in the case of Atlas the 'clean' solution would involve serving all the content from just one virtual-host for SSL, and that is simply not attainable with the current architecture of the website(s). On a related note, I tested now and the login page does not automatically redirect to https:// if accessed by http://, and I think it should. That's for the security of anyone using the service... Best regards, -- Mihnea-Costin Grigore RIPE NCC Web Developer - http://ripe.net/ From daniel.karrenberg at ripe.net Wed Nov 24 11:26:15 2010 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Wed, 24 Nov 2010 11:26:15 +0100 Subject: [atlas]internal timing constraints? In-Reply-To: <4CECE233.9000500@CC.UniVie.ac.at> References: <4CECE233.9000500@CC.UniVie.ac.at> Message-ID: <20101124102615.GG12202@ip212-238-47-12.hotspotsvankpn.com> On 24.11 10:00, Wilfried Woeber, UniVie/ACOnet wrote: > Dear Atlas folks, > > do you have a rough estimate or data about the internal timing of the > probes, like what sort of "delay" is added by the probe itself when > measuring e.g. ping RTT? > > The background is that I get different readings or ping RTTs from the > probe, compared to the "same" thing done from a regular PC running Linux > and sitting on the very same subnet, connected to the very same (small) > switch. > > The absolute difference I see is small (sub-millisecond), but it seems > to be systematic. The ping target is a "local" instance of i.root, btw. Of course there is a difference. There are many factors that contribute to that: CPU speed, protocol stack implementation, ethernet interface implementation, time keeping and measuring differences. Then thee may be different payload sizes ... And of course that is systematic. Find an example here: https://labs.ripe.net/Members/dfk/ipv6-home/ipv6-home Measuring the bsolute systematic component for the Atlas probe is on my list. However, given that it is systemactic and the absolute size is small this will not happen anytime soon. Daniel From robert at ripe.net Wed Nov 24 11:34:39 2010 From: robert at ripe.net (Robert Kisteleki) Date: Wed, 24 Nov 2010 11:34:39 +0100 Subject: [atlas]warning pop-up in IE for the various atlas-related pages In-Reply-To: <4CECDE4B.7040809@ripe.net> References: <4CEBBA74.30409@CC.UniVie.ac.at> <4CEBFBEE.7020300@ripe.net> <4CEBFCCC.7000904@CC.UniVie.ac.at> <4CECDE4B.7040809@ripe.net> Message-ID: <4CECEA3F.7060505@ripe.net> On 2010.11.24. 10:43, Mihnea-Costin Grigore wrote: > I know this is more of a workaround, however in the case of Atlas the > 'clean' solution would involve serving all the content from just one > virtual-host for SSL, and that is simply not attainable with the current > architecture of the website(s). We have external content (Google Maps) for which we cannot depend on https. > On a related note, I tested now and the login page does not automatically > redirect to https:// if accessed by http://, and I think it should. That's > for the security of anyone using the service... Good point. Robert From wolfgang at garf.de Wed Nov 24 10:58:49 2010 From: wolfgang at garf.de (Wolfgang Tremmel) Date: Wed, 24 Nov 2010 10:58:49 +0100 Subject: [atlas]Graphs gone... Message-ID: <4CECE1D9.9010009@garf.de> Hello, Probe is up (and shows up) but all the graphs show empty since yesterday. best regards, Wolfgang From robert at ripe.net Wed Nov 24 11:48:23 2010 From: robert at ripe.net (Robert Kisteleki) Date: Wed, 24 Nov 2010 11:48:23 +0100 Subject: [atlas]Graphs gone... In-Reply-To: <4CECE1D9.9010009@garf.de> References: <4CECE1D9.9010009@garf.de> Message-ID: <4CECED77.7030405@ripe.net> On 2010.11.24. 10:58, Wolfgang Tremmel wrote: > Hello, > > Probe is up (and shows up) but all the graphs show empty since yesterday. > > best regards, > Wolfgang > We'll look into this. For future reference: when submitting such issues, I'd like to ask everyone to please mention your probe id (first column in the probe list), because it helps us a lot finding your probe. Thanks, Robert From Tjebbe at kanariepiet.com Wed Nov 24 11:52:47 2010 From: Tjebbe at kanariepiet.com (Jelte) Date: Wed, 24 Nov 2010 11:52:47 +0100 Subject: [atlas]Graphs gone... In-Reply-To: <4CECED77.7030405@ripe.net> References: <4CECE1D9.9010009@garf.de> <4CECED77.7030405@ripe.net> Message-ID: <4CECEE7F.8090707@kanariepiet.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/24/2010 11:48 AM, Robert Kisteleki wrote: > On 2010.11.24. 10:58, Wolfgang Tremmel wrote: >> Hello, >> >> Probe is up (and shows up) but all the graphs show empty since yesterday. >> >> best regards, >> Wolfgang >> > > We'll look into this. > > For future reference: when submitting such issues, I'd like to ask everyone > to please mention your probe id (first column in the probe list), because it > helps us a lot finding your probe. > This does not appear to be an isolated case, btw; the graphs for my probe (174), are also empty since about 23:40 yesterday. Jelte -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzs7n8ACgkQ4nZCKsdOncVcIQCgpZOkFHCgI3OmiPQqZ80hYmVi 6zcAn1xIEg/u19p2GlQ82A6qPBWsh/Bc =Ix7C -----END PGP SIGNATURE----- From Woeber at CC.UniVie.ac.at Wed Nov 24 13:53:19 2010 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Wed, 24 Nov 2010 12:53:19 +0000 Subject: [atlas]Graphs gone... In-Reply-To: <4CECEE7F.8090707@kanariepiet.com> References: <4CECE1D9.9010009@garf.de> <4CECED77.7030405@ripe.net> <4CECEE7F.8090707@kanariepiet.com> Message-ID: <4CED0ABF.9040403@CC.UniVie.ac.at> Jelte wrote: > On 11/24/2010 11:48 AM, Robert Kisteleki wrote: [...] > This does not appear to be an isolated case, btw; the graphs for my probe (174), > are also empty since about 23:40 yesterday. ("I" .eq. 414), too, am missing most of the graphs, but not all of them. I also noticed that "something" believes, that there was some outage of "exactly" 10 minutes: Connect at: Disconnect at: 2010-11-23 23:56:28 UTC (still connected) 2010-11-22 12:31:02 UTC 2010-11-23 23:46:28 UTC > Jelte Wilfried From robert at ripe.net Wed Nov 24 16:52:55 2010 From: robert at ripe.net (Robert Kisteleki) Date: Wed, 24 Nov 2010 16:52:55 +0100 Subject: [atlas]Some issues today Message-ID: <4CED34D7.3030809@ripe.net> Dear All, As you already know, RIPE Atlas is in a prototype phase. A good illustration for it is an issue we had today. We're still investigating the cause, but in the meantime we had to ignore some data points for a subset of the probes -- please don't be surprised to see missing parts of your probe graphs for today. Thanks for your understanding, Robert From Woeber at CC.UniVie.ac.at Wed Nov 24 21:20:47 2010 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Wed, 24 Nov 2010 20:20:47 +0000 Subject: [atlas]The probes and IPv6 Message-ID: <4CED739F.3040600@CC.UniVie.ac.at> Just had a look again at the info page for my 414, in the "Configuration" panel. While this thing does have IPv6 connectivity and performs measurements just OK, the section "IPv6", next to the MAC Address, is empty. Bug or "reserved for future use"? While we did the EUI-64 math locally to generate a DNS AAAA entry derived from the MAC, some folks may be better off to see the auto-conf'd address. As an aside, for the "ideas stack", it would be hip to have a means of educating the probe about an IPv6-transport-capable DNS server. I know, there are some issues with this idea :-/ All the best, Wilfried. PS: Looking forward to see probe #2, 466, becoming visible as living in my village, after making pole position for #1 already :-) From robert at ripe.net Thu Nov 25 10:09:24 2010 From: robert at ripe.net (Robert Kisteleki) Date: Thu, 25 Nov 2010 10:09:24 +0100 Subject: [atlas]The probes and IPv6 In-Reply-To: <4CED739F.3040600@CC.UniVie.ac.at> References: <4CED739F.3040600@CC.UniVie.ac.at> Message-ID: <4CEE27C4.8040309@ripe.net> On 2010.11.24. 21:20, Wilfried Woeber, UniVie/ACOnet wrote: > Just had a look again at the info page for my 414, > in the "Configuration" panel. > > While this thing does have IPv6 connectivity and performs measurements > just OK, the section "IPv6", next to the MAC Address, is empty. > > Bug or "reserved for future use"? We never came around to write "to be filled in later" there. But it's coming (I mean either the values or text :-) Cheers, Robert From Woeber at CC.UniVie.ac.at Thu Nov 25 10:20:07 2010 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Thu, 25 Nov 2010 09:20:07 +0000 Subject: [atlas]The probes and IPv6 In-Reply-To: <4CEE27C4.8040309@ripe.net> References: <4CED739F.3040600@CC.UniVie.ac.at> <4CEE27C4.8040309@ripe.net> Message-ID: <4CEE2A47.7060609@CC.UniVie.ac.at> Robert Kisteleki wrote: > On 2010.11.24. 21:20, Wilfried Woeber, UniVie/ACOnet wrote: > >>Just had a look again at the info page for my 414, >>in the "Configuration" panel. >> >>While this thing does have IPv6 connectivity and performs measurements >>just OK, the section "IPv6", next to the MAC Address, is empty. >> >>Bug or "reserved for future use"? > > > We never came around to write "to be filled in later" there. But it's coming > (I mean either the values or text :-) Ah, I see. > Cheers, > Robert I think you can imagine which path I would prefer :-) While it isn't rocket science to do the EUI-64 on a piece of ePaper, cut-n-paste is even simpler.... Thanks, Wilfried From Woeber at CC.UniVie.ac.at Thu Nov 25 10:26:26 2010 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Thu, 25 Nov 2010 09:26:26 +0000 Subject: [atlas]IPv4 DHCP and varying addresses Message-ID: <4CEE2BC2.1050608@CC.UniVie.ac.at> Having a simple question regarding DHCP and varying addresses within a subnet... While I *do* have access to the config of the DHCP server that delivers addresses to 414, and thus the probe will always get that same IP address, I *do not* have access to configure the DHCP service in my ADSL CPE (yet), which means that the individual address given to the probe may change over time. I guess this is expected and being taken care of by the system, but wanted to double-check. Thanks, Wilfried. From antony at ripe.net Thu Nov 25 11:53:56 2010 From: antony at ripe.net (Antony Antony) Date: Thu, 25 Nov 2010 11:53:56 +0100 Subject: [atlas]IPv4 DHCP and varying addresses In-Reply-To: <4CEE2BC2.1050608@CC.UniVie.ac.at> References: <4CEE2BC2.1050608@CC.UniVie.ac.at> Message-ID: <20101125105356.GA12333@dog.ripe.net> Hi Wilfried, The dhcp client is udhcpc. I think it does the right thing with lease expiry and a new lease. The measurements will work fine. However, there may be an issue in reporting probe's IPv4 address. The probe IP address you see in the control panel may be the previous one. Once it reboot it will report the new one. I am not too sure I have to check. I will keep an eye for changes to probe ip address. regards, -antony On Thu, Nov 25, 2010 at 09:26:26AM +0000, Wilfried Woeber, UniVie/ACOnet wrote: > Having a simple question regarding DHCP and varying addresses within a > subnet... > > While I *do* have access to the config of the DHCP server that delivers > addresses to 414, and thus the probe will always get that same IP address, > > I *do not* have access to configure the DHCP service in my ADSL CPE (yet), > which means that the individual address given to the probe may change over > time. > > I guess this is expected and being taken care of by the system, but wanted > to double-check. > > Thanks, > Wilfried. > > From Woeber at CC.UniVie.ac.at Sat Nov 27 20:12:21 2010 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Sat, 27 Nov 2010 19:12:21 +0000 Subject: [atlas]how many of us are on this list? Message-ID: <4CF15815.6000004@CC.UniVie.ac.at> Hi folks, just had a look at the graphs and at the # of people "talking" on this list... There are some 130 probes "up" and some 150 "ready" :-) Now I am wondering, how many subscriptions does this list have by now? Have a nice weekend, all, Wilfried. From dogwallah at gmail.com Sat Nov 27 20:33:27 2010 From: dogwallah at gmail.com (McTim) Date: Sat, 27 Nov 2010 22:33:27 +0300 Subject: [atlas]how many of us are on this list? In-Reply-To: <4CF15815.6000004@CC.UniVie.ac.at> References: <4CF15815.6000004@CC.UniVie.ac.at> Message-ID: Hi Wilfried, I'm here! (the only active probe in Africa) -- Cheers, McTim "A name indicates what we seek. An address indicates where it is. A route indicates how we get there." Jon Postel On Sat, Nov 27, 2010 at 10:12 PM, Wilfried Woeber, UniVie/ACOnet wrote: > Hi folks, > > just had a look at the graphs and at the # of people "talking" on this > list... > > There are some 130 probes "up" and some 150 "ready" :-) > > Now I am wondering, how many subscriptions does this list have by now? > > Have a nice weekend, all, > Wilfried. > > From robert at ripe.net Sat Nov 27 20:53:21 2010 From: robert at ripe.net (Robert Kisteleki) Date: Sat, 27 Nov 2010 20:53:21 +0100 Subject: [atlas]how many of us are on this list? In-Reply-To: References: <4CF15815.6000004@CC.UniVie.ac.at> Message-ID: <4CF161B1.90804@ripe.net> On 2010.11.27. 20:33, McTim wrote: > Hi Wilfried, > > I'm here! (the only active probe in Africa) As of now :-) There are almost 10 on their way "home" in Africa. As for the list, there are 45 subscribers currently. Cheers, Robert From graham at apolix.co.za Sat Nov 27 20:47:05 2010 From: graham at apolix.co.za (Graham Beneke) Date: Sat, 27 Nov 2010 21:47:05 +0200 Subject: [atlas]how many of us are on this list? In-Reply-To: References: <4CF15815.6000004@CC.UniVie.ac.at> Message-ID: <4CF16039.40200@apolix.co.za> On 27/11/2010 21:33, McTim wrote: > I'm here! (the only active probe in Africa) Nice try McTim ;-) You'll notice there is a second one live a little further south. -- Graham Beneke From lesnix at gmail.com Sun Nov 28 13:50:40 2010 From: lesnix at gmail.com (Egor Zimin) Date: Sun, 28 Nov 2010 21:50:40 +0900 Subject: [atlas]how many of us are on this list? In-Reply-To: <4CF16039.40200@apolix.co.za> References: <4CF15815.6000004@CC.UniVie.ac.at> <4CF16039.40200@apolix.co.za> Message-ID: I'm here too ) The east Moscow probes. 2010/11/28 Graham Beneke : > On 27/11/2010 21:33, McTim wrote: >> >> I'm here! (the only active probe in Africa) > > Nice try McTim ;-) > > You'll notice there is a second one live a little further south. > > -- > Graham Beneke > > -- Best regards, Egor Zimin From Woeber at CC.UniVie.ac.at Sun Nov 28 17:43:07 2010 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Sun, 28 Nov 2010 16:43:07 +0000 Subject: [atlas]how many of us are on this list? In-Reply-To: References: <4CF15815.6000004@CC.UniVie.ac.at> Message-ID: <4CF2869B.50804@CC.UniVie.ac.at> McTim wrote: > Hi Wilfried, > > I'm here! (the only active probe in Africa) Hi McTim, it is sort of nice to end up in the pole-position... I made #1 and #2 in Vienna, AT :-) and we'll soon have a 3rd up in our village. Cheers, Wilfried. From Woeber at CC.UniVie.ac.at Sun Nov 28 17:50:44 2010 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Sun, 28 Nov 2010 16:50:44 +0000 Subject: [atlas]some comments regarding the user interface - re-sizing and outage(s) Message-ID: <4CF28864.8090400@CC.UniVie.ac.at> Just minor cosmetics, and for the to-do-list :-) - the probe and measurements display reacts to a resizing of the window, e.g. from partial screen to full-screen, by redrawing the inforamtion and using all the real estate, but does NOT redraw on a switch back to a smaller size. (IE7, W/XP prof. SP3) - regardig the "Uptime" panel, I'd like to see the most recent outage included by default (the UTC stamp of most recent down transition, the most recent up transition and the duration). Alternatively, I'd be happy to make the selection for "Show last 25 connections sticky, maybe by giving the number of entries to display. Cheers, Wilfried. From rbarnes at bbn.com Sun Nov 28 17:31:18 2010 From: rbarnes at bbn.com (Richard L. Barnes) Date: Sun, 28 Nov 2010 11:31:18 -0500 Subject: [atlas]how many of us are on this list? In-Reply-To: <4CF15815.6000004@CC.UniVie.ac.at> References: <4CF15815.6000004@CC.UniVie.ac.at> Message-ID: I'm here, but haven't gotten my (east-coast US) probe plugged in yet. --Richard On Nov 27, 2010, at 2:12 PM, Wilfried Woeber, UniVie/ACOnet wrote: > Hi folks, > > just had a look at the graphs and at the # of people "talking" on this > list... > > There are some 130 probes "up" and some 150 "ready" :-) > > Now I am wondering, how many subscriptions does this list have by now? > > Have a nice weekend, all, > Wilfried. > From daniel.karrenberg at ripe.net Mon Nov 29 08:21:35 2010 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Mon, 29 Nov 2010 08:21:35 +0100 Subject: [atlas]how many of us are on this list? In-Reply-To: References: <4CF15815.6000004@CC.UniVie.ac.at> Message-ID: <20101129072135.GD1964@reif.karrenberg.net> On 28.11 11:31, Richard L. Barnes wrote: > I'm here, but haven't gotten my (east-coast US) probe plugged in yet. > --Richard Why is that exactly? ;-) Daniel From Woeber at CC.UniVie.ac.at Mon Nov 29 14:53:00 2010 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Mon, 29 Nov 2010 13:53:00 +0000 Subject: [atlas]P466 - inconsistent readings? Message-ID: <4CF3B03C.9080804@CC.UniVie.ac.at> Hi Team, could you pls. have a look at the grpahs of 466 and the list of "perceived" outages for the probe? While I can't prove that there wasn't some problem with my ADSL link at home (while sitting in the office :-) ), the graphs for the pings seem to indicate that the probe was alive and kicking all the time. I may be misreading some stuff, though.... Wilfried From rbarnes at bbn.com Mon Nov 29 16:21:50 2010 From: rbarnes at bbn.com (Richard L. Barnes) Date: Mon, 29 Nov 2010 10:21:50 -0500 Subject: [atlas]how many of us are on this list? In-Reply-To: <20101129072135.GD1964@reif.karrenberg.net> References: <4CF15815.6000004@CC.UniVie.ac.at> <20101129072135.GD1964@reif.karrenberg.net> Message-ID: <52C7ADD6-778E-4C57-8790-3D5FBEAE9AB0@bbn.com> A long story if IT policy woe. To be told over a beer in Amsterdam next time. Hopefully resolved in another week or two. --Richard On Nov 29, 2010, at 2:21 AM, Daniel Karrenberg wrote: > On 28.11 11:31, Richard L. Barnes wrote: >> I'm here, but haven't gotten my (east-coast US) probe plugged in yet. >> --Richard > > Why is that exactly? ;-) > > Daniel From robert at ripe.net Tue Nov 30 11:47:06 2010 From: robert at ripe.net (Robert Kisteleki) Date: Tue, 30 Nov 2010 11:47:06 +0100 Subject: [atlas]some comments regarding the user interface - re-sizing and outage(s) In-Reply-To: <4CF28864.8090400@CC.UniVie.ac.at> References: <4CF28864.8090400@CC.UniVie.ac.at> Message-ID: <4CF4D62A.7020702@ripe.net> Hi, On 2010.11.28. 17:50, Wilfried Woeber, UniVie/ACOnet wrote: > Just minor cosmetics, and for the to-do-list :-) > > - the probe and measurements display reacts to a resizing of the window, > e.g. from partial screen to full-screen, by redrawing the inforamtion > and using all the real estate, but does NOT redraw on a switch back to > a smaller size. (IE7, W/XP prof. SP3) This is the same browser that you dislike because it complains too much, right? :-) > - regardig the "Uptime" panel, I'd like to see the most recent outage > included by default (the UTC stamp of most recent down transition, the > most recent up transition and the duration). > Alternatively, I'd be happy to make the selection for > "Show last 25 connections > sticky, maybe by giving the number of entries to display. A similar solution is in our queue: visualising the uptime. That'd probably help a lot. Cheers, Robert > Cheers, > Wilfried. > From robert at ripe.net Tue Nov 30 11:51:48 2010 From: robert at ripe.net (Robert Kisteleki) Date: Tue, 30 Nov 2010 11:51:48 +0100 Subject: [atlas]P466 - inconsistent readings? In-Reply-To: <4CF3B03C.9080804@CC.UniVie.ac.at> References: <4CF3B03C.9080804@CC.UniVie.ac.at> Message-ID: <4CF4D744.9010804@ripe.net> On 2010.11.29. 14:53, Wilfried Woeber, UniVie/ACOnet wrote: > Hi Team, > > could you pls. have a look at the grpahs of 466 and the list of > "perceived" outages for the probe? > > While I can't prove that there wasn't some problem with my ADSL link at > home (while sitting in the office :-) ), the graphs for the pings seem > to indicate that the probe was alive and kicking all the time. > > I may be misreading some stuff, though.... > Wilfried > Your graphs look fine to me now. Maybe I missed the window of opportunity? :-) Seriously: if there's a structural problem, then _all_ the graphs will have gaps in exactly the same intervals. This is easy to spot as on the probe status page all the graphs are nicely aligned. Robert From Woeber at CC.UniVie.ac.at Tue Nov 30 13:40:08 2010 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Tue, 30 Nov 2010 12:40:08 +0000 Subject: [atlas]P466 - inconsistent readings? In-Reply-To: <4CF4D744.9010804@ripe.net> References: <4CF3B03C.9080804@CC.UniVie.ac.at> <4CF4D744.9010804@ripe.net> Message-ID: <4CF4F0A8.7030905@CC.UniVie.ac.at> Hi Robert, Team! Robert Kisteleki wrote: > On 2010.11.29. 14:53, Wilfried Woeber, UniVie/ACOnet wrote: > >>Hi Team, >> >>could you pls. have a look at the grpahs of 466 and the list of >>"perceived" outages for the probe? >> >>While I can't prove that there wasn't some problem with my ADSL link at >>home (while sitting in the office :-) ), the graphs for the pings seem >>to indicate that the probe was alive and kicking all the time. >> >>I may be misreading some stuff, though.... >>Wilfried >> > > > > Your graphs look fine to me now. Maybe I missed the window of opportunity? :-) Maybe :-) My point is that the "outage panel" lists a lot of "downs" for yesterday, but these periods are not visible in the graphs for that timeframe as grey "no data" bars. Given the stability of my ADSL link, I'd rather believe in the graphs instead of the list of down-up transitions. So, I probably should have asked: which criteria do you select or evaluate to declare a probe "down" and then "up" again? :-) > Seriously: if there's a structural problem, then _all_ the graphs will have > gaps in exactly the same intervals. This is easy to spot as on the probe > status page all the graphs are nicely aligned. > > Robert Btw, just to make that clear, this is not a complaint or an attempt to bother you excessively. I "simply" try to understand how this stuff works. Because I consider this understanding as essential to grok the information in the graphs (and to be able to make potential probe-sponsors intersted). Cheers, Wilfried. From robert at ripe.net Tue Nov 30 16:12:32 2010 From: robert at ripe.net (Robert Kisteleki) Date: Tue, 30 Nov 2010 16:12:32 +0100 Subject: [atlas]P466 - inconsistent readings? In-Reply-To: <4CF4F0A8.7030905@CC.UniVie.ac.at> References: <4CF3B03C.9080804@CC.UniVie.ac.at> <4CF4D744.9010804@ripe.net> <4CF4F0A8.7030905@CC.UniVie.ac.at> Message-ID: <4CF51460.700@ripe.net> On 2010.11.30. 13:40, Wilfried Woeber, UniVie/ACOnet wrote: >> Your graphs look fine to me now. Maybe I missed the window of opportunity? :-) > > Maybe :-) > > My point is that the "outage panel" lists a lot of "downs" for yesterday, > but these periods are not visible in the graphs for that timeframe as grey > "no data" bars. Given the stability of my ADSL link, I'd rather believe in > the graphs instead of the list of down-up transitions. > > So, I probably should have asked: which criteria do you select or evaluate > to declare a probe "down" and then "up" again? :-) A probe is considered to be "up" if it's connected to our infrastructure and is sending in measurement data. If it isn't, then it's "down". If the probe disconnects for some reason, it'll try to get back as soon as it can. This is recorded as an event in the connection log. However, if the probe is able to get back quickly and resume measurements, there may not be gaps at all in the graphs. So, observing some downtime and having continuous graphs are not mutually exclusive. > Btw, just to make that clear, this is not a complaint or an attempt to bother > you excessively. I "simply" try to understand how this stuff works. > > Because I consider this understanding as essential to grok the information in > the graphs (and to be able to make potential probe-sponsors intersted). Therefore your questions are perfectly fair, and I hope I or other members of the team can answer them sufficiently. Cheers, Robert > Cheers, > Wilfried.