Re: [atlas] Probe 24434 down but pingable

[Dave]

Fixed. A colleague was so kind to do the procedure for the USB. That fixed
it indeed. Seems it was corrupted. No IPv6 DNS reachability issue after all.

Thanks.

Op vr 30 dec. 2022 om 10:04 schreef Dave :

> Hi,
>
> One of my probes is pingable but the status is disconnected for over a
> day. Could it be that it has troubles with DNS over IPv6 and that it is not
> smart enough to fall back to IPv4?
>
> https://atlas.ripe.net/probes/24434/#tab-general
>
> Thanks,
> Dave
>
-- 
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] Probe 24434 down but pingable

[Dave]

No, it is directly connected to open internet. I have a raspberry in a
neighboring IP and it also does not have DNS over IPv6 working. IPv4 is
fine. It seems the probe does not fall back to IPv4.

Op vr 30 dec. 2022 om 10:14 schreef Stephane Bortzmeyer :

> On Fri, Dec 30, 2022 at 10:04:35AM +0100,
>  Dave  wrote
>  a message of 43 lines which said:
>
> > One of my probes is pingable but the status is disconnected for over
> > a day.
>
> Could it be also that the probe is indeed disconnected but there is
> some middlebox in front of it that intercepts ICMP echo requests, and
> then replies?
>
-- 
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

[atlas] Probe 24434 down but pingable

[Dave]

Hi,

One of my probes is pingable but the status is disconnected for over a day.
Could it be that it has troubles with DNS over IPv6 and that it is not
smart enough to fall back to IPv4?

https://atlas.ripe.net/probes/24434/#tab-general

Thanks,
Dave
-- 
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

[atlas] Shared probes not shown anymore in "my atlas"

[Dave]

Hi,

In the past the probes that had shared management were shown below the
owned probes. This is not the case anymore. Is this intentional? Can it be
restored?

Thanks,
Dave
-- 
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] Feature request DNS DoH measurement

[Dave .]

Hi,

Would it be possible for your servers to first verify whether a DOH address
is really a DNS before running actual atlas tests? If you can do it from an
IP address that also hosts a web page that explains the purpose of the
test, anyone investigating traffic coming to them is easily informed.

Thanks,
Dave


Op vr 22 mei 2020 om 10:29 schreef Philip Homburg :

> On 2020/05/20 22:00 , Yang Yu wrote:
> > As DoH is getting more adoption, it would be interesting to have DoH
> > query support on Atlas. With support added as an additional protocol
> > for DNS measurement (currently TCP/UDP), most measurement
> > creation/result parsing settings can be reused.
>
> From a technical point of view it is not that simple. RFC 8484
> recommends at least HTTP/2. Currently there is no support for HTTP/2 in
> the Atlas measurement code.
>
> The bigger problem however is that there is a policy for RIPE Atlas to
> not allow http requests to arbitrary destinations. The reasoning is that
> connecting to certain webservers from certain countries could bring
> trouble to the probe hosts.
>
> Of course policies are not set in stone. However, nobody has come up
> with a better policy proposal.
>
> Note that Atlas does support DNS over TLS.
>
>

Re: [atlas] Looking for RIPE Atlas credits

[Dave .]

5M sent. Happy testing.  :)


Op wo 20 mei 2020 om 08:57 schreef Nils Rodday :

> Dear RIPE Atlas users,
>
> As I have been using around 300M credits over the past few months and am
> close to running out, I would like to ask if somebody has some spare
> credits to transfer into my account: nils.rod...@unibw.de
>
> I am a PhD-student at the Bundeswehr University Munich & University of
> Twente.
> If you have credits to share, I would appreciate it.
>
> Thanks. :)
>
> Kind regards,
> Nils
>
>
>
>

Re: [atlas] Requesting Credits for Research

[Dave .]

35M sent.

Let us know how many you have by now :)

And when you publish a paper, please share it.

Regards,
Dave


Op wo 11 mrt. 2020 om 10:03 schreef Alex Gamero-Garrido <
agame...@eng.ucsd.edu>:

> Hi folks,
>
> My name is Alexander Gamero-Garrido and I'm a 5th year PhD student at
> CAIDA, UC San Diego. We're soon launching a large traceroute campaign for
> research and could use your generous donation of credits.
>
> We'll need about 150 million credits, but any partial amount that gets us
> closer to that goal is welcome and greatly appreciated. My account
> is agamerog at eng.ucsd.edu
>
> Thank you,
> Alex
>
> --
> *Alex Gamero-Garrido*
> *PhD Student, Computer Science*
>
> Web: cseweb.ucsd.edu/~agamerog
>
> Center for Applied Internet Data Analysis (CAIDA)
> San Diego Supercomputer Center
> UC San Diego
> Pronouns: He/Him/His
>
>
>
> <https://inboxwhenready.org/?utm_campaign=signature&utm_medium=email&utm_source=signature>
> I'm using Inbox When Ready
> <https://inboxwhenready.org/?utm_campaign=signature&utm_medium=email&utm_source=signature>
> to protect my focus.
>

