- ripe-atlas - mailman.ripe.net

Running a probe behind a NAT66
by Roman Mamedov 13 Jun '18

13 Jun '18

Hello, I am trying to run a probe (#73) behind an IPv6 NAT. The probe gets an IP in a non-standard prefix 66:113::/64, which is then NATed to a single GUA IPv6. This used to work fine for a few months, but then in April-2018 problems started: the probe would connect to Atlas for 5-10 minutes, then disconnect for about 20 minutes, then connect again; this alternates over and over again. However -- if IPv6 RAs are enabled some time after the probe is powered-on (i.e. the controller connection already got established over IPv4), things seem to go on fine, i.e. the controller is connected over IPv4 for days, but various measurements are performed on IPv6 too. So it seems that only the controller connection is the problem. I fully expect that you didn't account for such a setup in the controller infrastructure or possibly various "local IP is valid" checks and whatnot, but why this used to work fine before? Has there been any change on your side in April that would break this kind of setup? -- With respect, Roman

5 8

Probe #32536 with incorrect location
by Ponikierski, Grzegorz 11 Jun '18

11 Jun '18

Hi! Probe #32536 according to Atlas is located in India but its description, ASN and traceroutes suggest that in fact it's located Slovakia. Please verify. Regards, Grzegorz

2 1

New on RIPE Labs: Sketching Connectivity Between Users
by Mirjam Kuehne 04 Jun '18

04 Jun '18

Dear colleagues, We've been looking at user-to-user connections, based on RIPE Atlas measurements and ISP market share estimates provided by the APNIC. Please see some interesting graphs and a more detailed description in this new article on RIPE Labs: https://labs.ripe.net/Members/emileaben/sketching-connectivity-between-users Kind regards, Mirjam Kühne RIPE NCC

2 3

CLI
by Milad Afshari 03 Jun '18

03 Jun '18

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

2 5

Probe name rules
by Daniel AJ Sokolov 03 Jun '18

03 Jun '18

Hello, I would like to suggest a naming convention for probes that excludes names referring to features or networks which are not present/supported. For example, I see a probe that contains in its name a large network, although the probe is actually connected to competitor networks. (I assume the probe's host changed their ISP and forgot to update the probe's name.) Such naming is misleading for Atlas users, but also opens a can of worms in relation to trade mark law. Similarly, a prove with "IPv6" in its name that doesn't support IPv6 could be confusing. BR Daniel AJ

2 1

Probe #595 invalid location
by Ponikierski, Grzegorz 27 May '18

27 May '18

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@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

1 0

Aggregator for TXT record
by Ponikierski, Grzegorz 24 May '18

24 May '18

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

1 0

New on RIPE Labs: Update on the RIPE Atlas Anchor VM pilot
by Alun Davies 14 May '18

14 May '18

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-pil… <https://labs.ripe.net/Members/kistel/update-on-the-ripe-atlas-anchor-vm-pil…> Best regards, Alun Davies RIPE NCC

1 0

Probe #33346 invalid location
by Ponikierski, Grzegorz 11 May '18

11 May '18

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

1 0

Atlas #50012 handed over..
by Geert Jan de Groot 09 May '18

09 May '18

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

2 1