- ripe-atlas - mailman.ripe.net

BGP hijacking
by Lukasz Trabinski 20 Dec '13

20 Dec '13

Hi I know that is not related with RIPE atlas, but maybe do know where to report in RIPE BGP hijacking topic? >From today BGP table: 46.0.0.0/8 xx 33 6939 5541 I 77.0.0.0/8 xxx 33 6939 5541 I 89.0.0.0/8 xxx 33 6939 5541 I 91.0.0.0/8 xxx 33 6939 5541 I 94.0.0.0/8 xxx 33 6939 5541 I 95.0.0.0/8 xxx 33 6939 5541 I

4 4

SOX (RS) has joined RIPE Atlas anchors
by Michela Galante 20 Dec '13

20 Dec '13

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called rs-beg-as13004 and is hosted by SOX (Serbian Open eXchange) in Belgrade, Serbia. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

DANTE (UK) has joined RIPE Atlas anchors
by Michela Galante 19 Dec '13

19 Dec '13

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called uk-lcy-as20965 and is hosted by DANTE in London, United Kingdom. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

ATE (FR) has joined RIPE Atlas anchors
by Michela Galante 17 Dec '13

17 Dec '13

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called fr-zdb-as35625 and is hosted by ATE in Sainghin en Mélantois, France. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

Emergency RIPE Atlas firmware upgrade
by Robert Kisteleki 17 Dec '13

17 Dec '13

Dear RIPE Atlas users, We want to let you know about a recent issue in the RIPE Atlas system involving an open port on the latest generation (v3) probes. Due to an issue with the latest firmware release, a subset of the v3 probes were listening to incoming connections on an open port that should not have been left open. As a secondary measure, however, access to this port required credentials only available to the RIPE Atlas probe developers. It therefore never presented open access to the probes. This port (SSH) is used for development purposes in our internal development environment. We upgraded the v3 probes to a new, corrected firmware version, and improved the checks in our firmware release process. We would like to thank ZeelandNet for reporting the issue to us. We want to assure you that the security of the RIPE Atlas system is important to us. We are continually improving the controlling infrastructure as well as the probes themselves in order to prevent vulnerabilities. We apologise for this issue and want to stress that no probes were actually affected in any way. You can learn more about the security of the RIPE Atlas system on our dedicated security page at: https://atlas.ripe.net/docs/security/ Thank you for your continuing support of RIPE Atlas. Regards, Robert Kisteleki RIPE NCC

10 17

IPv6 Gateway Undetermined/Unknown
by Christopher Werny 17 Dec '13

17 Dec '13

Hi Everybody, we received our probe a couple of days ago and after successful "deployment" (with static configuration), I noticed that the Configuration pane states that the IPv6 gateway is in the state "Undetermined/Unknown". It is correctly configured and IPv6 measurements are working fine. I couldn't find anything related to my "observation", hence why I am asking here. I just want to make sure I did everything right and whether this might be a known bug or limitation? Thanks for your time. Cheers, Christopher

2 1

Enjoy the holiday season with photos of RIPE Atlas probes
by Vesna Manojlovic 13 Dec '13

13 Dec '13

Dear colleagues, we have uploaded lots of pretty photos to the Community page: https://atlas.ripe.net/get-involved/community/#!tab-actionshots I am attaching the screenshot and one, most colorful photo. Please upload your own photos, and enjoy the holiday season. Share and Enjoy :) Vesna

1 0

Re: [atlas] Measurements at an interval
by warwick 13 Dec '13

13 Dec '13

