- ripe-atlas - mailman.ripe.net

Wrong uptime information in monthly report
by Rene Bartsch 01 Oct '14

01 Oct '14

Hi, I got the following report of a drone: -------------------------------------------------------------------------------------------------------------- This is your monthly availability report for probe 3146 (T-Online Call & Surf Comfort IP Speed 50/10 MBit/s ). Calculation interval : 2014-09-01 00:00:00 - 2014-10-01 00:00:00 Total Connected Time : 15d 16:46 Total Disconnected Time : 14d 07:13 Total Availability : 52.33% +---------------------+---------------------+------------+--------------+ | Connected (UTC) | Disconnected (UTC) | Connected | Disconnected | |---------------------+---------------------+------------+--------------+ | 2014-08-14 11:37:26 | 2014-09-02 02:22:27 | 1d 02:22 | 0d 00:00 | | 2014-09-02 02:36:21 | 2014-09-04 23:40:28 | 2d 21:04 | 0d 00:13 | | 2014-09-05 00:03:58 | 2014-09-16 17:23:55 | 11d 17:19 | 0d 00:23 | +---------------------+---------------------+------------+--------------+ ---------------------------------------------------------------------------------------------------------------- https://atlas.ripe.net/probes/3146/#!tab-network shows an uptime of 99.83%. Please fix this! -- Best regards, Renne

2 1

Fwd: Final Call For Presentations RIPE 69, deadline 1 October 2014
by Vesna Manojlovic 25 Sep '14

25 Sep '14

Dear colleagues, RIPE69 is approaching. If you would like to present to the whole plenary on RIPE Atlas, the deadline is soon. If you prefer to talk on MAT-WG, please approach the chairs directly: mat-wg-chairs(a)ripe.net Regards, Vesna -------- Original Message -------- Date: Wed, 24 Sep 2014 23:36:36 +0200 From: Benno Overeinder <benno(a)NLnetLabs.nl> Dear colleagues, Following the past submission deadline, there is a Draft RIPE Plenary programme published at: https://ripe69.ripe.net/programme/meeting-plan/plenary/ There are still slots remaining for the final RIPE 69 programme and RIPE Programme Committee will accept new proposals until 1 October 2014. This is a last call deadline if you wish to submit a proposal. Kind regards, Benno Overeinder for RIPE programme committee On 27/08/14 13:33, Benno Overeinder wrote: > Dear colleagues, > > Please find the CFP for RIPE 69 in London below. > > The deadline for submissions is 31 August 2014. > > Please also note that speakers do not receive any extra reduction or > funding towards the meeting fee at the RIPE Meetings. > > Kind regards, > > RIPE PC > http://www.ripe.net/ripe/meetings/ripe-meetings/pc > > > --------------------- > > Call for Presentations > > A RIPE Meeting is an open event where Internet Service Providers, > network operators and other interested parties get together. Although > the meeting is mostly technical, it is also a chance for people to meet > and network with others in their field. > > RIPE 69 will take place from 3-7 November 2014 in London, UK. > > The RIPE Programme Committee (PC) is now seeking content proposals from > the RIPE community for the plenary session presentations, BoFs (Birds of > a Feather sessions), panels, workshops, tutorials and lightning talks at > RIPE 69. The PC is looking for presentations covering topics of network > engineering and operations, including but not limited to: > > - IPv6 deployment > - Managing IPv4 scarcity in operations > - Commercial transactions of IPv4 addresses > - Data centre technologies > - Network and DNS operations > - Internet governance and regulatory practices > - Network and routing security > - Content delivery > - Internet peering and mobile data exchange > > Submissions > > RIPE Meeting attendees are quite sensitive to keeping presentations > non-commercial, and product marketing talks are strongly discouraged. > Repeated audience feedback shows that the most successful talks focus on > operational experience, research results, or case studies. For example, > presenters wishing to describe a commercial solution should focus on > the underlying technology and not attempt a product demonstration. > > The RIPE PC accepts proposals for different presentation formats, > including plenary session presentations, tutorials, workshops, BoFs > (Birds of a Feather sessions) and lightning talks. See the full > descriptions of these formats at > https://ripe69.ripe.net/submit-topic/presentation-formats/ > > Presenters who are proposing a panel or BoF are encouraged to include > speakers from several (perhaps even competing) companies and/or a > neutral facilitator. > > In addition to presentations selected in advance for the plenary, the > RIPE PC also offers several time slots for "lightning talks", which are > selected immediately before or during the conference. > > The following general requirements apply: > > - Proposals for plenary session presentations, BoFs, panels, workshops > and tutorials must be submitted for full consideration no later than > 31 August 2014, using the meeting submission system at > https://ripe69.ripe.net/submit-topic/guidelines/. Proposals > submitted after this date will be considered on a space-available > basis. > > - Lightning talks should also be submitted using the meeting submission > system (https://ripe69.ripe.net/submit-topic/submission-form/) and > can be submitted just days before the RIPE Meeting starts or even > during the meeting week. The allocation of lightning talk slots will > be announced in short notice – in some cases on the same day but > often one day prior to the relevant session. > > - Presenters should indicate how much time they will require. See more > information on time slot allocations per presentation format at > https://ripe69.ripe.net/submit-topic/presentation-formats/. > > - Proposals for talks will only be considered by the PC if they contain > at least draft presentation slides (slides may be updated later on). > For panels, proposals must contain a clear description, as well as > the names of invited panellists, presenters and moderators. > > - Due to potential technical issues, it is expected that most, if not > all, presenters/panellists will be physically present at the RIPE > Meeting. > > If you have any questions or requests concerning content submissions, > please email pc [at] ripe [dot] net. > > --------------------- > > -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

