Enable/Disable software probe
Hi, Two questions: 1. What would be the best way to temporarily disable (and enable again) a software probe? Is there some command for this besides killing all processes and run the ATLAS script again? Running a probe on CentOS, OpenWRT and Ubuntu 18.04 (all on separate ISP’s). I am currently logging the latency differences between HW and SW probes (both natively and under VMware emulation). Differences appear to be in the 1.5 ms. range. Negligible for my 4G networks but on my fiber line such a difference is more than 30% of the average latency. Will post more results soon. 2. Why 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
Hi Ernst, Let me answer your questions; The easiest way to stop ATLAS is systemctl stop atlas, or /etc/init.d/atlas stop (on OpenWRT). Not too sure there, the public OpenWRT package diverged a bit from our startup process. I’m not too sure on the Magellan report, can you share some details? Regards, Michel
On 11 Dec 2022, at 16:19, Ernst J. Oud <ernstoud@gmail.com> wrote:
Hi,
Two questions:
1. What would be the best way to temporarily disable (and enable again) a software probe? Is there some command for this besides killing all processes and run the ATLAS script again?
Running a probe on CentOS, OpenWRT and Ubuntu 18.04 (all on separate ISP’s).
I am currently logging the latency differences between HW and SW probes (both natively and under VMware emulation). Differences appear to be in the 1.5 ms. range. Negligible for my 4G networks but on my fiber line such a difference is more than 30% of the average latency. Will post more results soon.
2. Why 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
participants (2)
-
Ernst J. Oud -
Michel Stam