- ripe-atlas - mailman.ripe.net

Ping does no longer visualize?
by Sebastian Wiesinger 05 Oct '12

05 Oct '12

Hi, I just noticed that the Ping probe has changed, I can now enter more options but I'm unable to visualize the results. Even if I uncheck "do not visualize" I get no graphs. Regards Sebastian -- noris network AG - Thomas-Mann-Straße 16-20 - D-90471 Nürnberg Tel +49-911-9352-0 - Fax +49-911-9352-100 http://www.noris.de - The IT-Outsourcing Company Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel, Hansjochen Klenk - Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689

2 2

RIPE Atlas roadmap, September 2012 version
by Vesna Manojlovic 05 Oct '12

05 Oct '12

[apologies for duplicates] Dear colleagues, we just published a RIPE Labs article with the RIPE Atlas roadmap update for September: https://labs.ripe.net/Members/becha/ripe-atlas-roadmap-september-2012-update (the fact that is already October today is a bit confusing, but we presented this version during the RIPE 65 meeting last week...) This is the invitation to look at our plans, and let us know what you think, so that we can take that into account when making new plans, next month. Thanks, Vesna

1 0

Cannot change network configuration
by Tibor Djurica Potpara 04 Oct '12

04 Oct '12

Hello, I have recently changed the router that my Atlas probe is connected to. Since it is now in a separate subnet from my home LAN, with dedicated DHCP/RA configuration, there is no longer need for static address configuration, so I would like to revert its settings back to autoconfiguration for both IPv4 and IPv6. However, in the web interface,//"Change Probe's Network Configuration" menu is greyed out, so I cannot do anything even though the probe is up. What am I to do? Thank you, Tibor

4 3

Strange IPv6 problem with Atlas
by Max Grobecker 02 Oct '12

02 Oct '12

Hello, I got my new Atlas a few days ago and connected it to my network (in a separated VLAN). In this VLAN I'm announcing routing advertisements with autonomous IPv6 addressing enabled. Appearently the probe heard this advertisement and have chosen to communicate over IPv6 - but with a link-local IPv6 address only...?! This leads to "Beyond scope"-Messages from my router which I captured with tcpdump: fe80::280:a3ff:fe91:4070.58730 > 2a01:4f8:161:3281::43:148.443: Flags [S], seq 2585125851, win 5360, options [mss 1340,sackOK,TS val 4294950236 ecr 0,nop,wscale 1] fe80::225:90ff:fe92:2478 > fe80::280:a3ff:fe91:4070: ICMP6, destination unreachable, beyond scope 2a01:4f8:161:3281::43:148, source address fe80::280:a3ff:fe91:4070 My routing advertisements are currently looking like that: fe80::225:90ff:fe92:2478 > ff02::1: [icmp6 sum ok] ICMP6, router advertisement, length 64 hop limit 64, Flags [none], pref medium, router lifetime 1800s, reachable time 0s, retrans time 0s prefix info option (3), length 32 (4): 2a02:a00:e000:b:e6::/96, Flags [onlink, auto, router], valid time 86400s, pref. time 14400s mtu option (5), length 8 (1): 1400 source link-address option (1), length 8 (1): 00:25:90:92:24:78 Is there anything I can do to make the probe communicate over IPv6? Manual IP configuration is not possible since the menu item is greyed out (althrough my probe runs on FW 4470). I disabled RA at the moment so the Atlas cube can talk to the RIPEs Atlas servers. Thank you in advance! -- Greetings from Wuppertal, Germany Max Grobecker

3 3

10/8
by Randy Bush 01 Oct '12

01 Oct '12