UDM limit?
by Paul Vlaar 18 Sep '14

18 Sep '14

Hi, I'm trying to add a UDM for one of our nameservers, however it appears others are already doing "too many measurements" for this server, as this is the message I get when I try to add my UDM: "10 UDMs are already measuring 199.19.54.1/2001:500:c::1. Cannot add 2 more" AFAIK I have no UDMs running for this server, so the mentioned UDMs are beyond my control to retract. Is it possible to find out who is running these UDMs so I can ask them to stop, or alter them in such a way that they match what I need in this UDM? It seems a bit odd to me that I can't do custom measurements on our server because others are already doing some. ~paul -- Paul Vlaar DNS Infrastructure Group Afilias e-mail: pvlaar(a)afilias.info phone: +1-416-673-4078 mobile DE: +49-1578-5742-695 mobile NL: +31-6-506-306-35 mobile USA: +1-602-410-4148

4 6

XS4ALL (NL) has joined RIPE Atlas anchors
by Michela Galante 16 Sep '14

16 Sep '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called nl-ams-as3265 and it is hosted by XS4ALL in Amsterdam, Nederland. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

Seeking community feedback on draft RIPE Atlas Service Terms and Conditions
by Vesna Manojlovic 15 Sep '14

15 Sep '14

Dear colleagues, We have published a draft proposal for RIPE Atlas Service Terms and Conditions and are asking for community feedback on this, along with our proposed implementation plan. Please find more information on the MAT Working Group Mailing List, where we kindly ask you to direct any feedback you may have: https://www.ripe.net/ripe/mail/archives/mat-wg/2014-September/000489.html Regards, Vesna Manojlovic Senior Community Builder Measurements Community Building RIPE NCC

1 0

New on RIPE Labs: RIPE Atlas Measurements with Tagged Probes coming soon
by Mirjam Kuehne 15 Sep '14

15 Sep '14

Dear colleagues, Please find a new article on RIPE Labs: RIPE Atlas: Measurements with Tagged Probes Coming Soon https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-measurements… If you have any comments or questions, please let us know. Kind regards, Mirjam Kuehne RIPE NCC

3 2

SCT Schiele (DE) has joined RIPE Atlas anchors
by Michela Galante 15 Sep '14

15 Sep '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called de-ett-as202040 and it is hosted by SCT Schiele GmbH in Ettlingen, Germany. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

'limit' filed in the probe API metadata
by Eravuchira, Steffie Jacob 12 Sep '14

12 Sep '14