Hi Daniel, I sent an email (included below.) outlining a measurement with a specific interval done through the API and listed the response, please look at the email below. As for the Web UI measurement here is an example: /{u'result': u'/api/v1/measurement/1044471/result/', u'status': {u'id': 4, u'name': u'Stopped'}, u'msm_id': 1044471, u'interval': 1200, u'description': u'', u'participant_count': 50, u'can_visualise': False, u'resolve_on_probe': False, u'start_time': 1386161734, u'af': 6, u'creation_time': 1386161734, u'is_oneoff': False, u'stop_time': 1386165633, u'all_scheduling_requests_fulfilled': True, u'resolved_ips': [u'2001:7b8:40:1:d0e1:0:0:1'], u'dst_asn': u'12859', u'query': {u'type': u'AAAA', u'class': u'IN', u'value': u'nlnetlabs.nl.'}, u'is_public': True, u'type': {u'id': 7, u'name': u'dns'}, u'dst_addr': u'2001:7b8:40:1:d0e1:0:0:1', u'dst_name': u'2001:7b8:40:1:d0e1::1'}// / Robert Kisteleki suggested I send it through to atlas(a)ripe.net which I did and it has been listed as: [ripe.net #1113749] I received a response from Robert Kisteleki (which is the very last email included below), he said it might be a week or later until this gets investigated so he was right on the money :-) . Thank you for your response and we hope to see this bug(or whatever it is) get squashed :D P.S. If you could, please include Willem Toorop(Willem(a)nlnetlabs.nl) in the response as he was the one to mention this limitation to me and the one who suggested I email about this. He also sent an email outlining this issue but heard no response so I'm sure he would like to hear when a resolution to this limitation/bug/whatever has been found. P.P.S. At the bottom of the first included email is our work around which is get the probes specific to our needs (ipv6/4 etc..) and the chunk them into sizable chunks(50 probes work). Kind regards, Warwick Louw -------- Original Message -------- Subject: Re: [atlas] Measurements at an interval Date: Wed, 04 Dec 2013 14:04:05 +0100 From: warwick <warwick(a)nlnetlabs.nl> To: atlas(a)ripe.net Hello, Regarding the previous email: Measurements at an interval, below is the Json constructed for the measurement: / / /{'definitions': [{'description': '', 'use_probe_resolver': False, 'af': 6, 'query_argument': 'nlnetlabs.nl', 'query_type': 'AAAA', 'interval': 1200, 'query_class': 'IN', 'type': 'dns', 'is_oneoff': False, 'recursion_desired': False, 'target': '2001:7b8:40:1:d0e1::1'}], 'stop_time': 1386168052, 'probes': [{'requested': 100, 'type': 'area', 'value': 'WW'}]}/ And below is the response: /{"error": {"code": 104, "message": "You do not have enough credit to schedule this measurement."}}/ It seems as though it's a trivial mistake, that I might actually not have enough credits to perform this measurement but I'm sure I do since it's a simple DNS query with only 100 probes. With 50 probes: /{'definitions': [{'description': '', 'use_probe_resolver': False, 'af': 6, 'query_argument': 'nlnetlabs.nl', 'query_type': 'AAAA', 'interval': 1200, 'query_class': 'IN', 'type': 'dns', 'is_oneoff': False, 'recursion_desired': False, 'target': '2001:7b8:40:1:d0e1::1'}], 'stop_time': 1386168333, 'probes': [{'requested': 50, 'type': 'area', 'value': 'WW'}]}/ This request is executed as expected. With the following response: /{u'measurements': [...]}/ (measurement id removed.) To get past this problem we have been chunking our probes in groups of 50. I just thought you might be interested. Kind regards, Warwick Louw -------- Original Message -------- Subject: [ripe.net #1113749] Re: [atlas] Measurements at an interval Date: Wed, 4 Dec 2013 15:24:32 +0100 From: Robert Kisteleki <atlas(a)ripe.net> Reply-To: atlas(a)ripe.net To: warwick(a)nlnetlabs.nl Hi, Got it, we'll look into this (probably early next week when the best person for this is back). Regards, Robert On 2013-12-04 14:09:08, warwick(a)nlnetlabs.nl wrote: > Hello, > > Regarding the previous email: Measurements at an interval, below is the > Json constructed for the measurement: > / > / > > /{'definitions': [{'description': '', 'use_probe_resolver': False, > 'af': 6, 'query_argument': 'nlnetlabs.nl', 'query_type': 'AAAA', > 'interval': 1200, 'query_class': 'IN', 'type': 'dns', 'is_oneoff': > False, 'recursion_desired': False, 'target': > '2001:7b8:40:1:d0e1::1'}], 'stop_time': 1386168052, 'probes': > [{'requested': 100, 'type': 'area', 'value': 'WW'}]}/ > > > And below is the response: > > /{"error": {"code": 104, "message": "You do not have enough credit > to schedule this measurement."}}/ > > > It seems as though it's a trivial mistake, that I might actually not > have enough credits to perform this measurement but I'm sure I do since > it's a simple DNS query with only 100 probes. > > With 50 probes: > > /{'definitions': [{'description': '', 'use_probe_resolver': False, > 'af': 6, 'query_argument': 'nlnetlabs.nl', 'query_type': 'AAAA', > 'interval': 1200, 'query_class': 'IN', 'type': 'dns', 'is_oneoff': > False, 'recursion_desired': False, 'target': > '2001:7b8:40:1:d0e1::1'}], 'stop_time': 1386168333, 'probes': > [{'requested': 50, 'type': 'area', 'value': 'WW'}]}/ > > > This request is executed as expected. With the following response: > > /{u'measurements': [...]}/ (measurement id removed.) > > > To get past this problem we have been chunking our probes in groups of > 50. I just thought you might be interested. > > Kind regards, > Warwick Louw > -- Robert Kisteleki, R&D Manager, RIPE NCC RIPE Atlas Team

1 0

Measurements at an interval
by warwick 13 Dec '13

13 Dec '13

Hello again, I stumbled upon something peculiar when submitting measurements with an interval via the API. It seems when submitting a measurement with a specific interval the maximum number of probes I could use was 50, but through the web interface the exact measurement is acceptable with many more probes. Kind regards, Warwick Louw

2 1

Spectrum Internet Ltd (UK) has joined RIPE Atlas anchors
by Michela Galante 11 Dec '13

11 Dec '13

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called uk-cdf-as48294 and is hosted by Spectrum Internet Ltd in Cardiff, United Kingdom. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0