- ripe-atlas - mailman.ripe.net

Routing glitch between BSNL and F Root
by Anurag Bhatia 26 Apr '12

26 Apr '12

Hello, There has been some routing glitch in the F root server instance running in Chennai, India by niXi AS 24049. Govt. owned BSNL AS9829 routers are not hearing any BGP announcements and thus F root does not works at all on BSNL. anurag@laptop ~ $ traceroute f.root-servers.net -A traceroute to f.root-servers.net (192.5.5.241), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) [AS8151/AS28513] 1.552 ms 2.040 ms * 2 117.207.48.1 (117.207.48.1) [AS9829] 26.010 ms 28.433 ms 31.136 ms 3 218.248.173.42 (218.248.173.42) [AS9829] 34.497 ms 35.968 ms 38.372 ms 4 218.248.250.86 (218.248.250.86) [AS9829] 91.784 ms 94.430 ms 96.794 ms 5 * * * 6 * * * 7 * * * 8 * * * I have been hosting RIPE Probe #1032 and here is F Root connectivity data from proble: [image: Inline image 1] As we can see root server is not accessible at all from Jan and even in Nov, Dec last year it was available with over 300ms latency which indicates network was not using Chennai anycast node since latency between this test probe placed in Haryana (North India) and Chennai (South India) should be around 70ms. Thanks. -- Anurag Bhatia anuragbhatia.com or simply - http://[2001:470:26:78f::5] if you are on IPv6 connected network! Twitter: @anurag_bhatia <https://twitter.com/#!/anurag_bhatia> Linkedin: http://linkedin.anuragbhatia.com -- This message has been scanned by Kaspersky Anti-Virus. For more information about data security please visit http://www.kaspersky.com and http://www.viruslist.com

3 4

Request for RIPE Atlas probe DHCP change.
by Leo Bicknell 23 Apr '12

23 Apr '12

Could the RIPE Atlas probe DHCP client please be configured to send a ClientID, perhaps "RIPEAtlasProbe"? Many home gateways show a list of DHCP clients and list the client ID. It would make it much easier to identify which device is which using these tools. -- Leo Bicknell - bicknell(a)ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/

4 5

ATLAS as mechanism for route policy discovery
by Alexander Asimov 23 Apr '12

23 Apr '12

Hello. During last decade much attention was paid to topology discovery at inter-domain routing level. But most of these projects are only targeted on physical links discovery; at the same time there was little opportunity to check the real use of links by single AS. The knowledge of Autonomous System relationships from single AS view could be used in many cases. For example it could be used during designing AS or for traffic flow engineering purposes. In case to solve this problem we have invented several active probing algorithms for discovering real routing policy map from single AS view. One of them is based on using spoofed source IP. We send an echo request with record route option and source IP from our address space and as the result we can see the part of reverse trace from destination. This helps to understand which links are used by our AS. It is a kind of snapshot. This information is used in iteration process and the all data results in model of AS relationships which could be reversed to single view for every AS. At the current moment we cover with help of our nodes about 40% of transit AS, but with help of RIPE Atlas we will be able to cover more than 90%, and give back to community a tool for traffic flow prediction at interdomain routing level. Spoofing is obviously bad in most of cases, but not this time. We need opportunity to strictly spoof only one IP from our address space. The list technical requirements of our proposal: 1. 178.248.239.238 always will be used as spoofed address; 2. There will be about 15 experiments every day; 3. Each experiment will last not more than 10 minutes; 4. The total approximate packet generation activity from all nodes will be about 500 packets per second; 5. We need opportunity to have different measurement plans (list of destinations) on different nodes. We work with Planet Lab nodes in the same way: every day there is a new .gz archive with list of targets for all nodes, every node unpacks it and use then only a sublist of destinations, but the packet generation script is same on all nodes. We're open to discussion on procedures described above. Best regards, Alexader Asimov

1 0

Measure DNS resolve times
by Daniel AJ Sokolov 10 Apr '12

10 Apr '12

Hello, My ISP has changed something and as a result DNS lookups have slowed down considerably. How would I set up a User Defined Measurements to perform certain lookups on a nameserver and measure the response times? Thank you Daniel AJ -- Follow me on twitter @newstik http://twitter.com/newstik

3 2

RIPE Atlas User-Defined Measurements Are Here!
by Ann Barcomb 04 Apr '12

