- ripe-atlas - mailman.ripe.net

A Case Study of AAAA Filtering
by Vesna Manojlovic 15 Oct '12

15 Oct '12

Hi all, at RIPE 65, Lorenzo Colitti from Google raised the question whether Internet users would see significant filtering of AAAA DNS queries or replies, either by their ISP or by their Customer Premise Equipment (CPE). Emile & Philip used RIPE Atlas to provide an answer to this question. https://labs.ripe.net/Members/emileaben/ripe-atlas-a-case-study-of-aaaa-fil… Regards, Vesna

4 5

Atlas main database maintenance
by Andreas Strikos 15 Oct '12

15 Oct '12

Dear Atlas users, Tomorrow around 09:30 CEST we will bring down our main database for maintenance. Hopefully, the whole process will not take more than 2 hours. The majority of the web site functionalities and user interaction with the system will not be available but we don't expect any loss of data flowing in from the probes. We are sorry for any inconvenience this might cause. Regards, Andreas Strikos

1 0

traceroute via ICMP?
by Jens Weibler 10 Oct '12

10 Oct '12

Hi, how is the development of traceroute via ICMP going? My central firewall team doesn't like opening many udp-ports for traceroute :( -- Jens Weibler IT-Services Hochschule Darmstadt www.h-da.de University of Applied Sciences Fachbereich Informatik www.fbi.h-da.de Schöfferstr. 8b D-64295 Darmstadt Tel +49 6151 16-8425 Fax +49 6151 16-8935 jens.weibler(a)h-da.de

2 3

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