- ripe-atlas - mailman.ripe.net

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

Convert json traceroute output to normal traceroutes.
by Jan Hugo Prins 17 Oct '12

17 Oct '12

Hi, Because I'm a little more used to reading regular traceroute output instead of JSON files, I created a little python script to convert the ATLAS traceroute output to readable traceroutes. Comments are always welcome ofcourse. The whois information is gathered from Cymru using: https://github.com/JustinAzoff/python-cymruwhois -- Met vriendelijke groet / Best regards, Jan Hugo Prins Infra consultant E: jprins(a)betterbe.com T: +31-53-4800694 M: +31-6-26358951 S: jhaprins W: www.betterbe.com

4 5

Forcing https in Atlas
by Robert Kisteleki 16 Oct '12

16 Oct '12

Dear Atlas users, At the moment the Atlas UI servers allow regular, unsecured (http) connections from clients. For particular features, most notably anything that requires authenticated users, we're using secure (https) connections. Unfortunately, the potential mixing of the two schemes causes glitches and inconsistencies for some users. Therefore on 15 October we will start enforcing secure connections towards the Atlas UI servers (atlas.ripe.net and *.atlas.ripe.net). We'll do this by automatically redirecting all http queries to their https equivalents. This should not cause any changes to those of you who already use https by default, and should not cause any notable changes to anyone else. However, some clients (especially CLI based ones) may need some extra flags to deal with https connections. Regards, Robert Kisteleki

2 2

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