August 2013 - ripe-atlas - mailman.ripe.net

v3 Probe got disconnected and won't reconnect
by Axel Fischer 14 Aug '13

14 Aug '13

Hi, on 2013-08-11 at 05:15:30 UTC one of our probes (ID: 11707) got disconnected. It is connected via a switch to a router within our network. I can see the link up (it remained up all the time) but see the 3rd LED (Network Test) and 4th LED (Connecting) blinking. The MAC was visible on the switch port and router. I powercycled the probe but no change except that the MAC is no longer visible on the router. With a laptop instead of the probe it works fine. Is the probe broken? How can this state be fixed? Regards, Axel -- Axel Fischer Network Engineer 1&1 Internet AG Brauerstrasse 48 D-76135 Karlsruhe http://www.1und1.de (AS8560) Hauptsitz Montabaur, Amtsgericht Montabaur, HRB 6484 Vorstand: Ralph Dommermuth, Frank Einhellinger, Robert Hoffmann, Andreas Hofmann, Markus Huhn, Hans-Henning Kettler, Uwe Lamnek, Jan Oetjen, Christian Würst Aufsichtsratsvorsitzender: Michael Scheeren Member of United Internet Diese E-Mail kann vertrauliche und/oder gesetzlich geschützte Informationen enthalten. Wenn Sie nicht der bestimmungsgemäße Adressat sind oder diese E-Mail irrtümlich erhalten haben, unterrichten Sie bitte den Absender und vernichten Sie diese Email. Anderen als dem bestimmungsgemäßen Adressaten ist untersagt, diese E-Mail zu speichern, weiterzuleiten oder ihren Inhalt auf welche Weise auch immer zu verwenden. This E-Mail may contain confidential and/or privileged information. If you are not the intended recipient of this E-Mail, you are hereby notified that saving, distribution or use of the content of this E-Mail in any way is prohibited. If you have received this E-Mail in error, please notify the sender and delete the E-Mail.

3 2

Probe sharing
by Martin Stanislav 08 Aug '13

08 Aug '13

Hi, This spring RIPE Atlas update [1] introduced a new feature called probe sharing. Probe sharing should work for colleagues within the same LIR and is to be set via: "My Probes" -> "Probe's Settings" -> "General Configuration" -> Select your LIR in the "Share with" field. I've set the "Share with" field to our LIR ID for all three local probes. But a colleague of mine, in spite of being able to login to the Lirportal, sees an error message below every time he tries to access the probe list at https://atlas.ripe.net/atlas/myprobes.html The error message: "You are not logged in as a RIPE NCC member". Is there anything I've missed? Possible delay in privilege propagation from the Lirportal to Atlas section? Thanks. Martin [1] https://labs.ripe.net/Members/kistel/new-ripe-atlas-features-april-2013

4 4

Multiple Probe v3 Disconnects
by David Churchill 08 Aug '13

08 Aug '13

