- ripe-atlas - mailman.ripe.net

Filter for all results of a probe within a given timeintervall
by Lars Prehn 28 Jun '19

28 Jun '19

Hi everyone, I'm currently trying to retrieve ping and/or traceroute results for a specific probe in a given time interval via cousteau and/or the measurement API directly. It seems like I'm not clever enough to get it done. Is there a possibility to achieve this goal without iterating over each and every measurement to check whether or not the probes and the time match? Best regards, Lars

1 0

raspbian.net/raspbian.org ipv6 peering problems
by Thomas Schäfer 25 Jun '19

25 Jun '19

Hello, I am not sure if I am right here with my question. Does someone measurements to the server of "raspbian"? Their hoster (bytemark, iomart, zayo?) seems not to be able to establish correct peerings. At least the peering to AS3320 is broken. I already contacted 3320. They say zayo doesn't fulfill the minimum security requirements. Are more peerings broken? Regards, Thomas

4 5

When to consider a measurement finished
by Wouter de Vries 25 Jun '19

25 Jun '19

Hi all, I am currently trying to do some measurements according to the following steps: 1. create a one-off measurement 2. wait for it to finish, by periodically polling the msmid and checking the status. 3. fetch the results However, the system takes a pretty long time to set the status to finished, even when all results are already in (maybe 10 minutes?). What heuristics/method do you recommend to determine whether to consider a measurement as finished? One option I consider is to periodically fetch all results for a given msmid and checking if the number of results matches the number of probes assigned to the measurement. However, I suspect that causes a much higher load on the infrastructure. Best regards, Wouter de Vries

3 2

Probe off-line for 6 days due to bad firmware signature
by Novak Jirka 25 Jun '19

25 Jun '19

Hello, my probe 22424 is off-line due to bad firmware signature error. I try to boot it without USB stick many times, then i change the USB stick (replace the old one with new one), but it doesnt solve my problem. Could you help me? This is the information from my status page: Bad Firmware Signature What does this mean? The probe's firmware signature is wrong. How can I fix this? Power-cycle the probe and wait for a couple of hours. If probe doesn't come online you should try to reinitialise or even replace your flash drive. Please use the following procedure: 1. Unplug the probe from its power source 2. Remove the USB stick from the probe 3. Plug in the probe WITHOUT the USB stick 4. Wait for ten minutes 5. Insert the USB stick If it didn't help repeat these steps using another working USB stick that is at least 4GB in size. NOTE: This must be done on a network with working DHCP! It will NOT work if you have configured your probe to use a static IP address, because this mini-operating system does not have access to any statically configure IP addresses or DNS resolvers. If you have configured your probe to use a static IP address, the only thing you can do is move it to a network with working DHCP. When the probe is listed as "connected" again, it is safe to move the probe back to its original location. However, please note that we advise configuring your probe to use a static IP address only if you feel it is truly necessary to do so. Thx, Jiri

3 5

any clue rtt unreachable packet loss 100% com234.476.249
by kiran.gunana＠colruytgroup.com 25 Jun '19

25 Jun '19

Hello, Can some one help me with the reason behind me always getting RTT unreachable and packet loss 100% for every probe I choose to monitor one our service from internet in belgium. Is there something I am not doing right or can guid me a better way of doing it. Even though there is 100% packet loss , my credit balance is still being consumed. Kiran Gunana Network Engineer kiran.gunana(a)colruytgroup.com T +32 2 363 55 45 (Ext : 55711) Colruyt Group Edingensesteenweg 196 - 1500 Halle www.colruytgroup.com LinkedIn Twitter Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website

4 3

prometheus exporter atlas_exporter ripe atlas com234.553.762
by kiran.gunana＠colruytgroup.com 24 Jun '19

24 Jun '19

Hello, Is any body out there using "https://github.com/czerwonk/atlas_exporter" promethues exporter for exporting metrics from ripe atlas, started using it , wanted to know experience or best practices before spending more time on it. Only exporting ping metrics for now as explained in the article, any other metrics were tried and how were the results, any such help is appreciated :) Kind Regards, Kiran. Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website

1 0

Re: [atlas] any clue rtt unreachable packet loss 100% com234.553.190
by kiran.gunana＠colruytgroup.com 24 Jun '19

24 Jun '19

gboonie, Indeed you are right, I had the impression some thing else is breaking it, I did modify and got my results. rg, kiran ----- Original Message: com234.484.306 --------------------------------- From: Dave . (gboonie(a)gmail.com) To: kiran.gunana(a)colruytgroup.com Copy: ripe-atlas(a)ripe.net Subject: Re: [atlas] any clue rtt unreachable packet loss 100% com234.476.249 Date: 24 June 2019 (09:35) Hi, Your destination is not responding to ICMP (ping/traceroute). This is not an Atlas issue. Dave Op ma 24 jun. 2019 om 08:50 schreef <kiran.gunana(a)colruytgroup.com>: Hello, Can some one help me with the reason behind me always getting RTT unreachable and packet loss 100% for every probe I choose to monitor one our service from internet in belgium. Is there something I am not doing right or can guid me a better way of doing it. Even though there is 100% packet loss , my credit balance is still being consumed. Kiran Gunana Network Engineer kiran.gunana(a)colruytgroup.com T +32 2 363 55 45 (Ext : 55711) Colruyt Group Edingensesteenweg 196 - 1500 Halle www.colruytgroup.com LinkedIn Twitter Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website

1 0

delete old measurements from ripe com234.474.800
by kiran.gunana＠colruytgroup.com 24 Jun '19

24 Jun '19

Hello , Is there a way we can delete old measurements in ripe atlas measurements tab. Thes one's which are marked should be deleted for me. Kiran Gunana Network Engineer kiran.gunana(a)colruytgroup.com Colruyt Group Edingensesteenweg 196 - 1500 Halle www.colruytgroup.com LinkedIn Twitter Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website

1 0

Mailing list unsubscribe
by Christian Seifert 23 Jun '19

23 Jun '19

Hi, please unsubscribe me from the [atlas] mailing list. thanks

1 0

Mailing subscription
by Noe Manapo 23 Jun '19

23 Jun '19

Hi team, Please I want to join the ripe-atlas mailing list. Thank you Best regard Noe Manapo

2 2