Re: [atlas] running a probe via LTE access

[Dave .]

Hi,

I'm running this probe on Vodafone NL
https://atlas.ripe.net/probes/13308/

I did not limit the bandwidth and I only see a very stable bandwidth usage.
It seems it is by far from the built in tests.

The monthly usage is no concern for me. It is a test sim from work.

Regards,
Dave



Op di 18 feb. 2020 om 16:21 schreef Thomas Schäfer :

> Hi,
>
> Has anybody experience with running a probe via LTE? I see only a little
> amount if I use the tags 4g or LTE,  together with IPv6 as requirement,
> just
> less than 10.
> What is the monthly  data volume you have?
> Is it a big problem if I run in a speed limit of 32kbit/s?
>
>
> Regards,
> Thomas
>
>
>
>
>
>

Re: [atlas] measurement page broken?

[Dave .]

Hi Jasper,

Thanks for fixing and giving feedback.

Regards,
Dave


Op ma 16 dec. 2019 om 12:21 schreef Jasper den Hertog :

> hi Dave,
>
> We’ve dug into this and it turned out that the metadata for DNS
> measurements wasn’t propagating correctly through our infrastructure, but
> the measurement data (metadata + results) themselves were not affected.
>
> We’ve corrected this behaviour and have stored the metadata correctly so
> it can be retrieved by users. All the measurement ids you have mentioned in
> this thread will now return results and metadata.
>
> Thanks again for your valuable feedback and happy measuring,
>
> greetings,
>
> Jasper
>
> On 15 Dec 2019, at 20:13, Jasper den Hertog  wrote:
>
> hi Dave,
>
> Thanks for the feedback, I will try to reproduce this tomorrow. This is
> serious enough to warrant thorough investigation, we should never skip
> measurement ids, no matter what the response of a particular resolve is.
>
> I’ll keep you posted,
>
> Greetings,
>
> Jasper
>
> On 15 Dec 2019, at 18:28, Dave .  wrote:
>
> Hi Jasper,
>
> Same result for new tests unfortunately.
>
> https://atlas.ripe.net/measurements/23650744/#!general
>
> https://atlas.ripe.net/measurements/23650745/
>
> In case you want to try and reproduce it, I am trying to start a one-off
> DNS test for spotify.com or grc.com and use 74.82.42.42 (Hurricane
> Electric) as a resolver. The resolver in Amsterdam has an issue currently
> and I'd like to find out whether other nodes in other locations have the
> same issue or not. The issue was reported to HE so I guess they will have
> fixed it soon.
>
> Regards,
> Dave
>
>
> Op za 14 dec. 2019 om 14:33 schreef Jasper den Hertog  >:
>
>> hi Dave,
>>
>> I can confirm that there’s a problem with the measurements with ids your
>> mentioning.
>>
>> The creation process never finished for these measurements. The
>> measurements with the ids 23631303,23631304,23631305 and 23631307 all never
>> were created. For what I can see now this seems to be a transient problem.
>>
>> If you see other measurements with the same problem please report them to
>> us.
>>
>> We will look into the cause of this problem monday,
>>
>> greetings,
>>
>> Jasper den Hertog
>> RIPE Atlas team
>>
>>
>> On 13 Dec 2019, at 21:55, Dave .  wrote:
>>
>> Hi,
>>
>> I just started 2 measurements like 10 minutes ago but it does seem
>> something broke.
>>
>> https://atlas.ripe.net/measurements/23631307/#!probes
>>
>> Same issue here:
>> https://atlas.ripe.net/measurements23631307#!probes
>>
>> I get to see a spinner instead of the results.
>>
>> Thanks,
>> Dave
>>
>>
>>
>>
>>
>
>

Re: [atlas] measurement page broken?

[Dave .]

Hi Jasper,

Same result for new tests unfortunately.

https://atlas.ripe.net/measurements/23650744/#!general

https://atlas.ripe.net/measurements/23650745/

In case you want to try and reproduce it, I am trying to start a one-off
DNS test for spotify.com or grc.com and use 74.82.42.42 (Hurricane
Electric) as a resolver. The resolver in Amsterdam has an issue currently
and I'd like to find out whether other nodes in other locations have the
same issue or not. The issue was reported to HE so I guess they will have
fixed it soon.

