May 2013 - ripe-atlas - mailman.ripe.net

Atlas F.ROOT ping
by Peter Gervai 09 Jan '14

09 Jan '14

Hello, Atlas helped me today first to see a hard-to-detect bug: F-root anycast algo works fine for v4 but fails miserably for v6, as instead of AMSterdam it sends all traffic to some remote island in the pacific. ;-) Seems to be the reverse true for M-root: ipv4 sends me off to nowhere land while v6 is great. A-root follows the F-suit. (C-root is not a good avertisement valie for Cogent, with v4 only address and considerable ongoing pkt loss.) Thanks! Peter

4 5

Troubles with registering the probe if assigned by Ambassador
by Alex Saroyan 29 May '13

29 May '13

Hi, I'm not sure, but seems that if the probe was initially assigned to ambassador then ambassador assigned to the host the probe in not appearing in host's account. Example 1 Probe F81A674D7482 was assigned to levon.avagyan(a)gmail.com by me ambassador alex.saroyan(a)gmail.com. In Ambassador page I see this probe as "Online, not hosted", and host does not see the probe on his account at all. Example 2 Probe A0F3C1C44063 was assigned to surenispiryan(a)gmail.com again by me ambassador alex.saroyan(a)gmail.com. He didn't connect the probe yet to network. In Ambassador page I see the probe status "Applied" and host does not see the probe in his account under "my probes" at all. Regards. /Alex

6 15

