- ripe-atlas - mailman.ripe.net

IPv4/DNS entry not updated
by Daniel Gomez 04 Dec '12

04 Dec '12

Good Morning everyone, After a DSL restart from my ISP at 2:00, atlas.ripe.net has not updated the IPv4 and with it the DNS. The proble is online but it is listed as down. "dig A p4065.probes.atlas.ripe.net" is showing my IP from yesterday. There is any way to push an "update", in order for the probe to register the right IP ? Greetings, Daniel Gomez

2 1

Two users managing one probe
by Matthäus Wander 03 Dec '12

03 Dec '12

Hi, is it possible to register the same probe by two different users? I would like to give my co-worker full access to a probe in our group LAN. Kind regards, Matt -- Universität Duisburg-Essen Verteilte Systeme Bismarckstr. 90 / BC 316 47057 Duisburg

5 5

New page: RIPE Atlas Community
by Vesna Manojlovic 13 Nov '12

13 Nov '12

Good morning :) Since yesterday, we have a new page that shows the activity of the RIPE Atlas users community: https://atlas.ripe.net/atlas/community We are publishing top-ten hosts of the "Always Up" probes, top-ten UDM users: "Big Spenders" -- people who spend most credits, by doing the most measurements, and the flowing list of new arrivals, with flags of their countries. (Now you can see that there was IETF last week -- Bert gave away 55 probes!) Enjoy your additional few minutes of fame, if you name appears on one of these lists :) We are looking forward to your compliments, and to the further wishes on what else would you like to see here... We will be featuring these top-users in our communication, so expect some more attention from us... Ciao, Vesna

2 1

RIPE Atlas nominated for an ISOC Award
by Vesna Manojlovic 08 Nov '12

08 Nov '12

Hi guys, a bit of good news and publicity: RIPE Atlas has been nominated for an award by the Netherlands chapter of the Internet Society (ISOC). Please find a short announcement on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-nominated-fo… Makes me feel proud for being part of it :) Since RIPE Atlas if build with your help - congratulations, well done! Cheers, Vesna

2 1

Re: [atlas] "down" probe resurrection
by Artur Russu 08 Nov '12

08 Nov '12

Hi Philip, Connected it to my home network, directly to my provider, it has now a public IP address assigned by ISP's dhcp. Powered it from an USB power outlet (it has now 5 V/500 mA). Still reboots... :( What do your logs say? I will leave it like this for 24 hours. I guess that if this setup will still fail we'll have to return the probe to RIPE. Where can I find the procedure of returning a probe? Best Regards, Artur Russu PS Engineer TD / MCN / Mobile Packet Core Orange Moldova S. A. Tel.: +373 22 975381 Tel.: +373 691 98381 E-mail: artur.russu(a)orange.md

1 0

Probe sending DHCP request, not accepting?
by Michael-John Turner 07 Nov '12

07 Nov '12

Hi My probe arrived late last week and I finally hooked it up late yesterday afternoon. All was working fine until around 3:30am today when I received an automated email to say that my probe was down. I restarted it at around 7:00am when I got up but that didn't help - ever since it's been requesting a new IP every 3-5 seconds but not accepting the offered lease. From my dhcpd logs: Nov 6 07:12:02 dreamland dhcpd: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via br0 Nov 6 07:12:02 dreamland dhcpd: DHCPOFFER on 192.168.1.248 to aa:bb:cc:dd:ee:ff via br0 Nov 6 07:12:05 dreamland dhcpd: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via br0 Nov 6 07:12:05 dreamland dhcpd: DHCPOFFER on 192.168.1.248 to aa:bb:cc:dd:ee:ff via br0 (where aa:bb:cc:dd:ee:ff is the correct MAC, I've just redacted it). I've allocated the device a static IP based upon its MAC. Help! :) My probe ID is 3508. -mj -- Michael-John Turner mj(a)mjturner.net <> http://mjturner.net/

2 4

Question on UDMs
by Roman A. aka BasicXP 07 Nov '12