Regards,
Dave


Op za 14 dec. 2019 om 14:33 schreef Jasper den Hertog :

> hi Dave,
>
> I can confirm that there’s a problem with the measurements with ids your
> mentioning.
>
> The creation process never finished for these measurements. The
> measurements with the ids 23631303,23631304,23631305 and 23631307 all never
> were created. For what I can see now this seems to be a transient problem.
>
> If you see other measurements with the same problem please report them to
> us.
>
> We will look into the cause of this problem monday,
>
> greetings,
>
> Jasper den Hertog
> RIPE Atlas team
>
>
> On 13 Dec 2019, at 21:55, Dave .  wrote:
>
> Hi,
>
> I just started 2 measurements like 10 minutes ago but it does seem
> something broke.
>
> https://atlas.ripe.net/measurements/23631307/#!probes
>
> Same issue here:
> https://atlas.ripe.net/measurements23631307#!probes
>
> I get to see a spinner instead of the results.
>
> Thanks,
> Dave
>
>
>
>
>

[atlas] measurement page broken?

[Dave .]

Hi,

I just started 2 measurements like 10 minutes ago but it does seem
something broke.

https://atlas.ripe.net/measurements/23631307/#!probes

Same issue here:
https://atlas.ripe.net/measurements/23631303/#!probes

I get to see a spinner instead of the results.

Thanks,
Dave

Re: [atlas] Probes connected to 4G/LTE

[dave]

Hi,

My probe on 4g on Vodafone Netherlands can be found here.

https://atlas.ripe.net/probes/13308/

Go ahead and run some test. If you have any further questions, let me know.

Dave


> Op 5 dec. 2019 om 18:40 heeft Ponikierski, Grzegorz  het 
> volgende geschreven:
> 
> 
> Hi all!
>  
> I'm thinking about  becoming ambassador to deploy more probes in Poland 
> including rural areas where sometimes the only option to get access to the 
> Internet is 4G/LTE. I'm interested what is your experience with 4G/LTE and 
> Atlas probes. What tags you use to mark them? How stable they are?  What RTT 
> you see to first and second hop?
>  
> Regards,
> Grzegorz

Re: [atlas] any clue rtt unreachable packet loss 100% com234.476.249

[Dave .]

Hi,

Your destination is not responding to ICMP (ping/traceroute). This is not
an Atlas issue.

Dave

Op ma 24 jun. 2019 om 08:50 schreef :

> Hello,
>
> Can some one help me with the reason behind me always getting RTT
> unreachable and packet loss 100% for every probe I choose to monitor one
> our service from internet in belgium.
>
> Is there something I am not doing right or can guid me a better way of
> doing it.
> Even though there is 100% packet loss , my credit balance is still being
> consumed.
>
> [image: inline_55_1561359035868_0.png]
>
> *Kiran Gunana *
> *Network Engineer*
> kiran.gun...@colruytgroup.com
> T+32 2 363 55 45 (Ext : 55711)
>
> Colruyt Group
> Edingensesteenweg 196 - 1500 Halle
> www.colruytgroup.com
>
> *LinkedIn*
> <https://www.linkedin.com/company/16721?trk=tyah&trkInfo=clickedVertical%3Acompany%2CentityType%3AentityHistoryName%2CclickedEntityId%3Acompany_company_16721%2Cidx%3A0>
> *Twitter* <https://twitter.com/colruytgroup>
>
>
>
>
>
> *Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website
> <http://www.colruytgroup.com/nl/algemene-voorwaarden>Ce message est soumis
> aux conditions disponibles sur notre site web
> <http://www.colruytgroup.com/fr/conditions-g%C3%A9n%C3%A9rales>This message
> is subject to the terms and conditions available on our website
> <http://www.colruytgroup.com/en/terms-use>*

Re: [atlas] Communication with probes' owners

[Dave .]

If this gets implemented, please add a checkbox where one can indicate
whether one is a user or also can get things fixed in the AS where your
probe is connected.

Op vr 19 apr. 2019 om 12:37 schreef Paolo Pozzan :

