On Thu, Oct 29, 2020 at 5:48 AM Viktor Naumov wrote:
> The measurements were specified as a group with a shared probe set. A
> measurement group is considered a single unit for the purposes of scheduling.
> There were no probes found to satisfy both measurements.
> It will work if you specify
On Thu, Oct 29, 2020 at 2:26 AM Viktor Naumov wrote:
> Indeed the reason is different. What I can see from the logs is that the
> scheduler couldn't find any probe in AS4771 that would be capable of
> doing v6 measurement.
https://atlas.ripe.net/measurements/27881134/ the v4 measurement is
not
Hi,
I created 2 measurements with start time now, but neither started after 1 day
https://atlas.ripe.net/measurements/27881135/
https://atlas.ripe.net/measurements/27881134/
>
SCHEDULED from
2020-10-28T08:41:35Z
to
2020-11-11T00:35:07Z
every 900s
>none of requested probes got scheduled
Hi,
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.
Yang
Do you see anything under Network - SOS History? It should report the
type of issue over DNS A/ query to *.sos.atlas.ripe.net
Likely a DHCP/DNS issue if nothing is reported under SOS hisotry. I am
not aware of any DNS hijacking on atlas.ripe.net but probe rarely
stays connected for more than a
On Tue, Oct 11, 2016 at 4:46 AM, David Wilkinson
wrote:
> Is the probe able to get an IP via DHCP?
Yes. It is configured for DHCP on portal also.
> I have found that when you format the USB drive it looks for a DHCP server
> to get an IP before it will download the
On Tue, Oct 11, 2016 at 12:52 AM, Budiwijaya wrote:
> Usually, I formatted the disk to FAT32.
> Let the probe on and connected to internet for about 1/2 hour.
In my case it has been on for much longer than an hour, still not even
an SOS message.
Does the probe stop
Hi,
I have 2 probes that are connected but shown as offline even after
several power cycles.
I performed USB stick troubleshooting procedures by removing the USB
stick and saw NO-USB SOS message. But after inserting the USB stick
there wasn't any new SOS messages.
Plugged the USB stick to
Hi,
I got "Invalid target" error when I tried to create a measurement to
see how far some RFC 1918 prefixes got propagated (carrier not
properly filtering customer announcement). What is considered invalid
for each measurement type? Thanks.
Yang
Hello,
In https://atlas.ripe.net/measurements/2928258, I did a UDP
traceroute. "edst":"193.0.0.228" from first hop and second hop somehow
showed up in the results after the last hop that responded to
traceroute, which should have been a reply to buil-in measurement to
tt01.ripe.net. And under
It would be nice to be able to set architecture and firmware version
criteria when selecting probes, making the results more consistent and
avoid unnecessary measurements in certain cases.
Yang
Hello,
Looking through DNS queries log I saw tons of queries from the probe
for case sensitive names. Can someone please enlighten me what the
possible use cases are?
query: wWw.FacebOOK.COm IN A
query: wWW.Wikia.COM IN A
query: WwW.wIkIA.cOM IN A
query: POOl.NTP.ORg
query: Www.wikiA.CoM IN A
12 matches
Mail list logo