an external border, where an atlas probe is on the soft gooey inside, logged packets sourced from 10/8? could this have been the atlas probe? randy Sep 29 08:36:44 r0.sea.rg.net 390: Sep 29 08:36:43.966: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(53649) -> 23.63.172.166(443), 1 packet Sep 29 08:36:49 r0.sea.rg.net 391: Sep 29 08:36:48.466: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(46959) -> 23.63.205.115(443), 1 packet Sep 29 08:42:32 r0.sea.rg.net 392: Sep 29 08:42:31.363: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(53649) -> 23.63.172.166(443), 1 packet Sep 29 11:24:45 r0.sea.rg.net 393: Sep 29 11:24:44.826: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(32986) -> 64.12.235.15(443), 1 packet Sep 29 11:31:35 r0.sea.rg.net 394: Sep 29 11:31:34.644: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(53512) -> 143.225.229.137(554), 1 packet Sep 29 11:37:32 r0.sea.rg.net 395: Sep 29 11:37:31.453: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(53512) -> 143.225.229.137(554), 8 packets Sep 29 11:43:21 r0.sea.rg.net 396: Sep 29 11:43:20.339: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(59262) -> 38.102.136.104(80), 1 packet Sep 29 11:43:33 r0.sea.rg.net 397: Sep 29 11:43:32.151: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60780) -> 69.171.228.74(443), 1 packet Sep 29 11:45:23 r0.sea.rg.net 398: Sep 29 11:45:22.013: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60761) -> 69.171.228.74(443), 1 packet Sep 29 11:45:26 r0.sea.rg.net 399: Sep 29 11:45:25.017: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60759) -> 69.171.228.74(443), 1 packet Sep 29 11:48:57 r0.sea.rg.net 400: Sep 29 11:48:56.480: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(46352) -> 174.37.29.147(80), 1 packet Sep 29 11:49:32 r0.sea.rg.net 401: Sep 29 11:49:31.465: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60780) -> 69.171.228.74(443), 1 packet Sep 29 11:49:32 r0.sea.rg.net 402: Sep 29 11:49:31.465: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60781) -> 69.171.228.74(443), 2 packets Sep 29 11:50:32 r0.sea.rg.net 403: Sep 29 11:50:31.466: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60761) -> 69.171.228.74(443), 1 packet Sep 29 11:50:32 r0.sea.rg.net 404: Sep 29 11:50:31.466: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60759) -> 69.171.228.74(443), 1 packet Sep 29 11:54:32 r0.sea.rg.net 405: Sep 29 11:54:31.469: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(46352) -> 174.37.29.147(80), 1 packet Sep 29 12:10:05 r0.sea.rg.net 406: Sep 29 12:10:04.260: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60333) -> 193.0.6.139(443), 1 packet Sep 29 12:10:11 r0.sea.rg.net 407: Sep 29 12:10:10.292: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60348) -> 193.0.6.139(443), 1 packet Sep 29 12:10:24 r0.sea.rg.net 408: Sep 29 12:10:22.640: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60363) -> 193.0.6.139(443), 1 packet Sep 29 12:13:30 r0.sea.rg.net 409: Sep 29 12:13:29.535: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(33721) -> 193.0.6.133(443), 1 packet Sep 29 12:14:10 r0.sea.rg.net 410: Sep 29 12:14:09.435: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(37936) -> 178.63.78.16(80), 1 packet Sep 29 12:14:29 r0.sea.rg.net 411: Sep 29 12:14:28.256: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(33754) -> 193.0.6.133(443), 1 packet Sep 29 12:15:32 r0.sea.rg.net 412: Sep 29 12:15:31.489: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60348) -> 193.0.6.139(443), 2 packets Sep 29 12:15:32 r0.sea.rg.net 413: Sep 29 12:15:31.489: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60363) -> 193.0.6.139(443), 1 packet Sep 29 12:15:32 r0.sea.rg.net 414: Sep 29 12:15:31.489: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60364) -> 193.0.6.139(443), 2 packets Sep 29 12:15:32 r0.sea.rg.net 415: Sep 29 12:15:31.489: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(60366) -> 193.0.6.139(443), 2 packets Sep 29 12:19:32 r0.sea.rg.net 416: Sep 29 12:19:31.492: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(37936) -> 178.63.78.16(80), 2 packets Sep 29 12:19:32 r0.sea.rg.net 417: Sep 29 12:19:31.492: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(33754) -> 193.0.6.133(443), 2 packets Sep 29 12:21:00 r0.sea.rg.net 418: Sep 29 12:20:59.386: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(39687) -> 206.219.196.114(443), 1 packet Sep 29 12:21:42 r0.sea.rg.net 419: Sep 29 12:21:41.318: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(39683) -> 206.219.196.114(443), 1 packet Sep 29 12:23:57 r0.sea.rg.net 420: Sep 29 12:23:56.533: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(56161) -> 88.221.216.66(80), 1 packet Sep 29 12:24:20 r0.sea.rg.net 421: Sep 29 12:24:19.673: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(39741) -> 206.219.196.114(443), 1 packet Sep 29 12:26:32 r0.sea.rg.net 422: Sep 29 12:26:31.499: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(39687) -> 206.219.196.114(443), 2 packets Sep 29 12:27:32 r0.sea.rg.net 423: Sep 29 12:27:31.500: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(39683) -> 206.219.196.114(443), 10 packets Sep 29 12:28:53 r0.sea.rg.net 424: Sep 29 12:28:52.193: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(44361) -> 64.12.104.224(443), 1 packet Sep 29 12:29:32 r0.sea.rg.net 425: Sep 29 12:29:31.502: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(56162) -> 88.221.216.66(80), 7 packets Sep 29 12:29:32 r0.sea.rg.net 426: Sep 29 12:29:31.502: %SEC-6-IPACCESSLOGP: list serial-out4 denied tcp 10.13.0.6(56161) -> 88.221.216.66(80), 6 packets

