- ripe-atlas - mailman.ripe.net

[atlas]Feature request (fo consideration): broadcast rate measurement?
by Wilfried Woeber, UniVie/ACOnet 08 Apr '11

08 Apr '11

Xmas WishList 2011 :-) Looking at the yellow LED of the probes, I presume that their Ethernet IF operates in promiscuous mode. Even if not... I'd like to see some (easily configurable) measurement available, at least the rate of broadcast-packets on the probe's net. On a more elaborate basis, maybe according to simple paramters like a protocol/port combination. Would this make sense to implement and be of interest to others? Thanks for consideration, Wilfried. PS: yes, I do know about Netflow, WireShark and similar, but the beauty of the ATLAS Probe Approach is imho in the ready-nade UI :-)

1 0

Fwd: [atlas]"perceived" downtime of probe?
by Andreas Strikos 30 Mar '11

30 Mar '11

Begin forwarded message: > From: Andreas Strikos <astrikos(a)ripe.net> > Date: March 30, 2011 4:21:09 PM GMT+02:00 > To: Woeber(a)CC.UniVie.ac.at > Subject: Re: [atlas]"perceived" downtime of probe? > > Hi Wilfried, > > your probe is fine! > Last history uptime values are not propagated immediately to the central database by design. > That is why there were some "fault" calculations for small time for your probe. > Now that the latest uptime values are there, everything seems fine I believe. > > Regards, > Andreas > > On Mar 30, 2011, at 3:52 PM, Wilfried Woeber, UniVie/ACOnet wrote: > >> Hi Team, >> >> could you please have a look at the data for my 414, >> the "uptime" info claims a downtime of 7d, 16h, 51m, >> disconnected at 2011-03-22 20:50:26 UTC, up again at 2011-03-30 13:41:40 UTC. >> >> (the reason for the very short(!) interruption *today* was the need to move >> the USB cable to a different outlet...) [1] >> >> At the same time there is *no* loss of measurement data for this period!? >> >> Has anyone else seen such a situation recently? >> Wilfried >> >> [1] it would really be "cool" to ship future probes with some sort of >> "Y"-cable which w|should allow moving probes without loss of power, >> and/or to connect one plug to a UPS-fed outlet :-) >> >

1 0

[atlas]"perceived" downtime of probe?
by Wilfried Woeber, UniVie/ACOnet 30 Mar '11

30 Mar '11

Hi Team, could you please have a look at the data for my 414, the "uptime" info claims a downtime of 7d, 16h, 51m, disconnected at 2011-03-22 20:50:26 UTC, up again at 2011-03-30 13:41:40 UTC. (the reason for the very short(!) interruption *today* was the need to move the USB cable to a different outlet...) [1] At the same time there is *no* loss of measurement data for this period!? Has anyone else seen such a situation recently? Wilfried [1] it would really be "cool" to ship future probes with some sort of "Y"-cable which w|should allow moving probes without loss of power, and/or to connect one plug to a UPS-fed outlet :-)

1 0

[atlas]Statically configures probes - call for testers
by Robert Kisteleki 29 Mar '11

29 Mar '11

Hi, In a few days we'll be ready with a firmware that will support statically configured (IPv4) addresses for the probes. We'd like to test this out and get feedback from the interested people before we release it fully. So, if you are running a probe and would like to test the new functionality, please drop me a line. Cheers, Robert

1 0

[atlas]Simple way to open API access?
by Richard L. Barnes 24 Mar '11

24 Mar '11

