December 2010 - ripe-atlas - mailman.ripe.net

[atlas]Moving a probe
by Richard L. Barnes 13 Dec '10

13 Dec '10

Hey guys, I have had a probe move from Columbia, Maryland, USA to Cambridge, Massachusetts, USA. How do I update the registered location? --Richard

2 1

[atlas]Upgrades today
by Robert Kisteleki 11 Dec '10

11 Dec '10

Hi, Today we'll upgrade some of the central components of the system, including the UI. Please don't be surprised about service interruptions. Regards, Robert

6 10

[atlas]option ntp-servers ?
by Marco Davids (SIDN) 09 Dec '10

09 Dec '10

Hi, Question: does the Atlas-probe obey to the 'option ntp-servers' DHCP option? If not, mine could be into trouble, since I don't allow outbound NTP-requests. (Sorry if this has been asked before, I am new to this list and haven't found the archive just yet) Regards, -- Marco

2 1

[atlas]IPv4 and IPv6 to the same machine(s)...
by Wilfried Woeber, UniVie/ACOnet 07 Dec '10

07 Dec '10

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.

5 4

[atlas]Atlas probe showing up as Never seen
by Harald Firing Karlsen 06 Dec '10

06 Dec '10

Hi, I installed my RIPE Atlas-probe yesterday and it still shows up as "Never seen" on the Atlas website. Everything looks good networking-wise (it have received DHCP-offer, etc), but it still shows up as "Never seen" on the Ripe Atlas website. The MAC-address is 00204AC8243A and the IP-address is 91.209.30.2. I hope you can solve this. -- Kind regards Harald Firing Karlsen

1 0

[atlas]probe locations
by Florian Obser 06 Dec '10

06 Dec '10

Hi, so, I had a look at the probe locations at https://atlas.ripe.net/ looks like there is a probe on every continent... except Antarctica! How cool would that be! Maybe there is someone on this list who knows someone who knows someone... ;) While discussing this with a friend we both noticed that the coolness could only be topped by a probe on ISS. Looking at the registration page this seems easy enough, "Method of delivery*: Other, please specify: Soyus or Ariane 5" "Hosting Location" on the other hand will probably be a pain in the ass. Regards, Florian -- I remember yesterday, but the memory is in my head now. Was yesterday real? Or is it only the memory that is real?

4 3

[atlas]DNS records for the probes' internet address
by Tore Anderson 03 Dec '10

03 Dec '10

Hi list, I've got a probe connected to my home broadband connection, which might change its WAN address whenever my ISP feels like it should. I just thought it would be a nice feature if the probes had an A record in DNS that were automatically updated to match the current external address. Like probe-121.atlas.ripe.net or something. That way I would have a hostname I would be sure that points to the WAN address of my CPE whenever I want to log on to my home network from somewhere else. I would think such a feature would be a small incentive for home broadband users to become probe hosts. On an unrelated note, the graphs for the probe in question (#121) doesn't work, they're all gray, even though the probe is up. Best regards, -- Tore Anderson Redpill Linpro AS - http://www.redpill-linpro.com Tel: +47 21 54 41 27

8 16

[atlas]FYI probe problems after power failure
by Jelte Jansen 03 Dec '10

03 Dec '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Today I had a power failure, and luckily everything came back up when I fixed it. However, a while later, I wondered if the probe had too, and it had not. The status page said it was up, but it hadn't reported data for about 6 hours (grey graphs). I assume I hit one of the problems in the FAQ: - --- Technical background: the probe tries to get current time indication using NTP upon booting, which sometimes fails. This causes the probe to think the curent date is November 1999, which confuses it a lot; it doesn't register properly or it sends measurement data for the twentieth century which is immediately discarded by the system. We plan to convince the probe to insist on vaild NTP or acquire some other time indication. The fix will be deployed in a firmware update. - --- Since the probe boots a lot faster than my gateway, I guess it never retried NTP. Powercycle fixed it indeed. So the lesson here is (at least until there is an update that retries ntpdate, or something), if the machine that provides your Internet connection takes a while to boot up, and they are both powered on at the same time, you may need to powercycle your probe. Jelte -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkz4HX0ACgkQ4nZCKsdOncVlXgCfZe+3FbLdTWTxCvXYZFrmaXjd TsEAn3vqmfjbUmWfueVcziCi2a3Hs6jF =zqNQ -----END PGP SIGNATURE-----

2 1

[atlas]Inaccurate uptime tracking?
by Richard L. Barnes 02 Dec '10

02 Dec '10

Hey guys, I'm seeing an inconsistency between the reported uptime and the actual measurements from probe #394. On the one hand, the probe info page reports only a little over an hour of uptime: Total Uptime: 0d, 1h, 1m Connect at: Disconnect at: 2010-12-02 02:38:06 UTC (still connected) 2010-12-01 04:22:43 UTC 2010-12-01 04:28:42 UTC But the graphs for the last 8 hours show only a brief down-time; roughly: Disconnect: 2010-12-02 02:27:00 UTC Reconnect: 2010-12-02 02:35:00 UTC This wouldn't bother me much if uptime weren't tied to chances to win an iPad :) --Richard

2 2

[atlas]atlas win!
by Florian Obser 01 Dec '10

01 Dec '10

Hi, we are running two probes. One behind my private dsl line at home, one in our data centre. I noticed that the IPv6 ping times to m.root-servers.net are more then twice as bad from our data centre compared to the dsl probe. As it turns out at home I'm talking to the m-root instance in Paris while in the data centre we were talking to the instance in Tokyo(?) It looks like this: http://eafc8bd05a0435ef14d31bbff29687dd7b71c3ca.de/m.root-servers.net.v6.png Not _that_ important in the great scheme of things but non the less quite nice ;) Thanks! Best regards, Florian

2 1