I guess due to the new controller infra, the built-ins measurements for:
ctr-ewr01.atlas.ripe.net
ctr-fnc01.atlas.ripe.net
ctr-sin02.atlas.ripe.net
are invalid now? They don’t produce data since October 1st it seems.
Will the new controllers be included as built-ins?
Regards,
Ernst J. Oud
this.
Regards,
Ernst J. Oud
-
To unsubscribe from this mailing list or change your subscription options,
please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the
email matching your subscription
will come in once the probe reconnects of course but by that time the value of the one-off is indeed gone...Cheers,JohanOn Tue, 17 Sept 2024 at 12:00, Ernst J. Oud <ernst...@gmail.com> wrote:Current Atlas status shows a delay of over 16 hours. I created a measurement and no data is returne
Current Atlas status shows a delay of over 16 hours. I created a measurement
and no data is returned.
It appears this is not a problem with only probes disconnecting…
Ernst J. Oud
-
To unsubscribe from this mailing list or change your subscription options,
please visit: https
, for
instance with a second opinion with probes from Globalping.
I appreciate the efforts to improve reliability of the Atlas infra.
Just now a third probe disconnected (1004467).
Regards,
Ernst J. Oud
> On 17 Sep 2024, at 09:43, Robert Kisteleki wrote:
>
> Hello,
>
> I c
Correction, not upto an hour but disconnected now already for several hours.
> On 16 Sep 2024, at 23:36, Ernst J. Oud wrote:
>
> Today my probes 60200 and 61071 experience several disconnects of upto an
> hour, both on controller ctr-dub-hw01.
>
> It appears this supposedly
Today my probes 60200 and 61071 experience several disconnects of upto an hour,
both on controller ctr-dub-hw01.
It appears this supposedly fixed disfunction has not been completely fixed.
Regards,
Ernst J. Oud-
To unsubscribe from this mailing list or change your subscription options
tool in the toolkit.
Thanks for the input.
Regards,
Ernst J. Oud
Met vriendelijke groet,
Ernst J. Oud
> On 27 Aug 2024, at 14:03, Stephane Bortzmeyer wrote:
>
> On Tue, Aug 27, 2024 at 12:42:18PM +0200,
> Ernst J. Oud wrote
> a message of 12 lines which said:
>
>> It
L.S.
It might be “cursing in the church” as we say in NL, but does anyone here have
experience with the Globalping monitoring tools?
Not as comprehensive as Atlas and a lot less probes but at first glance it has
some useful features.
Your thoughts?
Regards,
Ernst J. Oud
-
To
Cassiano,
There has been an incident with controllers, see:
https://status.ripe.net/incidents/cxp20fvs62mc
Regards,
Ernst
> On 25 Aug 2024, at 19:58, Cassiano Aquino via ripe-atlas
> wrote:
>
>
> Hi,
>
> After sitting there for a long time with an USB drive the probe returned to
> live,
> We're just letting you know that your probe (#60200 ) has re-established its
> link to our network and we are again receiving data from it.
Good! After over 3 days.
Connected to controller ctr-nue17. Not to ctr-dub anymore.
Ernst
-
To unsubscribe from this mailing list or change your
from RIPE here in the
mailing list. Perhaps everybody is on holiday?
I don’t know whether restarting a probe would help and I also don’t know what
“over the weekend” means. Today? Tomorrow? Monday? Next year?
Regards,
Ernst J. Oud
> On 24 Aug 2024, at 11:27, Daniel AJ Sokolov wrote:
>
before.
Ernst
> On 23 Aug 2024, at 17:56, Nick Hilliard (INEX) wrote:
>
> Ernst J. Oud wrote on 23/08/2024 16:54:
>> Do we need to take actions to have disconnected probes reconnect “over the
>> weekend”? Or is a reconnect in this case automatically?
> probes automatica
I asked before but this list appears to be not for support questions?
Try again…
Do we need to take actions to have disconnected probes reconnect “over the
weekend”? Or is a reconnect in this case automatically?
Regards,
Ernst J. Oud
-
To unsubscribe from this mailing list or change your
My only probe that is still down tries to connect to ctr-dub-hw01
Travelled to the location of this probe (60200) and restarted it. Did not solve
the issue.
So the problem appears to be there? Dublin?
Regards,
Ernst J. Oud
> On 22 Aug 2024, at 16:19, Robert Kisteleki wrote:
>
&g
helps let me know.
Regards,
Ernst J. Oud
-
To unsubscribe from this mailing list or change your subscription options,
please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the
email matching your
All my four probes that are disconnected are controlled by controller
ctr-dub-sw01 so the problem lies there.
Please give that controller a kick.
Regards,
Ernst J. Oud
> On 22 Aug 2024, at 10:34, Ernst J. Oud wrote:
>
> Hi,
>
> And just now probe 1004467 also has be
Hi,
And just now probe 1004467 also has been disconnected.
What is going on?
Regards,
Ernst J. Oud
-
To unsubscribe from this mailing list or change your subscription options,
please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/
As we have migrated to Mailman 3, you
Hi,
Yesterday (SW) probe 1005072 disconnected and this morning (HW) probe 60200
disconnected.
This also happened on July 18th with exactly these same two probes, then it
apparently was a problem in the Atlas infra.
Please advice.
Regards,
Ernst J. Oud
Begin forwarded message:
> From: R
I believe this is more widespread.
Probe 1005072 always connects to controller ctr-hel09 but it now tries to
connect to ctr-dub-sw01 and fails.
Please advice.
Regards,
Ernst J. Oud
> On 21 Aug 2024, at 22:40, Marek Küthe wrote:
>
> Hello,
>
> I am running two RIPE NCC Atla
Same is true for 9.9.9.9 and others, too many measurements already running
against that target. I reckon RIPE does not want to be accused of spamming/ddos
so there is a maximum.
Regards,
Ernst J. Oud
> On 10 Jul 2024, at 11:55, Malte Tashiro via ripe-atlas
> wrote:
>
> On 7
Grzegorz,
Are these software of hardware probes? If hardware then the “experiment” they
are used in has cost RIPE funds for the hardware. In my opinion that is worse
than using SW probes.
Regards,
Ernst J. Oud
Met vriendelijke groet,
Ernst J. Oud
> On 2 Jul 2024, at 11:38, Ponikier
mentioned here.
Regards,
Ernst J. Oud
> On 25 Jun 2024, at 09:19, Robert Kisteleki wrote:
>
> Hello,
>
> Indeed we are experiencing some trouble with one of our controllers.
> This can affect probes and anchors, seemingly up to 10% of the probe
> population. The team is in
?
Regards,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
/45518789/#general).
It does not at all add up.
Regards,
Ernst J. Oud
Met vriendelijke groet,
Ernst J. Oud
> On 8 Apr 2024, at 08:30, Malte Tashiro via ripe-atlas
> wrote:
>
> Hi,
>
> I'm currently looking at measurement metadata and am a bit confused about the
>
Wow! On the profile page now you can add authenticators and copy the secret key
if you add one. This works fine with WinAuth.
Thanks!
Met vriendelijke groet / Regards,
Ernst J. Oud
> On 25 Mar 2024, at 20:14, Ernst J. Oud wrote:
>
>
> L.S.
>
> Oh well, I installed
,
Ernst
> From: "Ernst J. Oud"
> Date: 25 March 2024 at 13:39:45 CET
> To: Bogdan-Stefan Rotariu
> Subject: Re: [atlas] 2FA
>
> Bogdan-Stefan,
>
> I agree with your remark about the fact that 2FA using an Authenticator on
> the same system used for the lo
been
no further announcement in this group with some help. The page on 2FA only
mentions the Oauth Toolkit for Linux. No help whatsoever for Windows users.
Any clues?
Regards,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
these probes should be contacted and if their
response does not fit with the purpose of Atlas, the probes should be disabled.
Regards,
Ernst J. Oud
> On 5 Feb 2024, at 18:54, Randy Bush wrote:
>
>
>>
>> While doing some measurement work earlier this weekend I discovere
Three of them are connected again, obviously a problem with connection to the
controller since the built-in measurements show loss of contact to the
controller but not for instance to root servers.
Ernst J. Oud
> On 30 Jan 2024, at 14:26, Victor TALVAZ wrote:
>
>
> H
Ok. Must be some Atlas problem then.
My probes are on my VDSL line (KPN), tmobile 4G and Vodafone 4G and Oracle
Cloud. That last one is in a huge datacenter with excellent internet. So
definitely not my problem :-)
Ernst J. Oud
> On 30 Jan 2024, at 14:26, Victor TALVAZ wrote:
>
not work. Flashing red LED.
What is going on?
Regards,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
Very nice.
But from the RIPE perspective the more probes in a country the better,
shouldn’t colors be different? Thus green = lots of coverage, red = almost no
coverage? Now it is the other way around.
Regards,
Ernst J. Oud
> On 15 Nov 2023, at 12:33, Stephen Suess wrote:
>
>
Appears to be working again,
Ernst
> On 20 Oct 2023, at 22:55, Ernst J. Oud wrote:
>
> Hi,
>
> I experience that lots of graphs in the web interface don’t display,
> sometimes when clicking on the built-ins tab the “loading” never finishes etc.
>
> Measurements appe
Hi,
I experience that lots of graphs in the web interface don’t display, sometimes
when clicking on the built-ins tab the “loading” never finishes etc.
Measurements appear to run fine.
Any performance problems in the back end or ripe stat?
Regards,
Ernst J. Oud
--
ripe-atlas mailing list
Hi,
I know I was a bit harsh commenting about the degraded performance of Atlas the
last couple of days.
Therefore herewith also kudos now that the problems appears to be solved. I
guess a number of people have worked hard on the issue. Appreciated!
Ernst J. Oud
--
ripe-atlas mailing list
?
Regards,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
Chris,
Thanks for your input. That clarifies a lot!
Regards,
Ernst J. Oud
> On 20 Sep 2023, at 13:22, Chris Amin wrote:
>
> On 20/09/2023 12:57, Ernst J. Oud wrote:
>
>> I checked my code that calls Magellan. It does not add the
>> “system-ipv4-works“ tag to t
Robert,
I checked my code that calls Magellan. It does not add the “system-ipv4-works“
tag to the request for probes in measurements.
Does Magellan add that tag automatically?
Regards,
Ernst J. Oud
> On 20 Sep 2023, at 12:22, Robert Kisteleki wrote:
>
> Hi,
>
>> O
,
Ernst J. Oud
> On 20 Sep 2023, at 11:56, Stephane Bortzmeyer wrote:
>
> On Wed, Sep 20, 2023 at 07:43:20AM +0200,
> Robert Kisteleki wrote
> a message of 42 lines which said:
>
>> All else (continuing to run existing measurements, creating new ones,
>> real-time
, it is a non-critical service, but people like me do rely on data from my
probes to monitor my network. It is a bit of give and take but it appears I
need another service for this…
Regards,
Ernst J. Oud
> On 20 Sep 2023, at 03:09, Fearghas Mckay wrote:
>
>
>
>> On 19
://atlas.ripe.net/measurements/60182213/[0m
[32mConnecting to stream...[0m
[32mDisconnected from stream[0m
—-
Regards,
Ernst J. Oud
> On 20 Sep 2023, at 07:43, Robert Kisteleki wrote:
>
>
>
>> On 2023-09-19 23:04, Ernst J. Oud wrote:
>> Considering the fact that al
I don’t think I fully understand what you are saying. Do you imply that Atlas
works for you?
I doubt it since all of it is down, see the status page at ripe.net, I guess
worldwide. No results are processed, no tests are running, even Magellan is
down.
Or were you joking? My Dutch sense of humo
Considering the fact that all of Atlas is completely down for more than 24
hrs., I find the silence a bit deafening. No status updates, nothing. Weird.
Not up to RIPE standards.
Regards,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe
I stand corrected. Magellan is also dead.
Regards,
Ernst J. Oud
> On 19 Sep 2023, at 20:14, Ernst J. Oud wrote:
>
> Hi,
>
> If you look here, it shows that the back-end is dead:
>
> https://atlas.ripe.net/
>
> > 20 hours backlog, 0 results processed.
>
&g
Hi,
If you look here, it shows that the back-end is dead:
https://atlas.ripe.net/
> 20 hours backlog, 0 results processed.
Magellan works fine, so streaming is ok, only storage of results seems to be
severely impacted.
Regards,
Ernst J. Oud
> On 19 Sep 2023, at 20:04, Gerdriaan
the status?
Regards,
Ernst J. Oud--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
It appears to work again. Thanks!
And it looks better than before, or am I hallucinating here?
Regards,
Ernst
> On 7 Sep 2023, at 13:18, Robert Kisteleki wrote:
>
>
>> On 2023-09-07 09:53, Ernst J. Oud wrote:
>> Hi,
>> In the web interface clicking the tab “B
> From: "Ernst J. Oud"
> Date: 7 September 2023 at 20:46:53 CEST
> To: Jerome Mao
> Subject: Re: [atlas] Questions with regard to the measurement status and
> running time
>
> My 0.02 euro; did you get the results of all 15 probes in that short period?
>
Hi,
In the web interface clicking the tab “Built-ins” does not work, it shows
“loading” and nothing happens. Tried different browsers.
Regards,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
a lot,
is it the controller (ctr-hel09) that needs to go get a beer or what?
Regards,
Ernst J. Oud
> On 3 Aug 2023, at 22:33, Ernst J. Oud wrote:
>
> I noticed that the system tag “IPv4 stable 1d” is gone from my probe at:
>
> https://atlas.ripe.net/probes/1005104/
>
>
online for 2.5 days (normally it is more
stable, but my ISP had a small downtime).
So my question is what triggers this tag? The tag is self explanatory but what
does “stable” mean?
Regards,
Ernst J. Oud--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe
/ Regards,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
monitoring on this?
Status page still mentions no issues. There clearly is.
Met vriendelijke groet / Regards,
Ernst J. Oud
> On 30 Jun 2023, at 13:24, Ernst J. Oud wrote:
>
> Hi,
>
> Measurements stream fine in Magellan, but results only show up in the web
> interface after
backend and currently are
investigating this issue.
Posted 1 day ago. Jun 29, 2023 - 08:55 UTC
But clearly this has not been resolved!
Regards,
Ernst J. Oud--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
-operate.
Regards,
Ernst J. Oud
> On 26 Jun 2023, at 15:51, Chris Amin wrote:
> Hi Ernst,
>
> There is no way to know for absolute certain if a probe will be able to carry
> out a measurement and deliver results. There are a number of factors that
> prevent a measurement be
“can be used in a measurement”.
How can I supply probe ID’s in a “create measurement” command using Magellan
knowing for sure that these probes will supply data?
Regards,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
Hi,
Yes, Latencymon is very unresponsive every now and then. Also zooming out on a
built-in measurement sometimes hangs showing no data.
Hope this can be resolved.
Met vriendelijke groet / Regards,
Ernst J. Oud
> On 1 Mar 2023, at 14:16, r...@brite.cz wrote:
>
> Hi team,
>
install of a software probe is the best way to go.
Regards,
Ernst J. Oud
> On 30 Jan 2023, at 14:07, Lukas Tribus wrote:
>
> On Mon, 30 Jan 2023 at 13:34, Robert Kisteleki wrote:
>>
>> Hi,
>>
>> To me it seems that there are oh-so-many ways of packaging and
Cristel,
I have a probe on 4G T-Mobile and one on 4G from Vodafone. Both are 24/7
connected to a Huawei router.
T-Mobile: 60200
Vodafone: 55795
Regards,
Ernst J. Oud
> On 13 Jan 2023, at 10:32, Cristel Pelsser wrote:
>
> Hello,
>
> We are looking for RIPE atlas probes tha
matters with
probe “owners” instead of using old fashioned unstructured mailing lists… the
way we did things when the internet was in its infancy?
Regards,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
I have to check but I believe the CentOS version does automatically upgrade.
Pretty sure it did with my CentOS probe running on VMware on Windows. It ran
5070 when I installed it, it now runs 5080. I did not re-install it or did
anything else.
Regards,
Ernst J. Oud
> On 7 Jan 2023, at 06
L.S.
Added a paragraph on security. Shame on me not adding that in the first version.
Available at http://www.kineta.nl/atlas/wr802n-write-up-v2.pdf
Regards,
Ernst J. Oud--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
Hi,
I promised to create a write-up on how to turn the low cost, energy
efficient, TP-Link travel router WR802N into a fully functional Atlas probe.
This write-up is now available at:
http://www.kineta.nl/atlas/wr802n-write-up-v1.pdf
Might be an idea perhaps to also mention the document somewhe
generates results, i.e. the probe infrastructure works but data storage
does not, for data from probes in NL.
Rather serious problem I guess. No mentioning on status.ripe.net though.
Had an email conversation with Robert from the Atlas team today. No solution
yet.
Regards,
Ernst J. Oud
Met
-servers.net continues normally.
Also stopped are:
#1017 Ping to ctr-nue13.atlas.ripe.net
#1012 Ping to d.root-servers.net
#1013 Ping to e.root-servers.net
#1015 Ping to h.root-servers.net
#1005 Ping to i.root-servers.net
Any idea what is causing this?
Regards,
Ernst J. Oud--
ripe-atlas
expensive version with a USB port so that a USB stick can be
used to store those files. Will investigate that option.
If someone here wants a detailed write-up let me know and I will invest the
time to write it.
Regards,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https
Chris,
Weird. That probe is on AS15435 (just like me) which is an ISP that not yet
offer any ipv6 functionality. So how come ipv4-works is not tagged?
But thanks for the clarification that this tag is the reason I can’t add it. I
can’t do any ipv6 measurements to try.
Regards
Ernst J. Oud
everybody else”?
Regards,
Ernst J. Oud--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
Hi,
Just recently I realized that a probe can be labeled as “non-public”. Why is
this allowed? Atlas is a community effort. Why are probe “owners” allowed to
have benefits from using Atlas without sharing data?
Regards,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https
Asked this question before but that post did not make it to the mailing list:
Why can’t Magellan report on built-in measurement 1 (first hop)? It always
shows “No packets found”.
Met vriendelijke groet/Regards,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net
Oi, celebrated too soon. Most measurements have partial data and are hours
behind…
Regards,
Ernst J. Oud
> On 13 Dec 2022, at 20:22, Ernst J. Oud wrote:
>
> After some two hours it appears to work again.
>
> status.rip.net showed no problems…
>
> Regards,
>
> E
After some two hours it appears to work again.
status.rip.net showed no problems…
Regards,
Ernst J. Oud
> On 13 Dec 2022, at 19:54, Ernst J. Oud wrote:
>
>
> Hi,
>
> As of around 17:30 UTC on December 13th, all measurements other than
> built-ins, from the website or
the 14th…
What’s up?
Regards,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
can’t Magellan report on the first ping latency to ping.ripe.net?
It always reports “No packets found”. All other reports work fine.
TIA.
Regards,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
Hi,
@Chris Amin:
Yes, commit c53, version 3.0.3 completely solves this. My gratitude is
larger than the losses Mr. Musk is making now that Twitter is going down the
drain :-)
Thanks!
Regards,
Ernst J. Oud--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman
threading.py and client.py. What is it
doing, what is it waiting for?
Any solution?
Regards,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
,
get the measurement-ID from the URL and then use the report command, instead of
streaming.
Any ideas?
Met vriendelijke groet / Regards,
Ernst J. Oud--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
Hi,
As a result of my experiments some three moments ago I have an abandoned probe
(OpenWRT). If I power it again will it start working again or do I need te
re-apply for a new probe?
Regards,
Ernst J. Oud
Met vriendelijke groet,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas
CentOS VM is
>kept busy, the first hop is much faster. It is as if Windows and/or VMware
>suspends/sleeps the thread of the bridge when not active. I searched but did
>not find any more reports let alone solutions for this weird first hop
>phenomenon in VMware/Windows environments.
Hi,
On the “Built-ins” tab of the probe dashboard in the drop down list there is a
log to download called “Ping Alternative Second Hop”.
What is this? It returns an empty data set…
BTW… any news on the error when downloading first and second hop data?
Regards,
Ernst J. Oud
--
ripe-atlas
L.S.
Is there a sneak preview of the V5 probes available somewhere?
Regards,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
permission to perform this
action.","status":403,"title":"Forbidden","code":104}}
All other tests let me download the data fine, logged in or not.
Same happens to download first and second hop data of other public probes.
Any clues?
Regards,
Ernst J. Oud--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
Don’t know whether this is the place to share experiences but …
I installed a SW probe in Docker for Windows (the Alpine version). Turns out
traceroute doesn’t work in that setup. So I installed VMware player on that PC
(the latest version can coexist with Hyper-V which Docker requires) and Cent
running in the ATLAS loop and load the daemon if not.
Regards,
Ernst J. Oud
Met vriendelijke groet,
Ernst J. Oud
> On 30 Jun 2022, at 12:00, ripe-atlas-requ...@ripe.net wrote:
>
> Send ripe-atlas mailing list submissions to
> ripe-atlas@ripe.net
>
> To subscribe or unsubsc
Hi,
I noticed that of the probes I checked here in The Netherlands, all logging
stops at around 03:00 today (June, 22nd).
Checked a probe in Germany, same thing but stopped a couple of hours later it
seems.
Is there some problem?
Regards,
Ernst J. Oud
> On 21 Jun 2022, at 12:00, ripe-at
Hi,
Thanks for the reply. But it appears to be a common problem for Linux
containers in Docker Desktop for Windows. All traceroute commands only show
asterisks. As explained here:
https://github.com/moby/vpnkit/pull/302
(vpnkit is used by Docker in Windows).
So I will have to install the pro
Hi,
Out of curiosity, all my “Built-ins” in my software probe show data except ”#2
Second Hop to ping.ripe.net (193.0.0.164)” which shows:
“No data available for [Probe ID] / 2 for this time period.”
Any advice?
Regards,
Ernst
Update: This appears to be a docker for Windows issue. My soft
Hi,
Out of curiosity, all my “Built-ins” in my software probe show data except ”#2
Second Hop to ping.ripe.net (193.0.0.164)” which shows:
“No data available for [Probe ID] / 2 for this time period.”
Any advice?
Regards,
Ernst
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ri
90 matches
Mail list logo