> It seems a good idea. I don't think this will be abused and in case it
> would be easy to point out the spammers.
> Would this be useful also for other kind of messages?
>
> Paolo
>
> --
>
> *Da: *"Grzegorz Ponikierski" 
> *A: *ripe-atlas@ripe.net
> *Inviato: *Mercoledì, 17 aprile 2019 19:13:37
> *Oggetto: *[atlas] Communication with probes' owners
>
> Hi all!
>
>
>
> From time to time I find probes which has incorrect country in their
> description. For example #10333 supposed to be in US but from my
> measurements it looks like it is somewhere nearby Amsterdam. If something
> has 10ms RTT to target in Amsterdam, has hops with `
> nl-ams14a-ri1-ae8-0.aorta.net
> ` description and
> has ASN for LibertyGlobal then this probe is rather in Europe. It takes
> some time to resolve such issue via RIPE team so maybe we can get a form to
> send direct and short message to probe owner to let him/her know that
> something is wrong with his/her probe and we ask for verification. What do
> you think about that?
>
>
>
> Regards,
>
> Grzegorz
>
>
>

Re: [atlas] Request RIPE Atlas Credit for Research

[Dave .]

Hi,

Hi many more credits do you need?

Regards,
Dave

Op wo 6 mrt. 2019 om 12:42 schreef 陆超逸 :

> Dear all,
>
>
> Greetings! I'm a PhD student at Tsinghua University, China.
> Recently a large-scale measurement via RIPE Atlas is needed for my
> research. However, as a new user I don't have any credit to proceed, and
> unfortunately the time doesn't allow me to earn them by myself.
>
> So I'm here to ask for help. Is it possible for anyone generous enough to
> offer me some RIPE Atlas credits (like, a million)?
> My account at RIPE NCC is lc...@mails.tsinghua.edu.cn.
> Many thanks for your help!
>
> Sincerely,
> Chaoyi Lu
>

Re: [atlas] New RIPE Atlas measurement details page

[Dave .]

Hi,

The traceroutes give a nice list like a normal traceroute would do when
clicking on the blue i-icon. Could we get such a button for DNS tests? I'd
like to be able to see the full result from the web page, just like for
traceroute.

Thanks,
Dave

Op do 31 jan. 2019 om 14:55 schreef Alun Davies :

> Dear colleagues,
>
> We have made the switch to the new and improved user interface for RIPE
> Atlas measurement details. To see the new interface right now, simply click
> on any measurement ID on the RIPE Atlas measurement listing page:
> https://atlas.ripe.net/measurements/
>
> Please note that, for a limited time, you will still be able to revert
> back to the old interface via the yellow banner at the top of the
> measurement details page.
>
> For further details on exactly what changes have been made and why, please
> see the following article on RIPE Labs:
>
> https://labs.ripe.net/Members/jasper_den_hertog/new-design-and-functionality-for-the-ripe-atlas-measurement-detail-page
>
> Kind regards,
> Alun Davies
> RIPE NCC
>
>
>
>

[atlas] status is confusing

[Dave]

Hi,

The status page of one of my probes says:



I’ve been bitten a few times by misinterpreting this. Could these 2 things be 
put on separate lines? This does suggest the probe is up but only when you 
missed the red colour and didn’t get the meaning of the icon. Also, when you 
read the mail it may be hours later than when it was sent. So keep in mind that 
a receiver’s probe could be back online in the meantime. Often a mail will be 
checked on the mobile. The status on a small screen must be clear too.

I’ll restart the probe and modem and it will work again but I would have done 
that on day 1 if the message was more clear.


Thanks,
Dave

Re: [atlas] DNS results visualisation

[Dave .]

What would be illustrated would preferably be the output of dig. Something
like this


; <<>> DiG 9.10.3-P4-Ubuntu <<>> fok.nl
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17015
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;fok.nl.IN  A
;; ANSWER SECTION:
fok.nl. 120 IN  A   104.20.93.55
fok.nl. 120 IN  A   104.20.94.55
;; Query time: 9 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Aug 22 16:41:54 CEST 2017
;; MSG SIZE  rcvd: 67







2017-08-22 12:19 GMT+02:00 Barry Raveendran Greene :

>
>
>
> > On Aug 22, 2017, at 4:14 PM, Dave .  wrote:
>
> > For the traceroute results there is a icon at the right side where you
> can get the complete traceroute. (View Latest Result) This is beautifully
> presented.
> >
> > Could we please have a similar icon for DNS results?
>
> What would be illustrated?
>
>

[atlas] DNS results visualisation

[Dave .]

Hi,
For the traceroute results there is a icon at the right side where you can
get the complete traceroute. (View Latest Result) This is beautifully
presented.

Could we please have a similar icon for DNS results?

Thanks,
Dave Boonstra

[atlas] Ping option DF

[dave]

Hi,

It seems atlas sends out ping with fragmentation allowed. Why is there no 
option to enable DF?

Thanks,
Dave.