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
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@ripe.net (developer's list). Regards, Robert -- Robert Kisteleki, Science Group Manager, RIPE NCC RIPE Atlas Team
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.
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@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
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@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.
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
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
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.
participants (4)
-
Daniel Karrenberg -
Henk Uijterwaal -
Rene Wilhelm -
Robert Kisteleki