04 Apr '12

Dear Atlas Hosts and Sponsors, We are pleased to announce our first roll-out of user-defined measurements (UDM) for RIPE Atlas. As of today, all hosts and sponsors on this mailing list are invited to run custom measurements. Over the coming weeks we will continue to roll out UDM to a wider audience. To access UDM, either click on the link at the top right when you are logged in to the RIPE Atlas website, or go directly to: https://atlas.ripe.net/atlas/udm.html For the time being, we have created a fairly low rate limit, which we expect to increase over time. More information about limits and other aspects of the UDM system can be found in the documentation: https://atlas.ripe.net/doc/udm Discussion and questions about UDM can be directed to this mailing list (ripe-atlas(a)ripe.net) or to atlas-dev(a)ripe.net. You may also be interested in joining us at the UDM "Birds of a Feather" (BoF) session at RIPE 64 in Ljubljana, on Thursday, 19 April after the Measurements, Analysis and Tools (MAT) Working Group session. https://ripe64.ripe.net/programme/meeting-plan/bof/ Happy measuring! - The RIPE Atlas team

9 18

labs.ripe.net dead?
by damkol＠gmail.com 04 Apr '12

04 Apr '12

Hello. 29.03.2012 labs.ripe.net stopped respond to icmp. https://zpm02.atlas.ripe.net/atlas/rrd.png?prb_id=741&msm_id=1007&type=week… >From other places with other internet connections also not respond to icmp. -- damkol(a)gmail.com

3 2

Re: [atlas] Probe 2317 is down
by Colin Johnston 02 Apr '12

02 Apr '12

fixed internal network :) Can a request for enhancement be made for notification of probe goes up to the owner email ? Colin On 31 Mar 2012, at 08:30, RIPE Atlas wrote: > Dear colin, > > Your probe 2317 is down since 2012-03-31 06:56:49 UTC > > This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe goes is down for more than 30 minutes. > > If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/atlas/myprobes.html, click on probe 2317, in the opened tab select Probe's Settings -> Notifications and change your settings. > > Atlas team

2 1

change ownership of probe
by Thanos Tsakalos 02 Apr '12

02 Apr '12

Hello to all, Is there a way to change the ownership of a probe? Will it be ok if the probe is re-registered under the new email address (mac and pin are known) ? Or is there any other method to do it properly? Thank you, Triantafyllos

2 1

Altas switching to "RIPE NCC Access"
by Vesna Manojlovic 27 Mar '12

27 Mar '12

Dear Atlas people, Tomorrow during the day we'll switch RIPE Atlas to use RIPE NCC Access, our Single-Sing-On mechanism. Maintenance will happen during our working hours (9-5, Amsterdam time), and it will last between 1 and 3 hours. During this, Atlas login will be disabled. The Atlas web site will have limited functionality. After the completed maintenance, the "log in" link on Atlas web site will be re-directed to the RIPE NCC Access log-in page. For other possible outcomes on this migration, please read Robert's article: https://labs.ripe.net/Members/kistel/preparing-ripe-atlas-for-ripe-ncc-acce… Single-Sign-On functionality will enable us to share Atlas with the users of other RIPE NCC services; it will make the user-experience smoother for everyone who is accessing multiple services from the RIPE NCC (such as LIR Portal, RIPE Labs or RIPEstat), and will enable many new personalized features in the future. If you have any questions, please let us know. Thank you, Vesna

4 4

Request to test TCP and UDP to the root servers separately.
by Leo Bicknell 23 Mar '12

23 Mar '12

My day job has had some interesting discussions lately about TCP to the root servers based on a few odd behaviors we've had reported to us over the past few years. There aren't any surprises in this data, it's been known for a long time some people think DNS is UDP only for instance, some firewalls are broken, and so on. What we realized though is that there is no wide-spread measurement of how often TCP is a problem. Immediately my thought went to the Atlas probe network. It's distributed enough it could give an interesting indication of how often TCP DNS fails compared to UDP DNS. Perhaps the rates are so similar it's a non-issue, perhaps TCP fails much more often. Would it be of interest to the Atlas community to have the probes try and query "." via both UDP and TDP from each of the 13 root servers (perhaps v4 and v6 separately), report back that data, and then generate a report on the results? I would be happy to assist in preparing or presenting a report on the results! -- Leo Bicknell - bicknell(a)ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/

4 7