I just received my v3 probe 3 days ago and I've noticed on the status page that that there are quite a few disconnects: Disconnect at: Connected time: Disconnected time: (still connected) 0d, 0h, 30m (still connected) 2013-08-08 11:37:44 UTC 0d, 0h, 38m 0d, 0h, 2m 2013-08-08 10:49:09 UTC 0d, 1h, 14m 0d, 0h, 10m 2013-08-08 09:31:38 UTC 0d, 2h, 2m 0d, 0h, 3m 2013-08-08 07:25:41 UTC 0d, 1h, 22m 0d, 0h, 3m 2013-08-08 05:53:24 UTC 0d, 1h, 26m 0d, 0h, 9m 2013-08-08 04:24:56 UTC 0d, 2h, 23m 0d, 0h, 2m 2013-08-08 01:57:23 UTC 0d, 1h, 18m 0d, 0h, 4m 2013-08-08 00:35:09 UTC 0d, 0h, 26m 0d, 0h, 3m 2013-08-08 00:05:53 UTC 0d, 1h, 25m 0d, 0h, 2m 2013-08-07 22:37:14 UTC 0d, 1h, 12m 0d, 0h, 3m 2013-08-07 21:20:56 UTC 0d, 0h, 4m 0d, 0h, 4m 2013-08-07 21:11:44 UTC 0d, 2h, 9m 0d, 0h, 4m 2013-08-07 18:59:32 UTC 0d, 0h, 39m 0d, 0h, 2m 2013-08-07 18:18:40 UTC 0d, 6h, 12m 0d, 0h, 1m 2013-08-07 12:03:56 UTC 0d, 12h, 42m 0d, 0h, 1m 2013-08-06 23:19:16 UTC 0d, 0h, 4m 0d, 0h, 2m 2013-08-06 23:15:08 UTC 0d, 0h, 2m 0d, 0h, 0m 2013-08-06 23:05:16 UTC 0d, 4h, 45m 0d, 0h, 7m 2013-08-06 18:17:13 UTC 0d, 1h, 54m 0d, 0h, 2m 2013-08-06 16:18:39 UTC 0d, 0h, 45m 0d, 0h, 3m 2013-08-06 15:32:39 UTC 0d, 0h, 41m 0d, 0h, 0m 2013-08-06 14:50:33 UTC 0d, 2h, 32m 0d, 0h, 0m 2013-08-06 05:51:43 UTC 0d, 6h, 47m 0d, 6h, 25m Is this something I should be concerned about? If so, could it have to do with the fact that my probe is plugged into a 10/100/1000 MBit switch (I saw an earlier thread that suggested this might be an issue)? If the Gigabit switch is a problem, would it help if I cascade a 10/100 switch off one of the Gigabit switch's ports, or off one of my router's ports (which are all Gigabit) and then plug the probe into that 10/100 switch? Finally, I'm using a cell phone charger for power, it's 5V, mini-usb, I don't think that should cause an issue should it? Thanks for any help, David C. Churchill 5285 Vinings Springs Trl Mableton, GA 30126 770.819.5935 d_churchill(a)comcast.net

3 4

1000Base-T not supported?
by Tore Anderson 08 Aug '13

08 Aug '13

Today I was struggling to get a v3 probe (TP-Link) connected to my network, the link just wouldn't come up. On a whim I tried connecting it to a tri-rate 10/100/100Base-T device, and lo and behold - it came alive! Only 100Mb, though. Is it really the case that the probes don't support 1GbE? The probe has «150Mb» printed on it, which strikes me as rather odd if it's limited upwards to 100Mb. Tore

3 4

RIPE Atlas maintenance on Tuesday, 6 August
by Robert Kisteleki 06 Aug '13

06 Aug '13

Dear RIPE Atlas users, We'd like to let you know that we plan to perform scheduled maintenance on the RIPE Atlas central infrastructure on Tuesday, 6 August, for a couple of hours during the day. In this period, main features including the RIPE Atlas user interface (atlas.ripe.net), data downloads and measurement scheduling functions will be unavailable. Probes will continue to work and all results will still be collected or buffered; however, during the maintenance period you will be unable to log in to the website, manage your probes/measurements, or get to result data/visualisations. We apologise for any inconvenience this may cause. Regards, Robert Kisteleki

1 1

Probe no longer on an IPv6 network?
by Rusty Dekema 05 Aug '13

05 Aug '13

Good evening, When I first installed it, probe 10555 was on a network which supports IPv6. Since then, I have moved it to a different network which does not have IPv6 access at all. Is there something I should do to let the RIPE Atlas system know that it no longer has IPv6 access? It seems like there should be, but I haven't found it. I would not like for it to be one of those probes which "thinks" it has IPv6 but actually does not... Thanks, Rusty D

2 1

adding a device
by folkert 05 Aug '13

05 Aug '13

Hi, Yesterday I received a probe-device at a conference. I entered the details in the website (which was a lot of fun: finding out the ipv4 prefix(?!) - I ended up trying a couple of entries found in the whois info of my ipv4 address, also in what format should I enter the mac-address?) but the device does not appear in the "My probes" list. Even after a couple of hours. I verified that it got an ip4-address from the dhcp server and also radvd is happily announcing the ipv6-prefix in that segment. Furthermore: I see that the probe is doing all kinds of network traffic to the internet. So the device at itself seems to work. What can be wrong? Folkert van Heusden -- Always wondered what the latency of your webserver is? Or how much more latency you get when you go through a proxy server/tor? The numbers tell the tale and with HTTPing you know them! http://www.vanheusden.com/httping/ ----------------------------------------------------------------------- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com

3 3