May 2020 - atlas-sw-probes - mailman.ripe.net

How to force the SW Probe to use particular IP Interface / IP Address?
by ripe＠brite.cz 19 Jun '20

19 Jun '20

Hi team, is there a way how to force the SW Probe to use particular IP Interface / IP Address? 1. Turris Omnia Router: 1a - there is public IPv4 on WAN interface, but the probe choose LAN interface that is behind NAT, what is not necessary and would be better to choose the WAN. 1b - I have multiple IPv6 interfaces, the probe keeps choosing the one I use for testing and therefore is not as stable as the others. I would like the probe to use WAN6 interface instead. 2. CentOS virtual machine - there is public IPv4 and local IPv4 RFC1918, again, the probe choose the local instead of the public IP. It's a pity, the probe better use the public one. Take Care Jiri

3 6

Re: [atlas-sw-probes] How to force the SW Probe to use particular IP Interface / IP Address?
by Philip Homburg 25 May '20

25 May '20

On 2020/05/25 16:24 , jsuchan(a)centrum.cz wrote: > - how can I have my probe 1000069 not tagged IPv4 RFC1918? There is not much that can be done here. It is an automated process. Of course removing all interfaces with RFC 1918 addresses would do the trick. > - how can I make the probe use the default outgoing interface mentioned above? The probe just reports all of it's addresses. It is our backend system that needs to be improved. I can see that this is an issue. But I don't know how busy the people are who should implement this change. Philip

1 0

All IPv6-only software probes offline?
by Maurice Walker 12 May '20

12 May '20

Hey, It seems that all IPv6-only software probes are shown as offline since about 2020-05-12 12:48:30 UTC. I can't see anything wrong with my own probe (which is also affected). It has working Internet access and I rebooted it just to make sure. Could this be a server-side or routing issue? #1000018, #1000075, #1000076, #1000101, #1000169, ... Cheers Maurice

2 1

Software probe registered but not yet created
by Swapneel Patnekar 11 May '20

11 May '20

Hello! I've registered a software probe successfully on Ubuntu 16.04.4 LTS but it hasn't created it yet. Usually, this is done in 10-15 minutes. The machine is behind a pfSense firewall which as far as I can tell isn't blocking any requests. Can you share a troubleshooting checklist which I can try to see where the problem is? If I may make a suggestion to also update the troubleshooting page[1] for software probes Thank you. [1]: https://atlas.ripe.net/docs/troubleshoot-probe-issues/ -- Best, Swapneel https://brainattic.in/blog

1 0

How to remove unused SW-Probe
by ripe＠groetzner.net 08 May '20

08 May '20

Hello, how can I remove a unused VM-Probe? I don`t think „transfer ownership“ ist he right solution for an SW-Probe 😉 Sascha

4 3

New release v5020
by Philip Homburg 08 May '20

08 May '20

Hi, I just pushed version v5020 to github (https://github.com/RIPE-NCC/ripe-atlas-software-probe/tree/v5020) The main change is to the 'SOS' mechanism. Probes look up a special DNS name just before they try to connect. This can be used to diagnose probes that have trouble connecting. For hardware probes we rely on the probe's ethernet address to distinguish between probes. For software probes that doesn't work because we don't record ethernet addresses for software probes. We made a change to have software probes send the hash of the probe's public key instead. With this change the network tab of the probe page shows the 'SOS History'. >From this release we now also support CentOS 8 binary packages, though I noticed that we did not yet add that to the installation instructions. Finally, we changed the way we accept SSH public keys. We now accepts longer RSA keys (max. 4096 bits) as well as ECDSA and ED25519 Philip Homburg

2 2

Fwd: Thank you for applying for a RIPE Atlas software probe
by Georgi Vasilev 08 May '20

08 May '20

Hello, May I ask you to check, what is the problem with my probe. Here is the link https://atlas.ripe.net/probes/16362/ Thank you in advance Br, Georgi Vasilev ---------- Forwarded message --------- From: RIPE Atlas <no-reply(a)ripe.net> Date: Thu, Jan 30, 2020 at 12:25 PM Subject: Thank you for applying for a RIPE Atlas software probe To: Georgi Vasilev <georgi.petkov.vasilev(a)gmail.com> Dear Georgi Vasilev, Thank you for applying for a RIPE Atlas software probe! Your application ID is 91. If your application was successful, you will receive another email with the probe ID and additional instructions. We appreciate your support of the RIPE Atlas network. If you have any questions or concerns, please don't hesitate to contact atlas(a)ripe.net Kind regards, RIPE Atlas Team

2 1