- ripe-atlas - mailman.ripe.net

Reconnecting probe 3508 - troubleshooting
by Michael-John Turner 24 Aug '16

24 Aug '16

Hi I've just reconnected probe 3508 to the network after a number of years offline (I think it was last online in November 2012?). Under the SOS history, I can see that it's making DNS queries successfully (using the DNS servers it receives by DHCP), but it's not connecting correctly to the RIPE network. The following is also displayed under SOS history: "This probe cannot connect on port 443 (HTTPS)". Any thoughts on where I can start troubleshooting? For test purposes I've connected the probe to my LAN, with full internet access. Cheers, MJ -- Michael-John Turner * mj(a)mjturner.net * http://mjturner.net/

7 10

Atlas Sagan error_message
by Wenqin SHAO 24 Aug '16

24 Aug '16

Dear list, I was using ripe.atlas.sagan to parse some ping measurements, one of them looks like the following in JSON format: rec = {u'af': 4, u'prb_id': 15843, u'result': [{u'error': u'connect failed: Network is unreachable'}], u'avg': -1, u'size': 20, u'from': u'88.174.18.20', u'proto': u'ICMP', u'timestamp': 1470009620, u'dup': 0, u'type': u'ping', u'sent': 0, u'msm_id': 1010, u'fw': 4730, u'max': -1, u'step': 240, u'src_addr': u'192.168.0.22', u'rcvd': 0, u'msm_name': u'Ping', u'lts': 641089, u'dst_name': u'192.228.79.201', u'min': -1, u'dst_addr': u'192.228.79.201'} Suppose that the above measurement is stored in a variable called rec as a dict, and I parse it using PingResult: from ripe.atlas.sagan import PingResult parsed_rec = PingResult(rec) I was expecting a no-empty string for parsed_rec.error_message, as we can see the measurement result contains an error string, however the parsed_rec.error_message is None. type(parsed_rec.error_message) <type 'NoneType’> Probably I misunderstood some part of the doc: error_message str If the result is an error, the message string is in here Could someone please clarify the exact functionality of this error_message? Many thanks in advance. Best, wenqin

1 0

Probe 10973 problem
by Vladislav Solovei 17 Aug '16

17 Aug '16

Hi. I have connected probe 10973 (which was offline several years) to the network. Firmware updated from 3.3.8 to 4010. "Status" said that "Your probe is currently connected." But on probe page i see the message: "Note: this probe is most likely not operational, and as such it has been written off as of 2013-12-03 15:44 UTC. The most likely reason for this is that the host could not be contacted." It is ok? :) Do i need to upgrade FW to latest version (tried to reboot probe several times, but fw version still 4010)? Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 1

RIPE Atlas "Commercial use" policy
by Robert Kisteleki 17 Aug '16

17 Aug '16

Dear colleagues, A few different organisations have approached us about using RIPE Atlas data for commercial products, services, reports, etc. We’ve now published conditions for the commercial use of RIPE Atlas data: https://atlas.ripe.net/get-involved/commercial-use/ Please read these conditions carefully if you plan on using RIPE Atlas data for any commercial purpose, and don’t hesitate to contact us if you have any questions. Regards, Robert Kisteleki RIPE NCC

1 0

Alternative to jq: gron
by Stephane Bortzmeyer 16 Aug '16

16 Aug '16

It seems many people here use jq to browse JSON files. I've been referred recently to gron <https://github.com/tomnomnom/gron> which is quite different: less features but probably simpler to use for beginners. Unlike jq, gron does not have a filtering language: it just formats the JSON in a way that makes simple to use traditional grep. Here is an example with measurement #4477822, a DNS one: % gron 4477822.json|more json = []; json[0] = {}; json[0].from = "178.248.214.8"; json[0].fw = 4730; json[0].group_id = 4477822; json[0].lts = 18; ... Selecting the values of the serial number is as simple as: % gron 4477822.json | grep SERIAL json[0].resultset[0].result.answers[0].SERIAL = 2223898795; json[0].resultset[1].result.answers[0].SERIAL = 2223898793; json[1].resultset[0].result.answers[0].SERIAL = 2223898790; json[1].resultset[1].result.answers[0].SERIAL = 2223898792; json[1].resultset[2].result.answers[0].SERIAL = 2223898795; json[2].resultset[0].result.answers[0].SERIAL = 2223898791; ... And you can turn back the result of the filtering into JSON.

2 1

Probe down - USB?
by İhsan Doğan 13 Aug '16

13 Aug '16

Hi, My probe went down this morning. Probably I'm running into the issue with the USB stick. I was thinking to replace the USB stick. Are there any special requirements (size, speed, etc.) for the USB stick? -Ihsan -- ihsan(a)dogan.ch http://blog.dogan.ch/

3 4

Re: [atlas] Probe down - USB?
by Colin Johnston 13 Aug '16

13 Aug '16

or mount the usb flash with linux ext3 and fsck check it :) Sent from my iPhone > On 13 Aug 2016, at 13:44, Budiwijaya <budiwijaya(a)ipv6.or.id> wrote: > > You don't need to change the USB stick, just unplug from the probe, > format the disk with fat32 using PC, plug back again to the probe, > and you're done. > > Thank you > Budiwijaya > > > On Sat, Aug 13, 2016 at 6:24 PM, =C4=B0hsan=C2=A0Do=C4=9Fan <ihsan(a)dogan.ch= >> wrote: >> Hi, >> >>> On Saturday, 13 Aug 2016 11:00 +0200, Estelmann, Christian wrote: >>> >>> every USB flash drive with 4 GB (or more) will do. >>> See >>> https://labs.ripe.net/Members/philip_homburg/troubleshooting-ripe-atlas-= > probes-usb-sticks >> >> Thanks. I have now ordered a 8 GB flash drive. >> >>> Don't forget that all data on the flash drive will be destroyed. >> >> But it's not affecting me, as it's pulling the configuration >> again, right? >> >> >> >> -Ihsan >> >> -- >> ihsan(a)dogan.ch http://blog.dogan.ch/ >

1 0

IPv4-only Anchors Now Supported
by Robert Kisteleki 12 Aug '16

12 Aug '16

Dear colleagues, We've decided to support "IPv4-only" anchors in ASNs where IPv6 is not available. You can learn more in this RIPE Labs article: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ipv4-only-ripe-atlas-an… Regards, Robert Kisteleki RIPE NCC

6 5

Incrementing LTS For probe 6106
by Clinton Work 09 Aug '16

09 Aug '16

Probe 6106 has an LTS value of at least 187450 and it continues to grow. ================================= Clinton Work Senior Design Specialist IP Core Network Integrity TELUS | Network and System Operations Phone: (403) 384-4027

2 1

Awarding credits for measurement results
by Robert Kisteleki 04 Aug '16

04 Aug '16

Dear probe and anchor hosts, When you create measurement results in RIPE Atlas, you’ll now get a little something extra back in the form of credits. From now on, we’re giving all RIPE Atlas probe and anchor hosts one credit back for every measurement result they generate. This means that most probe hosts will earn up to an additional 10,000 credits (50%) per day on top of the credits they get for keeping their probes online, anchor hosts will earn an additional roughly 200,000 credits (100%) daily, and DNSMON anchor hosts will receive roughly 1,000,000 additional credits. This is our way of rewarding the probe and anchor hosts who contribute the most to RIPE Atlas - enjoy! Regards, Robert Kisteleki RIPE NCC

2 1