Hello, In the REST API for RIPE Atlas probes [1], there is a metadata "limit" to set the number of items displayed in the API [2]. Previously I have used the "limit" field to get the details of all the registered probes (by specifying limit as the value in the field "total_count" in metadata) at once using this API. Now the API works well with values of "limit" up to 100. But for any value greater than 100, the limit is automatically set to 100. Could anyone help me understand why this could happen and how I can access the details of all the RIPE Atlas registered probes? [1] https://atlas.ripe.net/api/v1/probe [2] https://atlas.ripe.net/api/v1/probe/?limit=n Thank you in advance for the help. Regards, Steffie _________________________________________________________ Steffie Jacob Eravuchira Research I, Room 91 Computer Networks and Distributed Systems (CNDS) Lab School of Engineering and Sciences Jacobs University Bremen, Germany

2 1

DigitalOcean (SG) has joined RIPE Atlas anchors
by Michela Galante 10 Sep '14

10 Sep '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called sg-sin-as133165 and it is hosted by DigitalOcean in Singapore City, Singapore. Congratulations to DigitalOcean for their third anchor online! Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

The Beta Version of the New DNSMON is Now Available
by Vesna Manojlovic 08 Sep '14

08 Sep '14

Dear colleagues, The DNS Monitoring Service (DNSMON) has been providing a comprehensive, objective and up-to-date overview of the quality of various global and regional DNS operators' services since 2003. We are in the process of integrating DNSMON within RIPE Atlas and the beta version of the new DNSMON is now publicly available: https://atlas.ripe.net/dnsmon We have also published a RIPE Labs article detailing what’s changed in the new DNSMON: https://labs.ripe.net/Members/fatemah_mafi/an-updated-dns-monitoring-service We invite you all to try the new service and provide your feedback. We’re confident that the new DNSMON will continue to meet your needs and hope that you'll be happy with the new features. Please send your comments and questions to the DNS Working Group Mailing List at dns-wg(a)ripe.net. Kind regards, Vesna Manojlovic Measurements Community Building RIPE NCC

7 10

S-IT Informationstechnologie Betreiber (DE) has joined RIPE Atlas anchors
by Michela Galante 25 Aug '14

25 Aug '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called de-cal-as39702 and it is hosted by S-IT Informationstechnologie Betreiber in Calw, Germany. With this anchor we reached a total of 70 online. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

2 1

DigitalOcean has joined RIPE Atlas anchors
by Michela Galante 19 Aug '14

19 Aug '14

Dear RIPE Atlas users, We're happy to announce that two RIPE Atlas anchors have joined the network and are now available as targets for probe hosts conducting their own user-defined measurements. The new anchors are uk-slo-as202109 located in Slough, United Kingdom and us-sfo-as14061 located in San Francisco, United States, both hosted by DigitalOcean. Congratulations to DigitalOcean for bringing their two anchors online! Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards these anchors from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

Probe on a /31 or /32 IPv4 network
by Baptiste Jonglez 18 Aug '14

18 Aug '14

Hi, We would like to deploy our Atlas probe on a separate L2 network, but without having to spend 4 IPv4 addresses (i.e. a /30 network). Using a /31 would be nice, but the web UI doesn't allow it as static IPv4 configuration ("The Gateway address should be different from the ending network address"). Would it be possible to allow /31 in the web UI? I believe the probes themselves support it. Even nicer would be support for /32 networks, even though it is perhaps less usual. This can easily be done with iproute2 on Linux, assuming the probe is 192.0.2.48/32 and its gateway is 192.0.2.1: ip addr add 192.0.2.48/32 dev eth0 ip route add 192.0.2.1/32 dev eth0 ip route add default via 192.0.2.1 or even shorter: ip addr add 192.0.2.48/32 dev eth0 ip route add default via 192.0.2.1 onlink dev eth0 Using a gateway that is not on the same subnet doesn't sound very nice, but again, the goal is to avoid wasting precious IPv4 space. Thanks, Baptiste

4 4

measurment with endtime - faulty date
by gboonie 18 Aug '14

18 Aug '14