3 4

RIPE Atlas at RIPE65
by Vesna Manojlovic 21 Sep '12

21 Sep '12

[apologies for duplicates] Dear community, we are happy to invite you to the "Atlas Bash" at the RIPE65: Tuesday, 25 September, 18:00 – 19:00 (plenary room). This has just been added to the meeting agenda, in one of the BoF slots (Birds of Feathers): https://ripe65.ripe.net/programme/meeting-plan/birds-of-a-feather/ We would like to make this an interactive session, in order to bring RIPE Atlas UDM users and beta-testers together in one room with RIPE Atlas developers and the Measurements Community Builder to discuss developments, exchange ideas and best practices, suggest improvements, etc. This is also a great opportunity to learn more about the RIPE Atlas Anchors pilot project, how to get involved, to discuss host requirements, which features do you want, and more. We will be giving various presentations at many working groups, too, about the measurements results from RIPE Atlas, and plans for the future: MAT-wg, NCC-services-wg, plenary... Detailed information will follow next week, when all agendas are finalized. Hope to see you there! If you can not take part, there will be webcasts and jabber, and we will report back on these mailing lists. Regards, Vesna

1 1

Announcing RIPE Atlas Anchors, Pilot Phase
by Vesna Manojlovic 31 Aug '12

31 Aug '12

Dear Atlas community, Please find a new article on RIPE Labs describing the details of RIPE Atlas Anchors: https://labs.ripe.net/Members/dfk/ripe-atlas-anchors Right now, we are looking for a small number of pilot hosts from the RIPE NCC membership for deployment to begin in October 2012. If you are interested, please contact me or Daniel Karrenberg before the RIPE65. We will be discussing further details at the RIPE meeting. Regards, Vesna Manojlovic -- Vesna Manojlovic BECHA(a)ripe.net Senior Community Builder +31205354444 for Measurements Tools RIPE NCC http://ripe.net

1 0

Operational issue between ~14h-16h UTC
by Robert Kisteleki 29 Aug '12

29 Aug '12