[ripe.net #1087678] problem with connection to network
by Alastair Strachan 28 May '13

28 May '13

Hello, Thanks for your email and update. I can confirm the probe is back online and reporting without issue. If you do have any further questions, please do not hesitate to contact us. Thank you for taking the time to host an Atlas probe. Kind Regards, Alastair Strachan RIPE Atlas Team ============================================================ Take the RIPE NCC Survey 2013 and tell the RIPE NCC what you think! Participants will be entered into prize draws to win an iPad. https://www.ripe.net/survey2013 ============================================================= On Mon May 27 18:33:28 2013, sdimonius(a)gmail.com wrote: > Hello and thanks for reply! > > Now probe is work. I was read all FaQ, but nothing help. > > The network is efficient for 100%. > > Experiments help me. First i remove external memory, boot from built > in, > and then attach usb flash, after 10 mins probe connect to network. > > 27.05.2013 16:23, Alastair Strachan пишет: > > Hello, > > > > Thanks for your email and update. > > > > It would appear there is something on the network that is blocking > the probe from connecting outside the network. > > > > If a probe has been assigned a Static IP and for some reason that is > not reachable, the probe will automatically fall back to DHCP. As this > is not happening, there must be something blocking it. > > > > The probe is currently configured via DHCP, again, this is not > allowing the probe to connect outside your network. > > > > Please ensure port 443 is fully open and all firewall/security rules > have been adjusted accordingly. Please take a look at our FAQ for more > troubleshooting steps: https://atlas.ripe.net/about/faq/ > > > > If you do have any further questions, please do not hesitate to > contact us. > > > > Thank you for taking the time to host an Atlas probe. > > > > Kind Regards, > > > > Alastair Strachan > > > > RIPE Atlas Team > > > > ============================================================ Take > the RIPE NCC Survey 2013 and tell the RIPE NCC what you think! > > Participants will be entered into prize draws to win an iPad. > > https://www.ripe.net/survey2013 > ============================================================= > > > > > > > > > > > > On Sun May 26 16:01:00 2013, sdimonius(a)gmail.com wrote: > >> Hello! > >> > >> I have problem with my probe v3 (ID 11003, FW 4520). > >> > >> First i used DHCP (at Home, for tests), all was worked fine. > >> > >> Then i reconfigure my probe to Static IP (by manual). Static IP > >> necessary to install my probe 24/7/365 in server room. We don't use > DHCP. > >> > >> But probe can't connect to network... > >> > >> I brought probe to home, connect to DHCP network. Router give IP to > >> probe. But probe still disconnected on atlas.ripe.net at least 3 > hours... > >> > >> LEDs: > >> 1 - ON > >> 2 - OFF > >> 3 - Slow blink > >> 4 - ON > >> 5 - ON > >> > >> Power reset - no result. Try to change Router cfg (ip, dns, mask) - > no > >> result. Probe still disconnected. > >> > >> I read, that if set static IP - probe try to test setting. > >> > >> By LEDs - "Network test"? But 3+ hours "Network test"? > >> > >> DHCP work correctly (Router - Zyxell Keenetic, last firmware), PC > work > >> without problems on full autoconfiguration (IP, mask, gateway, DNS) > >> > >> Can you help me? > >> > >> P.S. Sorry for my english, i'm from Ukraine > >> > >> > >> > > > > > >

5 4

RIPE Atlas slides for AFNOG
by Randy Bush 28 May '13

28 May '13

the atlas folk have been kind enough to hand me a batch of probes to hand out key engineers at the afnog workshops in lusaka. i want to give maybe a half hour talk on the probes, something that starts from the beginning, o what is ripe atlas, o how do i install a probe, o how do i register it, o how do i interpret the web pages, o etc. vesna was kind enough to give me her dublin preso, but that assumes a *lot* of background. i need ripe atlas 101. thanks. randy

2 3

Re: [atlas] [ripe.net #1087678] problem with connection to network
by Дмитрий Сергеевич 27 May '13

27 May '13

Hello and thanks for reply! Now probe is work. I was read all FaQ, but nothing help. The network is efficient for 100%. Experiments help me. First i remove external memory, boot from built in, and then attach usb flash, after 10 mins probe connect to network. 27.05.2013 16:23, Alastair Strachan пишет: > Hello, > > Thanks for your email and update. > > It would appear there is something on the network that is blocking the probe from connecting outside the network. > > If a probe has been assigned a Static IP and for some reason that is not reachable, the probe will automatically fall back to DHCP. As this is not happening, there must be something blocking it. > > The probe is currently configured via DHCP, again, this is not allowing the probe to connect outside your network. > > Please ensure port 443 is fully open and all firewall/security rules have been adjusted accordingly. Please take a look at our FAQ for more troubleshooting steps: https://atlas.ripe.net/about/faq/ > > If you do have any further questions, please do not hesitate to contact us. > > Thank you for taking the time to host an Atlas probe. > > Kind Regards, > > Alastair Strachan > > RIPE Atlas Team > > ============================================================ Take the RIPE NCC Survey 2013 and tell the RIPE NCC what you think! > Participants will be entered into prize draws to win an iPad. > https://www.ripe.net/survey2013 ============================================================= > > > > > > On Sun May 26 16:01:00 2013, sdimonius(a)gmail.com wrote: >> Hello! >> >> I have problem with my probe v3 (ID 11003, FW 4520). >> >> First i used DHCP (at Home, for tests), all was worked fine. >> >> Then i reconfigure my probe to Static IP (by manual). Static IP >> necessary to install my probe 24/7/365 in server room. We don't use DHCP. >> >> But probe can't connect to network... >> >> I brought probe to home, connect to DHCP network. Router give IP to >> probe. But probe still disconnected on atlas.ripe.net at least 3 hours... >> >> LEDs: >> 1 - ON >> 2 - OFF >> 3 - Slow blink >> 4 - ON >> 5 - ON >> >> Power reset - no result. Try to change Router cfg (ip, dns, mask) - no >> result. Probe still disconnected. >> >> I read, that if set static IP - probe try to test setting. >> >> By LEDs - "Network test"? But 3+ hours "Network test"? >> >> DHCP work correctly (Router - Zyxell Keenetic, last firmware), PC work >> without problems on full autoconfiguration (IP, mask, gateway, DNS) >> >> Can you help me? >> >> P.S. Sorry for my english, i'm from Ukraine >> >> >> > > -- С уважением, Дмитрий Личный блог: www.weblance.com.ua Хобби: www.mukachevo.net Работа: www.dovgolit.com

1 0

problem with connection to network
by Дмитрий Сергеевич 27 May '13

27 May '13

Hello! I have problem with my probe v3 (ID 11003, FW 4520). First i used DHCP (at Home, for tests), all was worked fine. Then i reconfigure my probe to Static IP (by manual). Static IP necessary to install my probe 24/7/365 in server room. We don't use DHCP. But probe can't connect to network... I brought probe to home, connect to DHCP network. Router give IP to probe. But probe still disconnected on atlas.ripe.net at least 3 hours... LEDs: 1 - ON 2 - OFF 3 - Slow blink 4 - ON 5 - ON Power reset - no result. Try to change Router cfg (ip, dns, mask) - no result. Probe still disconnected. I read, that if set static IP - probe try to test setting. By LEDs - "Network test"? But 3+ hours "Network test"? DHCP work correctly (Router - Zyxell Keenetic, last firmware), PC work without problems on full autoconfiguration (IP, mask, gateway, DNS) Can you help me? P.S. Sorry for my english, i'm from Ukraine -- С уважением, Дмитрий Личный блог: www.weblance.com.ua Хобби: www.mukachevo.net Работа: www.dovgolit.com

3 2

Bug when creating DNS6 with udp_reply_bytes via API
by Willem Toorop 24 May '13

24 May '13

Hi RIPE Atlas developers, I found a bug in the DNS API. When creating a DNS measurements via the API that have udp_reply_bytes property set, they never leave the "Scheduled" state and eventually fail. When I query the status of the measurements I notice that they have the udp_payload_size property set to true in stead of the value given with udp_reply_bytes. This is different from measurements created via the interface, where udp_payload_size reflects udp_reply_bytes. Also, it appears I can only origin 80 probes (by probe id), whilst in the interface I can origin from 500 probes. Is that correct? Would it be possible to (temporarily) increase my limit to 1050 probes? Best regards, -- Willem

2 2

Cannot archive failed measurements
by Willem Toorop 24 May '13

24 May '13

Hi, Here is another bug report. I cannot archive/delete measurements that have the "Failed" status. Regards, -- Willem

1 0

reset IP configuration
by "Аптека 'Довголіт' (ТОВ 'К ЕШ, ЛТД')" 24 May '13

24 May '13

Hello! I have RIPE Atlas probe v3 (TP-Link). First i used DHCP configuration, for test at home. But then i was configured my Probe to static IP. Setting will saved with error, and now probe cannot connect to worldwide network. How i can manual reset my Probe to factory/default dhcp settings? -- З повагою, Дмитро Староста ТОВ "КЕШ,ЛТД" www.dovgolit.com <http://dovgolit.com> Увага! Інформація у даному листі є конфіденційною!

1 0

Probe doesn't seem to automatically recover from IPv6 connectivity failure
by Sulev-Madis Silber 24 May '13

24 May '13

Hello. Probe (v2) doesn't seem to recover from all network failures automatically. It currently connects using IPv4 and reports IPv6 tests as "can't send". I can't ping probe on IPv6 and it seems like it doesn't talk IPv6 at all on that VLAN, although router sends RA's every minute. In web interface it says that it has IPv6 address (all other things under IPv6 are "Undetermined/Unknown") but it doesn't actually participate in network at all. Only router talks IPv6 in that network, according to tcpdump. I think not recovering from IPv6 failures is a bug. Somehow, it still recovers from IPv4 failures. Problem appeared after I had it physically disconnected from Ethernet for some hours. Before that, probe also didn't have connection to internet for a day. I wish I would not need to pull the power every time this happens. Although it's rare occasion that anything is down here. Thanks.

8 22