Hi, I noticed the last few days that when I create a new measurement with a end date and time next week that I get a failure message on the next screen. --- Your measurement will start ASAP. Your measurement will end at: Y-8-16 0:i UTC. and in the next screen: Enter a valid date/time. --- What I selected was: 2014-08-16 00:45 Multiple tests on 2 different Win7 PCs give the same result. Regards, Dave

2 4

atlas on a public subnet
by James Sink 14 Aug '14

14 Aug '14

Hello all, I just received my atlas probe and am about to deploy it. However I have a question about the subnet I am going to place it it on. Is it safe to put it on an unfiltered public ip? If not what ACL should I place on the interface? Thanks --- James Sink Network Engineer P: 800-477-1477 x: 813

2 2

Current crediting issues
by Robert Kisteleki 14 Aug '14

14 Aug '14

Dear All, We have reports of the Atlas billing process doing strange things at the moment. We're investigating these and will get back to you with more information. Regards, Robert

1 2

Upcoming "Measurements Tools" Workshop for LIRs: 19 September, in Amsterdam
by Vesna Manojlovic 12 Aug '14

12 Aug '14

Dear colleagues, Training Services, RIPEstat/RIPE Atlas developers and me will be giving a "Measurements Tools" Workshop on 19 September, in Amsterdam. Registration is possible for members of RIPE NCC via LIR Portal: https://lirportal.ripe.net/training/courses Below is the preliminary information about the workshop. If you know people who would be interested, please forward this to them. Regards, Vesna Target audience: LIRs (RIPE NCC members), network operators Goal of the Measurements Tools Workshop is to convey the benefits that the network operators can gain from using RIPE NCC tools, such as RIPEstat and RIPE Atlas - through practical exercises and hands-on approach. Prerequisites: RIPE NCC Access account; general knowledge about IP networking, DNS and BGP, as well as of one/any programming language. Workshop overview: RIPEstat topics: Basic: 1) finding the information about IP resources 2) comparing resources 3) finding anti-abuse information Advanced: embedding the widget using BGplay using command-line interface analysing events (examples of uses cases) personalizing RIPEstat RIPE Atlas topics: Basic: 1) creating a measurement 2) looking-up measurements data and analyzing the data 3) monitoring: setting-up status checks Advanced: member-specific services use cases by other people analysing information in Internet Traffic Maps take part in the community: share your code, distribute the probes, install anchors…

1 0

Probe suddenly lost IPv6 connectivity
by Ondřej Caletka 11 Aug '14

11 Aug '14

Hi, strange thing happened today. My probe v2 #3467 suddenly lost IPv6 connectivity and reconnected to the control server using IPv4. The probe does not even respond to ping6 ff02::1%eth1 sent from the router. I wonder what could cause such behavior. I will try to reboot the probe once I'll reach it. -- Ondřej Caletka

2 2

Probe 2092 shown as offline for a month
by David Precious 06 Aug '14

06 Aug '14

Hi there, My v1 probe #2092 has been showing as offline for a month, despite being powered up and pinging. Yesterday I power-cycled it, and it came back up and answers pings again, but the Atlas control panel still shows it as disconnected. Is there any troubleshooting I can do to get more information? I've verified that I can ping it from my internal network. There's no egress filtering which would be blocking it from talking outbound. I've just had my router log new outbound connections then power-cycled the probe again. I saw it successfully obtain an IP via DHCP (10:13:21), then 31 minutes later, connected to oneill.atlas.ripe.net (193.0.19.12) on port 443 (10:44:50) (UK times). I have verified that another box on the same network can connect to that IP & port: [davidp@columbia:~]$ telnet 193.0.19.12 443 Trying 193.0.19.12... Connected to 193.0.19.12. Escape character is '^]'. SSH-2.0-OpenSSH_5.3 Anything else I can do to provide more useful info? Cheers Dave P -- David Precious ("bigpresh") <davidp(a)preshweb.co.uk> http://www.preshweb.co.uk/ www.preshweb.co.uk/twitter www.preshweb.co.uk/linkedin www.preshweb.co.uk/facebook www.preshweb.co.uk/cpan www.preshweb.co.uk/github

