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