This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas]Upgrades today
- Previous message (by thread): [atlas]Upgrades today
- Next message (by thread): [atlas]Upgrades today
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Karrenberg
daniel.karrenberg at ripe.net
Wed Nov 10 09:56:02 CET 2010
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
- Previous message (by thread): [atlas]Upgrades today
- Next message (by thread): [atlas]Upgrades today
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]