- ripe-atlas - mailman.ripe.net

Feature-suggestion: "round-robin" probes
by Alexander Mayrhofer 11 Jun '12

11 Jun '12

Hello, i'm figuring how RIPE atlas could be most useful for assisting in monitoring our Ancast Network, and came up with the following idea: The Atlas network has a big advantage over other monitoring /measurement networks, which is obviously its sheer size (and topological diversity). Rather than using the Atlas network for pure performance measurements, i would love to be able to use Atlas for reachability measurements (and understand which Anycast location attracts traffic from which region, and how this changes over time). These reachability / topology discovery measurements do not need to be nearly as frequent as the performance measurements, but should utilize all available probes. So, instead of being able to use 10 probes to run a continous performance test (say, DNS query every 300 seconds), i would rather like to be able to use a very high number of probes (best case: "all"), but have each of the probe eg. perform just one traceroute per day (or, even once per week would be enough). This would give me an excellent overview about the topology, but is not possible using the current limits of the UDMs. However, instead of allowing users to allocate measurements to a much higher number of probes, this functionality would also be possible be adding some "probe round-robin" feature to the control infrastructure, for example "randomly allocate a new set of probes every xx seconds". If that feature would exist, i could implement the above reachability test with the following parameters: Test: traceroute Number of probes: 10 Measurement interval: 3600 Swap probe-set interval: 10800 (NEW feature) (which would re-allocate new probes every 3 hours, theoretically working through all 1500 probes about every month?). An obvious alternative would be functionality where i could "queue" "single-shot" measurements for the whole network (since chances are low i would get every probe if they are randomly assigned). comments? Suggestions? Alternatives? Alex Mayrhofer Head of R&D nic.at

5 13

Cannot ping 128.0.0.1, 128.0.24.1
by ckeck＠texoma.net 31 May '12

31 May '12

Cheers! Looked at my stats, and it looks as if not only my probe can't ping 128.0.0.1 and 128.0.24.1. The probe is hooked up to a router on a Verizon FIOS (fiberoptic) line. To see if that's a systemic issue, I pinged the same addresses from systems at work, as well as TMobile's (U.S.) wireless broadband, and they respond just fine. Question now is, where is the problem at? THX! -Cornelius -- Cornelius Keck -----------------------------------------> ckeck(a)texoma.net Beware, so long as you live, of judging men by their outward appearance. Jean de La Fontaine

4 4

v6 support
by Randy Bush 29 May '12

29 May '12

i am not understanding why probe 2285 does not seem to even get an ipv6 address on the in-rack lan, while a whole lot of other devices do. and 2283 managed to get a v6 address but no gateway, and of course no v6dns. what do the little puppies want, nd ra ??? randy

4 8

Ping to labs.ripe.net
by Dan Luedtke 16 May '12

16 May '12

Hi probe-admins, I see this on all my probes, do you have the same problem? Ping (IPv4) labs.ripe.net 193.0.6.153 100% packet loss regards Dan -- Dan Luedtke http://www.danrl.de

3 2

baccouche2@yahoo.com t'invite à rejoindre Twoo
by Thomas via Twoo 10 May '12

10 May '12

Je viens de découvrir un nouvel outil pour rencontrer du monde en ligne : Twoo.com. ---------------------------------------------------------------- Hi, ripe-atlas Thomas vient de trouver un nouvel outil pour rencontrer du monde en ligne et aimerait que tu te joignes à la fête : Twoo.com Copie/colle le lien ci-dessous dans ton navigateur : http://twoo.com/m/39jVbXL_ Tu ne veux plus recevoir ces mails? Clique sur ce lien: /unsubscribe/?email=ripe-atlas%40ripe.net&code=37d33a52e2b420b3962ae52bae8ce1cb&typeid=2---------------------------------------------------------------- TWOO NV/SA, UBIDOCA Center 3145, 105 Route Pommiers, F-74370 Bellevue, France info-fr(a)twoo.com BE0834322338.

1 0

Credit Consumption
by Jens Weibler 09 May '12

09 May '12

Hi, I just noticed that I can't create new measurements anymore: "Your current daily credit consumption (62496) is higher than you allowed (15000)." But I've got enough credits on my balance and I don't want to stop my measurements. Why can't I just change the probe count or the measurement interval? ;) -- 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 2

New on RIPE Labs: Test your IPv6 Reachability by Using RIPE Atlas
by Ann Barcomb 09 May '12

09 May '12

[apologies for duplicate mails] Dear colleagues, RIPE Atlas can now be used to test your IPv6 reachability, even if you do not host a RIPE Atlas probe - provided you are a RIPE NCC member. More details can be found on RIPE Labs: https://labs.ripe.net/Members/becha/test-your-ipv6-reachability-using-ripe-… If you have any comments or questions, please let us know. Kind Regards, Ann Barcomb

1 0

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