2 4

Re: [atlas] Measurements can't be stopped
by Max Grobecker 02 Aug '14

02 Aug '14

Hi, YEAH! That did the trick ;-) I've never right-clicked on these items before... Thank you! Greetings from Wuppertal, Germany Max Grobecker Am 02.08.2014 um 11:52 schrieb Iñigo Ortiz de Urbina: > Hi Max, > > On Sat, Aug 2, 2014 at 11:43 AM, Max Grobecker > <max+ratlml(a)grobecker.info> wrote: >> Hi, >> >> I tried to stop a measurement, which was defined as "end never". >> >> In order to stop the measurement I opened it, clicked "Settings" and >> unchecked "End never". >> But regardless what I choose as "End at" time, it always gets refused with >> the hint that I need to enter a valid date. >> For example, [ 2014-08-03 ] [ 00:00 ] is refused as invalid date/time. >> >> Is there any option to stop this measurements? > > You can stop measurements by right-clicking on them, and then > selecting Stop. The options that you should see after right-clicking > are: Archive, Settings and Stop. > > HTH, > >> Thank you! >> >> -- >> Greetings from Wuppertal, Germany >> Max Grobecker >> > > >

1 0

Measurements can't be stopped
by Max Grobecker 02 Aug '14

02 Aug '14

Hi, I tried to stop a measurement, which was defined as "end never". In order to stop the measurement I opened it, clicked "Settings" and unchecked "End never". But regardless what I choose as "End at" time, it always gets refused with the hint that I need to enter a valid date. For example, [ 2014-08-03 ] [ 00:00 ] is refused as invalid date/time. Is there any option to stop this measurements? Thank you! -- Greetings from Wuppertal, Germany Max Grobecker

1 0

Static IPv6 problem
by Jonas Byström 01 Aug '14

01 Aug '14

Hi, I have a problem when i try to set a Static IPv6 adress i get on my probe. I get: No more than 3 static DNS values may be used at any given time for either IPv4 or IPv6. I have set: 2001:4860:4860::8888 and 2001:4860:4860::8844 as DNS. What should i do to get this to work? Regards Jonas Byström

3 2

Re: [atlas] [ripe.net #1133019] Re: Your RIPE Atlas Probe (ID: 16784) is not connected to our network
by Daniel Suchy 01 Aug '14

01 Aug '14

It's surprising, that you can't manage probe remotelly when it isn't "connected" (even you can directly reach it on L3). Technically, probe runs on Linux, so you can have SSH daemon with restricted IP access running here (listenning daemon has minimal performance overhead) - by current "behavior" you simply loose any way to diagnose problem - and dependence of established tunnel is another layer, which can fail... As stated before - simple rebooting is just a *workaround* of any issue, not a solution (but it seems that's your basic recomendation). I think you should work on improvements on probe diagnostics in such cases - new hardware versions of probes seems to be more problematic compared to older probes, as I can see also on atlas mailing list. I remember, that I had to plug out/in USB flash as some step with probe before (also your recomended "solution"). Also on probe should run some kind of watchdog, which reboots probe in case of similar problem automatically - probably it doesn't run now... With regards, Daniel On 31.7.2014 17:31, Philip Homburg wrote: > Hi Daniel, > > On Tue Jul 29 19:29:20 2014, danny(a)danysek.cz wrote: >> What checks did you performed at your side before sending such email? >> You don't have any kind of "emenergency" probe management, like SSH >> shell access directly to the device? What do you see in *your* logs >> about affected probe before it was disconnected? > > The mail gets sent when the is not connected for some time. Nothing more. > > There are no open ports on the probes. The probe can only be controlled when it is connected. > > There is some evidence in the logs that there was already something wrong with the probe when it disconnected. Most likely there is something wrong with the filesystem on the USB flash drive, but that is hard to say. > > Philip >

6 6

Re: [atlas] Paris-traceroute variations
by FANOU Roderick 31 Jul '14

31 Jul '14