Dear Atlas users, This afternoon our developers deployed an upgrade to the Atlas controlling infrastructure. Unfortunately, the update contained a bug that we did not catch in the test environment. This bug caused all probes to suspend their running UDMs (User Defined Measurements) between approximately 14h-16h (UTC, different probes were affected at different times). After noticing the error we reverted the changes, and resumed all UDMs. Because of this, your UDMs likely have missing data points for this time frame. Obviously, more frequent measurements will have more missing results while less frequent measurements will have less (or even nothing) missing results. "Built-in" measurements (i.e. non-UDMs) have not been affected. Based on this experience, we'll enhance our testing procedure to lower the chance of these kind of errors happening again. Excuses for the inconvenience this issue may have caused. Regards, Robert Kisteleki RIPE NCC

1 0

Two new measurements types, and a new interface (wizard)
by Vesna Manojlovic 28 Aug '12

28 Aug '12

Dear Atlas community, I am happy to announce DNS & SSL certificate measurements, a new addition to the UDMs, making it in total 4 types of customized measurements you can perform! Please find out the details in the RIPE Labs article: https://labs.ripe.net/Members/becha/dns-user-defined-measurements-in-ripe-a… In order to make more types of measurements possible, we have also introduced the new web interface: so-called wizard. It has been extensively tested by the beta-testers for two months, and we hope that the rest of the Atlas UDM users will find it handy. The old interface has been deprecated, so the usual link now leads to the new wizard: https://atlas.ripe.net/atlas/udm.html Please let us know what you think, and enjoy the measurements :) If you have a success-story to share, consider giving a presentation at the RIPE65, or writing RIPE Labs article. I am willing to work on this together with you, so do let me know if you need any help. Regards, Vesna

3 2

Static configuration feedback
by Jeroen van der Ham 16 Aug '12

16 Aug '12

Hi, I've noticed that the table on the webpage which displays the status of a probe's static configuration is not working right. If the "Static Enabled" setting is ticked, the "Probe Knows" is automatically ticked as well, *even for probes which are offline*. The feedback this gives is wrong and actually counterproductive. Could this be fixed please? Jeroen.

2 1

Traceroute path consistency
by David Lebrun 15 Aug '12

15 Aug '12

Hi all, I have a suggestion regarding the udp traceroute feature: allowing the user to specify the source port. The motivation for this suggestion is to keep consistent paths between two traceroutes towards the same destination. I understand that the source port is used to discriminate concurrent traceroutes, so perhaps allocating a range for user-defined source ports would do the trick. There is of course the issue of two users selecting the same source port for the same destination but this is very unlikely. Do you think this is feasible ? David

3 4

RIPE Atlas Roadmap: monthly update: August
by Vesna Manojlovic 08 Aug '12

08 Aug '12

Dear Atlas community, (thanks, Inigo ;-) while developing RIPE Atlas, we wish to keep *you* involved and informed. We are maintaining a roadmap of the features we are working on, and with this update we are asking for feedback, so that we can use it as guidance for making further plans. You can find much more details are in the RIPE Labs article: https://labs.ripe.net/Members/becha/ripe-atlas-roadmap-august-2012-update Here I only want to copy the plans for next 4-6 weeks, and three months after that, and to repeat the questions from the article: Plans for the next month: * Users can get more flavors of customized measurements: DNS & SSL - new wizard for two new types of measurements, currently beta-tested * Making it possible to download measurements results without having to be logged in - by deploying & enabling API Keys * Making it easier to follow the rate of deployment of probes over time - by updating the graphs that show the distribution and status of probes * Atlas hosts and sponsors can meet developers during RIPE65, Amsterdam - exchange experiences, give feedback and requirements - so developers can adjust priorities Plans for Q4 2012: * Installing Atlas Anchors as new targets for pre-defined measurements - this will offer greater topological diversity for measurements - Atlas Anchors will also become powerful probes, capable of performing more measurements then small probes * In order to remind you if the probe is not plugged in or if it is down - we will add more automatic email notifications of events * We will create Internet Traffic Maps based on Atlas data - maps will illustrate the health (e.g. reachability) of measured networks Questions: - About the current functionality: what do you want us to improve? - About additions to the next release: what are the most-wanted features for each one of them? - And finally, from the less-specific planned functionalities that we will work on three-six months from now: - what do you find most important? - to which one of them shall we give most priority? Thank you for your feedback, have a great summer, and see you soon in Amsterdam, Vesna