07 Nov '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello! First of all, I'd like to thank RIPE for such an interesting project, allowing to study the availability of various resources online. I have a question. If I'd like to set up a UDM, that will only be designated for my probe only, will it require credits or using my own probe is "free"? Thank you in advance. _____ Best regards, Roman A. aka BasicXP x12ozmouse(a)ya.ru -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJQk7vQAAoJEBjQX5UpOG9YquQP/RptIW1NbaPdOPczWUTYvjxB ZMRNHWO/VX2RWeYMIRWcoUpqVJSV2f7Sy+55hG6kkkcnWvXb+Do9ro4/MsyXocsD y+AXzgt9zgEaQMtJsgr7gjOttRp4vl9Y9RiQ/NfAV/QMZj6YH0QuoqjhpSLDYs6H bA8rmCAx2RGOTlhEvQTBnwI/K6zO8Cp9psLyQ1hzkQeUqlZbOGtD4AGpBuLOcrGR cHyckfN3Lww83oaecBEU1wjgOgUuHzTQzoJKhU7CLr0h0EeBC60Qd9CD75CW7yUD pAZA3JUHhAsYh4Bw5NDihuRhRqDYfo+Ch63JZvdNxznWgRXPgNjm8dm9BqC3rOM2 /aYo4MnglRke7VqCw9vPkw1IW/aXCfx7OoOt4Vp17dKal5iOS/FT2u58qFkzeLRT Mn90I5EdcEbB+Nuv3GsjYBI94JrrSK2KtcoV235mSTAGYyAM665c3fVR+HkOc9Eu s/msjchT3MBlEini6HVqAqdTFDaCro+mOw53lKzCch8VQSJRTrbHz1S7RgRVK9dB 89E1ij3HhUv6Tz9y3fGvWmNwFCWxgkY0qnB8erlFDcTxBtg/ou+a5oU2Yd6Pa14n HaZfXgzSjpasDSTDzxfLzpG/w7qhAluQgo2Q+fViG8yweVWvCDT9DrvbTEuUrPFq TuxIjj0uFFzfPUZrSTrW =GYfh -----END PGP SIGNATURE-----

4 7

New RIPE Atlas features from October, and roadmap for November and beyond
by Vesna Manojlovic 01 Nov '12

01 Nov '12

Dear RIPE Atlas users, I am pleased to announce the whole lot of new things you can do with RIPE Atlas in/since October: - one new map (comparing TCP & UDM DNS measurements) - easier credits administration - and for some of you, we worked together further on Atlas Anchors There's more, with pictures, in the RIPE Labs article: https://labs.ripe.net/Members/becha/ripe-atlas-roadmap-october-2012-update We are also announcing many new features till the end of the year, and plans for few months in the future, for example: - more notifications - more APIs - promoting active users etc Please let us know if you want us to increase the priority of some of the ones listed in the article. Regards, and enjoy the measurements, Vesna

1 0

Fwd: Issues encountered with assigning .0 and .255 as usable addresses?
by Tore Anderson 24 Oct '12

24 Oct '12

Here's a suggestion for an Atlas experiment and subsequent RIPE Labs article. Do a ping measurement from all the probes to the .0 and .255 address of the same /24, plus to another control address in the same /24, and compare success rates. It's particularly interesting for me as my own personal home page is accessible at 87.238.60.0 at the moment.., Might also be worth checking it out for IPv6 at the same time (at least the case where the last 64 bits are all zeroes). Tore -------- Opprinnelig melding -------- Emne: Issues encountered with assigning .0 and .255 as usable addresses? Dato: Mon, 22 Oct 2012 22:07:50 +0000 Fra: Paul Zugnoni <paul.zugnoni(a)jivesoftware.com> Til: nanog(a)nanog.org <nanog(a)nanog.org> Curious whether it's commonplace to find systems that automatically regard .0 and .255 IP addresses (ipv4) as src/dst in packets as traffic that should be considered invalid. When you have a pool of assignable addresses, you should expect to see x.x.x.0 and x.x.x.255 in passing traffic (ie. VIP or NAT pool, or subnets larger than /24). Yet I've run into a commercial IP mgmt product and getting reports of M$ ISA proxy that is specifically blocking traffic for an IP ending in .0 or .255. Any experience or recommendations? Besides replace the ISA proxy…. Since it's not mine to replace. Also curious whether there's an RFC recommending against the use of .0 or .255 addresses for this reason.

2 1

New probe firmware released: version 4.480
by Vesna Manojlovic 24 Oct '12

24 Oct '12

Hi everyone, few days ago we have released a new version of the probe firmware: 4.480. It introduces few bug fixes, and improvements that enable us to work on new features, but that still require work on the User Interface to make it visible to users. Until now, about 1.500 probes have been upgraded to new firmware. Below are the technical details. Regards, Vesna * Fixed bug in traceroute when it has to deal with rfc4884 objects (mpls) that have a wrong size. * Delayed DNS name resolution in ping and traceroute. This feature will soon be enabled through the UI. * Fixed bug in HTTP GET where some characters where not properly escaped in generating the result JSON. * Fixed bugs in the libevent stub resolver to better handle DNS errors and timeouts (affects mostly httpget) * Limit the amount of measurement data that is sent as one unit. This prevents probes that have not connected to a controller for some time from overloading the controller. * The probe uptime is now in the DNS SOS messages that are sent by probes before they try to connect. This will allow making a distinction between various reasons for disconnects: e.g. probe reboot vs. network problems. (also published on https://atlas.ripe.net/announce )

1 0