Hi all, Just a quick question. What is the real difference between a TCP paris-traceroutes and an UDP paris-traceroute ? How do the probes perform each of them? Thanks, Best regards, Roderick On 26.06.2014 13:13, Philip Homburg wrote: > Hi Juan, > > On 2014/06/19 16:59 , Juan Antonio Cordero Fuertes wrote: >> Not sure this is the right place to ask this... sorry if it is not. >> >> I'm trying to configure Paris-traceroute measurements, and it is not >> clear for me what is the meaning of the /paris/ parameter. In >> https://atlas.ripe.net/docs/udm/ it is said that it corresponds, for >> values from 1 to 16, to "the number of variations to be used for a Paris >> traceroute <http://www.paris-traceroute.net/>". What is this? Does it >> correspond to the number of initial probes to be used by >> paris-traceroute? I am unable to figure it out from the RIPE Atlas >> docs... any indication would be appreciated. > > Paris-traceroute tries to make sure that all packets of a traceroute > take the same route through a load balancer. This in contrast to > traditional traceroute where packets from different hops typically take > different routes when load balancers are involved. > > However, in the case of paris-traceroute it is still interesting to find > out if there are multiple routes or not. For this reason, the traceroute > measurement creates different variations that may take a different route. > > Each interval, it will try one variation. So if you select 16 variations > then it will take 16 intervals before you get back to the first one. > > Philip

2 1

Re: [atlas] [ripe.net #1133019] Re: Your RIPE Atlas Probe is not connected to our network
by Daniel Suchy 29 Jul '14

29 Jul '14

There's no firewall / ACL, anything on the way, just pure L3 device. Probe worked properly, then disconnected without any logical reason with that notification received. Probe is pingable on both IPv4 and IPv6 from outside, proper (so there's no L3 issue on the way). Probe itself resets all incoming TCP connections from my IP address located in another ASN (probably due to firewall at the probe). On traffic mirrored from the probe I see ocasional NTP queries to some servers, so "something" on probe runs. Nothing else. You do not provide any access to probe for hosts to check anything directly, so I expect you can manage fully (as this is something running any kind of Linux?). As probe has public IPv4/IPv6 address, you should not have problem reach it. Unfortunatelly, probe is located on remote datacenter with limited physical access. Also this is not a solution of problem - with reboot you probably loose anything to diagnose causes of this problem. What checks did you performed at your side before sending such email? You don't have any kind of "emenergency" probe management, like SSH shell access directly to the device? What do you see in *your* logs about affected probe before it was disconnected? With regards, Daniel On 22.7.2014 11:17, Alastair Strachan wrote: > Hello Daniel, > > Thanks for your email. > > It would appear there is something on your network blocking the probe from connecting outside your network. Could I ask you to double check to ensure there is no security/firewall rule that has been updated or needs updating to allow the probe a clean connection outside your network. > > I would also recommend trying a complete power recycle on the probe. > > Thank you for taking the time to host a RIPE Atlas probe. > > If you have any further questions, please let me know > > Kind Regards, > > Alastair Strachan > > RIPE Atlas Team > > RIPE NCC Customer Satisfaction Survey > Tell us about your customer services experience by filling out the anonymous, three-question RIPE NCC customer satisfaction > > survey:https://www.ripe.net/contact/survey/satisfaction-cs/ > >> >> On 18.7.2014 05:40, RIPE Atlas wrote: >>> Dear RIPE Atlas probe host, >>> >>> Thank you for participating in RIPE Atlas! >>> >>> We have noticed that your probe is not connected to our infrastructure and has been >> disconnected since 2014-07-11 03:15 UTC. Could you please check >> whether everything is set up correctly on your side? If it is, and >> your probe is still reported as disconnected when you log in at >> https://atlas.ripe.net, please reply to this email so that we can >> follow up. >>> >>> You can review the instructions for setting up your probe at >> https://atlas.ripe.net/getting-started >>> >>> If you have any questions, please contact us at atlas(a)ripe.net >>> >>> Best regards, >>> >>> RIPE Atlas Team >>> >>> ********** >>> You are receiving this message because you applied for or were given >> a RIPE Atlas probe. We will only send messages when your probe >> becomes disconnected for an extended period of time. >>> >> > >

1 0