1 0

Make more measurements
by Vesna Manojlovic 06 Aug '12

06 Aug '12

Dear Atlas users, for few weeks already it is possible to perform *more* UDMs (User Defined Measurements), since we have increased the limits, and allowed you to spend your well-earned "credits": - you can perform up to 5 measurements simultaneously, - from up to 50 probes, - and you can spend 270,000 credits per day. A reminder of documentation location: - to see your measurements, and schedule a new one: https://atlas.ripe.net/atlas/udm.html - to find out more about UDM functionality: https://atlas.ripe.net/doc/udm You can read much more about Atlas on RIPE Labs: https://labs.ripe.net/atlas Have a great summer! Vesna

2 1

HTTP UDM?
by Miles McCredie 03 Aug '12

03 Aug '12

Are there any plans to support an HTTP UDM? Thanks -Miles

2 4

Sharing Stats?
by Dan Luedtke 03 Aug '12

03 Aug '12

Hello everyone, what are your opinions on sharing stats from a probe to the public? My idea: I have a public probe and public UDMs running, and I would like to embed the "last 8 hours" graphs into a website where people can see it, even those that do not have access to RIPE Atlas. Do you think it is a good idea to ask for a feature that splits the "Public" checkbox into two ones saying "Public (ATLAS Community)" and "Public (Internet)"? best regards, Dan -- Dan Luedtke http://www.danrl.de

8 10

Port blocking statistics
by Bartsch, Rene 25 Jul '12

25 Jul '12

Hi, when charting the internet it would be useful to have an oversight about ISPs blocking ports. Especially discussions about network neutrality should be based on hard facts instead of polemic discussions. So I suggest to check the connectivity of the protocols listed in http://www.iana.org/assignments/service-names-port-numbers/service-names-po… once a week as built-in measurement. Best regards, Renne -- Sent with love from the new tine 2.0 email client ... Please visit http://tine20.org

3 3

128.0.0.1 and 128.0.24.1 measurements
by Tuomo Soini 24 Jul '12

24 Jul '12

Should these measurements be discontinued? These networks are no more visible. http://www.ris.ripe.net/dashboard/128.0.24.0/24 http://www.ris.ripe.net/dashboard/128.0.0.0/21 -- Tuomo Soini <tis(a)foobar.fi> Foobar Linux services +358 40 5240030 Foobar Oy <http://foobar.fi/>

2 1

Probe down?
by Yoann Gini 23 Jul '12

23 Jul '12

Hello, My probe is down since a while now. I’ve try to unplug and replug many time, change USB and ethernet slot and it’s still down. The green led is on and the orange is slowly flashing, my swith see the probe, bit Atlas always report it as down. I’ve the Probe ID 2199. What I’m supposed to do ? Best regards, Yoann Gini.

5 5

Fwd: [ipv6-wg] New on RIPE Labs: Test your IPv6 Reachability by Using RIPE Atlas (now visualised)
by kix 23 Jul '12

23 Jul '12

fyi. I think this mail was not sent to this mail list. Cheers, kix -------- Mensaje original -------- Asunto: [ipv6-wg] New on RIPE Labs: Test your IPv6 Reachability by Using RIPE Atlas (now visualised) Fecha: 17/07/2012 14:32 Remitente: Mirjam Kuehne <mir(a)ripe.net> Destinatario: ipv6-wg(a)ripe.net [apologies for duplicate mails] Dear colleagues, As announced in earlier, it is possible for RIPE NCC members to do IPv6-traceroutes from all RIPE Atlas probes to IPv6 destinations. In this new article on RIPE Labs we present a first experimental analysis and a prototype visualisation of the traceroute results: https://labs.ripe.net/Members/emileaben/visualise-your-ipv6-connectivity-us… Kind Regards, Mirjam Kuehne RIPE NCC -- Rodolfo García Peñas (kix) http://www.kix.es

7 7

