From aformoso at ripe.net Thu May 3 13:50:20 2018 From: aformoso at ripe.net (Agustin Formoso) Date: Thu, 3 May 2018 13:50:20 +0200 Subject: [atlas] Minor change in the API Participation Requests endpoint In-Reply-To: References: Message-ID: <889F2EEC-0FF1-402A-97D0-710659DC60DE@ripe.net> Dear users, This is a quick update to let you know this change has been rolled-out today. Regards ? Agust?n RIPE NCC > On 16 Apr 2018, at 15:31, Agustin Formoso wrote: > > Dear Atlas users, > > We're planning to roll-out a minor change in the API Participation Requests endpoint. We'll be changing the response that gets sent out when a Participation Request is submitted. Although minor, the change may break your code if you are making use of the response. > > Current response example: > [35878] > > Future response example after roll-out: > > { > 'request_ids': [35878] > } > > We plan to put this change into production two weeks from now. > > For those who don't know what Participation Requests are, they allow you to add or remove probes from a pre-existing measurement. You can find more information in https://atlas.ripe.net/docs/api/v2/manual/participation_requests.html > > Regards > > ? > > Agust?n Formoso > RIPE NCC > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2611 bytes Desc: not available URL: From belafkih.hayat at gmail.com Sun May 6 22:50:08 2018 From: belafkih.hayat at gmail.com (BELLAFKIH hayat) Date: Sun, 6 May 2018 22:50:08 +0200 Subject: [atlas] Firmware version 4660 Message-ID: Dear Atlas users I am using data collected by RIPE Atlas probes, I found data with a firmware *4660*, but I can't find definition of the structure related to this firmware here . Any help? Regards *Hayat BELLAFKIH* -------------- next part -------------- An HTML attachment was scrubbed... URL: From philip.homburg at ripe.net Mon May 7 15:08:07 2018 From: philip.homburg at ripe.net (Philip Homburg) Date: Mon, 7 May 2018 15:08:07 +0200 Subject: [atlas] Firmware version 4660 In-Reply-To: References: Message-ID: <723a6f5b-d4ad-ce97-f5c2-16f23041b786@ripe.net> Hi, > I am using data? collected by RIPE Atlas probes, I found data with a> firmware /*4660*/, but I can't find definition of the structure related> to this firmware here . For 4660 you need Section 7: https://atlas.ripe.net/docs/data_struct/#v4610 I made some changes to make the ranges more clear in the index, but that will only go out on the next deploy, which is probably two weeks from now. Philip From gponikie at akamai.com Mon May 7 17:50:11 2018 From: gponikie at akamai.com (Ponikierski, Grzegorz) Date: Mon, 7 May 2018 15:50:11 +0000 Subject: [atlas] Probe #27786 invalid location Message-ID: Hi RIPE team! Probe #27786 is located UK but Atlas see it as US probe. It make measurements incorrect. Can you verify it? Regards, Grzegorz -------------- next part -------------- An HTML attachment was scrubbed... URL: From jterbeest at ripe.net Mon May 7 18:57:32 2018 From: jterbeest at ripe.net (Johan ter Beest) Date: Mon, 7 May 2018 18:57:32 +0200 Subject: [atlas] Probe #27786 invalid location In-Reply-To: References: Message-ID: <2bf21e53-5d92-f42f-dc0b-775944755084@ripe.net> Hi Grzegorz, On 07/05/2018 17:50, Ponikierski, Grzegorz wrote: > > Hi RIPE team! > > ? > > Probe #27786 is located UK but Atlas see it as US probe. It make > measurements incorrect. Can you verify it? > Thanks for reporting this. We have corrected the country to United Kingdom as it should be. We will investigate why the country was set incorrectly while the probe was located in the UK as this normally should not be possible. Kind regards, Johan ter Beest RIPE Atlas Team > > ? > > Regards, > > Grzegorz > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pEpkey.asc Type: application/pgp-keys Size: 1765 bytes Desc: not available URL: From afshar.milad89 at gmail.com Wed May 9 10:05:04 2018 From: afshar.milad89 at gmail.com (Milad Afshari) Date: Wed, 9 May 2018 12:35:04 +0430 Subject: [atlas] CLI Message-ID: Hi all, It's more than a month that I have a lot of issues with running measurements through CLI here from IRAN, the measurements starts correctly but the results will not be displayed. Do you have any idea to fix this or anyone else have the same problem? Many thanks Milad Afshari -------------- next part -------------- An HTML attachment was scrubbed... URL: From GeertJan.deGroot at xs4all.nl Wed May 9 11:54:23 2018 From: GeertJan.deGroot at xs4all.nl (Geert Jan de Groot) Date: Wed, 9 May 2018 09:54:23 +0000 Subject: [atlas] Atlas #50012 handed over.. Message-ID: Hi, Lia just handed over probe 50012 (that's the new hardware version), and I plugged it into the AIS/AfriNIC network here in Dakar. Can you please make this probe "mine" so I can administer it? For the next few days, will try a few things (and please do so yourself!) My existing probe is 16233. Currently it is powered through the USB port of another device, I will try PoE later (it will switch to 100 mbit then). Currently it seems to do 1gbit. Will make notes and share with you. GJ From noodi.net at gmail.com Wed May 9 13:04:04 2018 From: noodi.net at gmail.com (Amin Khoshnood) Date: Wed, 9 May 2018 15:34:04 +0430 Subject: [atlas] Atlas #50012 handed over.. In-Reply-To: References: Message-ID: Dear Geert Jan de Groot, This is a pubic mailing list. You can ask Lia to transfer probe to your account (email address needed) or you can add probbe by it's MAC address to your account. https://atlas.ripe.net/about/faq/#can-i-transfer-a-probe-to-a-new-host Best Regards. On Wed, May 9, 2018 at 2:24 PM, Geert Jan de Groot < GeertJan.deGroot at xs4all.nl> wrote: > Hi, > > Lia just handed over probe 50012 (that's the new hardware version), and I > plugged it into the AIS/AfriNIC network here in Dakar. > > Can you please make this probe "mine" so I can administer it? > For the next few days, will try a few things (and please do so yourself!) > > My existing probe is 16233. > > Currently it is powered through the USB port of another device, I will try > PoE later (it will switch to 100 mbit then). > Currently it seems to do 1gbit. > > Will make notes and share with you. > > GJ > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gponikie at akamai.com Fri May 11 20:16:16 2018 From: gponikie at akamai.com (Ponikierski, Grzegorz) Date: Fri, 11 May 2018 18:16:16 +0000 Subject: [atlas] Probe #33346 invalid location Message-ID: Hi! Found another probe assigned to incorrect country: https://atlas.ripe.net/probes/33346/#!tab-network Probe is located in Hong Kong but Atlas things it's China ;) Can you fix it? Regards, Grzegorz -------------- next part -------------- An HTML attachment was scrubbed... URL: From adavies at ripe.net Mon May 14 14:30:59 2018 From: adavies at ripe.net (Alun Davies) Date: Mon, 14 May 2018 14:30:59 +0200 Subject: [atlas] New on RIPE Labs: Update on the RIPE Atlas Anchor VM pilot Message-ID: <2AF5260B-97E8-45E7-9A8F-C38602A32992@ripe.net> Dear colleagues, We recently published an update on our pilot programme to assess the feasibility of introducing virtual machines to the pool of RIPE Atlas anchors. Read all about it in this RIPE Labs article from Robert Kisteleki: https://labs.ripe.net/Members/kistel/update-on-the-ripe-atlas-anchor-vm-pilot Best regards, Alun Davies RIPE NCC -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2607 bytes Desc: not available URL: From gponikie at akamai.com Thu May 24 22:02:45 2018 From: gponikie at akamai.com (Ponikierski, Grzegorz) Date: Thu, 24 May 2018 20:02:45 +0000 Subject: [atlas] Aggregator for TXT record Message-ID: Hi! I wanted to use Aggregator feature for DNS measurement but looks like it doesn't work with TXT record. Anybody has experience with this feature? Does Aggregator support TXT record? Regards, Grzegorz -------------- next part -------------- An HTML attachment was scrubbed... URL: From gponikie at akamai.com Sun May 27 13:04:11 2018 From: gponikie at akamai.com (Ponikierski, Grzegorz) Date: Sun, 27 May 2018 11:04:11 +0000 Subject: [atlas] Probe #595 invalid location Message-ID: <7C756C93-2194-4BF1-BCCE-15DD2C0B9B03@akamai.com> Hi! I cannot open page for probe #595 (question is why, it's private?) but from what I see this probe is marked as US probe: [cid:image001.jpg at 01D3F5BB.36A72710] But AS 29422 is Finish ISP and when you check traceroute from this probe you will see that's for sure it's more Finland than US. Traceroute: 595 ----------------- 1 - 192.168.0.254 NA None NA 1.614ms 2 - 83.150.126.202 29422 None NBLNETWORKS-AS Nebula Oy, FI 15.026ms 3 - 188.117.15.250 29422 rtr1-te4-3.lau.hel.fi.nblnet.com NBLNETWORKS-AS Nebula Oy, FI 14.762ms <- Finland 4 - 80.239.132.5 1299 hls-b2-link.telia.net TELIANET Telia Carrier, SE 15.005ms <- Finland 5 - 80.91.245.214 1299 s-bb4-link.telia.net TELIANET Telia Carrier, SE 22.251ms <- Sweden 6 - 80.91.249.219 1299 s-b5-link.telia.net TELIANET Telia Carrier, SE 21.888ms 7 - 62.115.36.166 1299 akamai-ic-310810-s-b5.c.telia.net TELIANET Telia Carrier, SE 22.332ms <- Sweden 8 - 23.216.52.2 21342 a23-216-52-2.deploy.static.akamaitechnologies.com AKAMAI-ASN2, US 22.111ms Can you double check location of this probe? Regards, Grzegorz -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 21739 bytes Desc: image001.jpg URL: From bortzmeyer at nic.fr Tue May 29 13:36:24 2018 From: bortzmeyer at nic.fr (Stephane Bortzmeyer) Date: Tue, 29 May 2018 13:36:24 +0200 Subject: [atlas] CLI In-Reply-To: References: Message-ID: <20180529113624.g5f5nmj35nduotob@nic.fr> On Wed, May 09, 2018 at 12:35:04PM +0430, Milad Afshari wrote a message of 26 lines which said: > It's more than a month that I have a lot of issues with running > measurements through CLI here from IRAN, the measurements starts > correctly but the results will not be displayed. It may be of course some interference from an evil HTTPS interceptor. Could you: 1) Give the measurement ID of a few (public) measurements, so people can check the results? 2) Copy/paste the command-line used (we don't even know whch tool did you use to start the measurements)? From afshar.milad89 at gmail.com Wed May 30 08:43:11 2018 From: afshar.milad89 at gmail.com (Milad Afshari) Date: Wed, 30 May 2018 11:13:11 +0430 Subject: [atlas] CLI In-Reply-To: <20180529113624.g5f5nmj35nduotob@nic.fr> References: <20180529113624.g5f5nmj35nduotob@nic.fr> Message-ID: Hi, The output of CLI is attached, As you see, the measurement has been run correctly and we can see the result through the web interface: https://atlas.ripe.net/measurements/13595420/ Regards Milad On Tue, May 29, 2018 at 4:06 PM, Stephane Bortzmeyer wrote: > On Wed, May 09, 2018 at 12:35:04PM +0430, > Milad Afshari wrote > a message of 26 lines which said: > > > It's more than a month that I have a lot of issues with running > > measurements through CLI here from IRAN, the measurements starts > > correctly but the results will not be displayed. > > It may be of course some interference from an evil HTTPS > interceptor. Could you: > > 1) Give the measurement ID of a few (public) measurements, so people > can check the results? > > 2) Copy/paste the command-line used (we don't even know whch tool did > you use to start the measurements)? > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- milad at milad:~$ ripe-atlas measure ping --from-probe 33717 --target 9.9.9.9 Looking good! Your measurement was created and details about it can be found here: https://atlas.ripe.net/measurements/13595420/ Connecting to stream... Disconnecting from stream You can find details about this measurement here: https://atlas.ripe.net/measurements/13595420/ Exception in thread Thread-1 (most likely raised during interpreter shutdown): Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner File "/usr/lib/python2.7/dist-packages/socketIO_client/heartbeats.py", line 27, in run File "/usr/lib/python2.7/dist-packages/socketIO_client/__init__.py", line 192, in _ping File "/usr/lib/python2.7/dist-packages/socketIO_client/transports.py", line 159, in send_packet : 'NoneType' object is not callable Unhandled exception in thread started by sys.excepthook is missing lost sys.stderr milad at milad:~$ From bortzmeyer at nic.fr Wed May 30 08:52:48 2018 From: bortzmeyer at nic.fr (Stephane Bortzmeyer) Date: Wed, 30 May 2018 08:52:48 +0200 Subject: [atlas] CLI In-Reply-To: References: <20180529113624.g5f5nmj35nduotob@nic.fr> Message-ID: <20180530065248.n3rpy5utft25xema@sources.org> On Wed, May 30, 2018 at 11:13:11AM +0430, Milad Afshari wrote a message of 97 lines which said: > Exception in thread Thread-1 (most likely raised during interpreter shutdown): > Traceback (most recent call last): > File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner > File "/usr/lib/python2.7/dist-packages/socketIO_client/heartbeats.py", line 27, in run > File "/usr/lib/python2.7/dist-packages/socketIO_client/__init__.py", line 192, in _ping > File "/usr/lib/python2.7/dist-packages/socketIO_client/transports.py", line 159, in send_packet > : 'NoneType' object is not callable > Unhandled exception in thread started by > sys.excepthook is missing > lost sys.stderr It seems a bug in the tool, to me, may be triggered by some MiTM TLS interceptor. In the case it is specific to the streaming interface, you may try a tool which does not use this interface (weaknesses can be strengths :-) : % blaeu-reach --probes 33717 9.9.9.9 1 probes reported Test #13596250 done at 2018-05-30T06:46:37Z Tests: 3 successful tests (100.0 %), 0 errors (0.0 %), 0 timeouts (0.0 %), average RTT: 130 ms Or with your measurement (which indeed worked): % blaeu-reach --measurement-ID 13595420 --probes 33717 9.9.9.9 Warning: --probes ignored since we use probes from a previous measurement Test #13595420 done at 2018-05-30T06:29:04Z Tests: 3 successful tests (100.0 %), 0 errors (0.0 %), 0 timeouts (0.0 %), average RTT: 130 ms If you have time to test, tell me if it works better.