Hey all, Suggestion for a simple way to provide some basic automated access to ATLAS data: It's pretty clear from the traffic that the site is driven off a set of JSON APIs [1]. This would make it pretty easy to write scripts that can access information from the site -- except that the script would need to have a Cookie for a valid user session. So it seems like a simple way to open access up would be to allow developers to access these JSON APIs, but with a different form of authentication. Namely, you could grant developers an "API key" that would function in the same way as a 'stat-session' cookie (in particular it would be bound to a developer identity/email), but would last indefinitely. This wouldn't really put any burden on the NCC other than to have a page to register the API keys. It would be helpful to document the APIs, but not strictly necessary, since JSON is so verbose. And you wouldn't necessarily have any additional requirements for the APIs to be stable, if this feature were properly marked as experimental/undocumented. Noting that the other cookie that the ATLAS page sets is "csrftoken" (which would probably have to be ignored in API key requests), it is worth noting that there is some risk with this approach that a bad developer will use this mechanism to enable CSRF attacks. But such attacks should be fairly easy to recognize, and if one is, then the relevant developer can be turned off. Just a thought, --Richard [1] For example <http://atlas.ripe.net/atlas/publicprobesgrid.json>

3 3

[atlas]New Atlas Features
by Andreas Strikos 07 Mar '11

07 Mar '11

Dear Hosts, We've now enabled two features that were requested by hosts earlier: 1. The "Probe DNS" function allows you to ask for a DNS entry for you probe. Operational details: * The exact DNS name of your probe depends on your settings (simple or obfuscated), and can be looked up on the "Probe Conf" section of the probe status page. * The zone file is re-generated every 15 minutes. * The resulting address is the one we observe when the probe to connects to our infrastructure, so if you're using NAT then it's the public address of the NAT device. Currently it's either IPv4 or IPv6, but not both. We'll add the "other address" too in the future. 2. The probe uptime section has more details. It now contains: * Relative uptime for the last week and month, and for the full lifetime. * The source IP address of the individual connections. * The amount of up- and downtime (in days/hours/minutes), for each connection. Regards, Andreas

2 1

[atlas]too many disconnects?
by Wilfried Woeber, UniVie/ACOnet 07 Mar '11

07 Mar '11

[my apologies to the Team for the duplicate, I 1st picked the wrong address] Q to the Team and to the Probe Hosts: My feeling is that the probes do register too many "disconnects". I just had a look at the two under my control and the numbers of transitions are - 466: 25 events between 2010-12-21 07:14:30 UTC and 2011-03-01 10:24:11 UTC 414: 25 events between 2010-11-22 12:31:02 UTC and 2011-02-20 20:18:24 UTC While there may be a local reason for some of the down-periods, I doubt that I had so many outages on my ends. Is anyone else seeing a similar pattern? Regarding presentation, again, could we please have an additional item of "Total Downtime" (next to the "Total Uptime"), and the duration of the downs in the 25 lines with the time stamps? This would make it much more straight- forward to spot patterns.... Minor cosmetics, relevant when reporting stuff, could the probe's number be displayed somewhere in the Probe Conf panel (e.g. in the line with the Firmware Version)? Thanks for your consideration, have a nice weekend Wilfried

3 2

[atlas]Atlas website upgrades
by Andreas Strikos 02 Mar '11

02 Mar '11

Hi, Today, in sync with the new Ripe NCC website we are upgrading Ripe Atlas website. You might encounter strange behaviors on some pages but we believe until the end of the day they will be fixed. Except from the template, there are some other changes in UI like a new tab for public probes and a bigger settings button. Also, from now on there will be an announcement page where you can read the latest information about Atlas. Regards, Andreas

4 3

[atlas]Down/Up fail
by Richard L. Barnes 16 Feb '11

16 Feb '11

Hey guys, I've just been re-engineering my home network to give probe 394 more stable access. It seems that the ATLAS web site still reports it as "down" even though it's clearly reporting information to the central system (since the RRD graphs are updated). Huh? --Richard

2 2

[atlas]Strange behaviour of probe
by Patrick Vande Walle 31 Jan '11

31 Jan '11

Hello Robert, According to the graphs on atlas.ripe.net, my probe (#45) seems to have been offline for nearly 24 hours. During that period, the DSL connection was up nevertheless. Are there more detailed logs on the probe controller that could explain what happened ? Thanks, Patrick Vande Walle

2 1