Concurrent traceroute issues on the probes
by David Lebrun 23 Jul '12

23 Jul '12

Hi all, I was wondering whether the probes can perform multiple concurrent traceroutes toward different destinations, and if so, are they able to differentiate the replies ? I just ran into this problem with paris-traceroute, the path were completely mixed up and stderr output looking like the following messages multiple times (IP addresses redacted): [WARN](TracertImpl.cc, 368)A reply received with bad original destination address A.B.C.D, should be W.X.Y.Z [WARN](TracertImpl.cc, 326)Bad return flow id 0x4d2 from E.F.G.H [WARN](TracertImpl.cc, 331)ICMP reserved words 0 0 0 0 0 As the probes use paris-traceroute, I prefer to be sure that the results are not flawed. David

2 4

Embedd built-in measurement page into website
by Bartsch, Rene 23 Jul '12

23 Jul '12

Hi, is there any way to embedd the "Built-in Measurements"-JQuery-Frame of my probes into a publically accessible website? Thanx for any hint, Renne -- Sent with love from the new tine 2.0 email client ... Please visit http://tine20.org

2 1

High inbound traffic causing packet loss?
by Tibor Djurica Potpara 23 Jul '12

23 Jul '12

Hello! I have just received an Atlas probe and I have been observing some weird readouts on the Atlas portal. Especially, occasional packet loss and considerable jitter, even to first and second hop destinations. I am surprised because even though I am a home user, I have a very stable connection (FTTH, 100/10 Mbps) and I've never experienced such connectivity issues. I've attached the probe directly to the ISP-provided switch that doesn't do IGMP snooping and since IP multicast is used for IPTV, high traffic (up to 50 Mbps) is occasionally flooded to all the switch ports. Taking into account that the probe is underpowered in terms of CPU, is it possible that it cannot handle such traffic and thus reports packet loss? If such is the case, I will move the probe behind a router to filter the multicast streams out. Best regards, Tibor Djurica Potpara

2 1

Flood-ping to measure packet loss?
by Bartsch, Rene 18 Jul '12

18 Jul '12

Hi, I've just started hosting a probe and I'm new to the list, so a "Hello" to all! :) Does the probe send simple pings or does it send flood pings (e.g. ping -f -c 1000 <destination>) for detection of packet loss? Best regards, Renne -- Sent with love from the new tine 2.0 email client ... Please visit http://tine20.org

3 3

Firmware 4470 to be released soon
by Ann Barcomb 11 Jul '12

11 Jul '12

Hello, Probe firmware version 4470 will be released soon. This version includes a small data structure change from 4460 which only affects DNS measurements: the addition of the optional field 'src_addr'. We have also published a correction for version 4460, which mistakenly listed a field 'src' for DNS measurements. This field does not exist in 4460. http://weir-dev.atlas.ripe.net/doc/data_struct#v4460_dns Kind Regards, Ann -- Ann Barcomb RIPE NCC Community Builder http://www.ripe.net Measurements Community Building +31 20 535 4444

2 1

Atlas infrastructure issues on Friday, 2012-06-29
by Robert Kisteleki 03 Jul '12

03 Jul '12

Dear Atlas users, As part of regular maintenance, last Thursday (2012-06-28) afternoon we upgraded the OS on a subset of our controlling infrastructure. During this work, some Atlas probes were told to hold back result reporting. A consequence of this was that when reconnecting, these probes sent in way more (and bigger) results than usual. Unfortunately, not all of the upgraded components ("controllers") had enough disk space to deal with the sudden increased data inflow. The combination of these events means that part of our infrastructure could not buffer results submitted from the probes, and as a result these results have been discarded. The event lasted approximately between 22h Thursday and 05h Friday (UTC), and affected about 30% of the probes. These probes will have a gap in their downloadable data sets and on their graphs. Since the event we increased the capacity of the involved infrastructure components. This will help us avoiding the same event occurring again. We apologise for the inconvenience this may cause. Regards, Robert Kisteleki RIPE NCC R&D

1 0