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

Software probes status on various platforms
by Robert Kisteleki 29 Jan '20

29 Jan '20

Hello, The official release of software probes is scheduled for 11(ish) of February. This means that we'll remove the barrier to register software probes at this date. The RIPE NCC provides: * the source code on github * centos7 binary package * centos8 binary package in the near future We hear people having interest in openwrt, docker, raspbian and perhaps debian versions. Some of you have these up and running as a result of one-time efforts. Unfortunately, I'm not aware that any of these manifested as being available to the public in the form of installable packages. Please speak up if you have working versions that we can point people to as this would help us encouraging people to deploy software probes without requiring them to have knowledge about installing from source... Thanks, Robert

1 0

Re: [atlas-sw-probes] SW Probe offline after reinstall & SSH KEY change
by ripe＠brite.cz 27 Jan '20

27 Jan '20

Hi team, it seems it still does not work correctly. I had to change my probe 1000078 hosting server. The situation with SSH KEY is the same as described below. Furthermore on https://atlas.ripe.net/probes/1000078/#!tab-network I can see its new IP addresses, what is weird, since it still shows Offline, but the new IPv4 and IPv6 are there. Cheers Jiri _________________________________________________________________________________ Johan ter Beest jterbeest at ripe.net Fri Jan 17 19:36:53 CET 2020 Hi Jiri, > On 17 Jan 2020, at 14:51, <ripe at brite.cz> <ripe at brite.cz> wrote: > > Hi team, > I have SW probe 1000069 running on router Turris Omnia. I had to commit factory reset and reinstall all software. All went good, I have the SW Probe running, got new SSH KEY [command "/etc/init.d/atlas get_key"] and pasted the new key to web > Update SSH Key. First it accepted, but the probe never managed to connect. I restarted the probe process and even whole router, also tried to get the key from the probe again and when pasting to Update SSH Key field it says "A probe with this key already exists. Please enter a unique key". So the new key is sure recorded correctly. For some reason the new key was not copied to the probe. I have now done this manually so it should be able to connect now > > Probe log: > root at turris:~# /etc/init.d/atlas log > 01/17/20 12:36:02 ctrl-init > 01/17/20 13:39:02 net-try > 01/17/20 13:39:05 net-ok > 01/17/20 12:39:05 ctrl-init > 01/17/20 13:42:06 net-try > 01/17/20 13:42:09 net-ok > 01/17/20 12:42:09 ctrl-init > 01/17/20 13:45:09 net-try > 01/17/20 13:45:12 net-ok > 01/17/20 12:45:12 ctrl-init > > From https://www.ripe.net/ripe/mail/archives/atlas-sw-probes/20191023/000002.html I read "We'll add a means to replace this key for an existing probe, in case you need to reinstall and lose the original key material." Does it mean it is not implemented yet? It should be implemented… I will check on Monday why it failed to copy the new key to the probe. Cheers and have a good weekend :) Johan > > Thank you > > Jiri

2 2

SW Probe offline after reinstall & SSH KEY change
by ripe＠brite.cz 17 Jan '20

17 Jan '20

Hi team, I have SW probe 1000069 running on router Turris Omnia. I had to commit factory reset and reinstall all software. All went good, I have the SW Probe running, got new SSH KEY [command "/etc/init.d/atlas get_key"] and pasted the new key to web > Update SSH Key. First it accepted, but the probe never managed to connect. I restarted the probe process and even whole router, also tried to get the key from the probe again and when pasting to Update SSH Key field it says "A probe with this key already exists. Please enter a unique key". So the new key is sure recorded correctly. Probe log: root@turris:~# /etc/init.d/atlas log 01/17/20 12:36:02 ctrl-init 01/17/20 13:39:02 net-try 01/17/20 13:39:05 net-ok 01/17/20 12:39:05 ctrl-init 01/17/20 13:42:06 net-try 01/17/20 13:42:09 net-ok 01/17/20 12:42:09 ctrl-init 01/17/20 13:45:09 net-try 01/17/20 13:45:12 net-ok 01/17/20 12:45:12 ctrl-init >From https://www.ripe.net/ripe/mail/archives/atlas-sw-probes/20191023/000002.html I read "We'll add a means to replace this key for an existing probe, in case you need to reinstall and lose the original key material." Does it mean it is not implemented yet? Thank you Jiri

2 1

Connection & Traffic - No data available...
by ripe＠brite.cz 13 Jan '20

13 Jan '20

I noticed for multiple (maybe all) SW probes there is no Connection & Traffic shown. Is it by design? Would I be able to change it for my probe? Thank you Jiri https://atlas.ripe.net/probes/1000069/

2 1

How to change RIPE Atlas Software Probe configuration and network settings?
by ripe＠brite.cz 09 Jan '20

09 Jan '20

I have RIPE Atlas Software Probe 1000069 up and running, but it somehow made up its network settings on its own. I need to virtually “plug” it into one of my other network interfaces. Is there a way how to configure its network settings? On https://atlas.ripe.net/probes/1000069/#!tab-network I show: Local Address 192.168.1.1 Gateway 10.11.5.146 Netmask 255.255.255.0 DNS Resolvers 127.0.0.1 it works, but I don’t see any interface of 10.11.5.146 (in LUCI or ifconfig), and one of my other local LAN has assigned 192.168.1.1/24 therefore the probe itself should not have the same, and I want to have the probe connected to different Network Interface. Furthermore for IPv6 it picked all IPv6 addresses of the router - one WAN and both LAN IPv6 addresses (I have two LANs), I want it different. I tried assign probe IP address via web interface, it does not work. Any idea how to configure the probe network settings? Thank you Jiri

2 2

Re: [atlas-sw-probes] SW Probe 1000069 issue
by ripe＠brite.cz 09 Jan '20

09 Jan '20

Maybe it was shortly after router reboot and it was doing clock adjusting during the time, since I am in GMT+1 timezone. The further content of file /tmp/log/ripe_sw_probe looks time-consistent. See attachment (.txt extension added. At 9:08 I rebooted the router). I uncommented those two lines in both scripts, now it does not show any messages in Log. When I run /etc/init.d/atlas restart, I get following log: Jan 9 10:21:25 turris atlas-sw-probe: Stopping atlas sw probe Jan 9 10:21:25 turris atlas-sw-probe: Kill all atlas processes Jan 9 10:21:25 turris atlas-sw-probe: Kill ssh tunnel Jan 9 10:23:37 turris telnetd[8892]: found atlas session Nothing else ATLAS related in Log. It looks the probe is now sending measurements results fine. Thanks for now, I will have further questions about the Probe network settings, will send another email shortly... Cheers Jiri ______________________________________________________________ > Od: "Philip Homburg" <philip.homburg(a)ripe.net> > Komu: atlas-sw-probes(a)ripe.net > Datum: 09.01.2020 10:35 > Předmět: Re: [atlas-sw-probes] SW Probe 1000069 issue > >Hi, > >On 2020/01/08 10:31 , ripe(a)brite.cz wrote: >> Some outputs: >> >> root@turris:~# /etc/init.d/atlas log >> 01/08/20 10:17:01 net-ok >> 01/08/20 09:17:01 reg-init >> 01/08/20 09:17:03 ctrl-init >> 01/08/20 09:17:04 keep-start >> 01/08/20 10:20:04 keep-found >> 01/08/20 10:20:04 net-ok >> 01/08/20 10:23:04 keep-found >> 01/08/20 10:23:04 net-ok >> 01/08/20 10:26:04 keep-found >> 01/08/20 10:26:04 net-ok > >The weird thing here is the timestamps. I wonder why the clock seems to >jump back for an hour for 3 of the entries. > >> Syslog: >> Jan 8 09:29:04 turris ATLAS[2929]: enough space free, no need to do anything >> Jan 8 09:29:04 turris ATLAS[2929]: buddyinfo: can't open '/proc/buddyinfo': No such file or directory >> Jan 8 09:29:04 turris ATLAS[2929]: buddyinfo: can't open '/proc/buddyinfo': No such file or directory >> Jan 8 09:29:04 turris ATLAS[2929]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt' exists >> Jan 8 09:29:04 turris ATLAS[2929]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/simpleping' exists > >This is mostly harmless. On hardware probes, those messages went to >/dev/null. The last two should be gone in the next release of software >probe code. I'll make a note to suppress the first one and make sure to >disable code that generates the 2nd and 3rd on software probes. > >When I look at our logs, I can see something weird that I don't quite >understand. > >The 'ATLAS ' and 'reginit.sh' scripts contain the lines (for the ATLAS >script, lightly different for the reginit.sh script): >#exec >/tmp/ATLAS.out 2>/tmp/ATLAS.err >#set -x > >Maybe you can uncomment those lines in both scripts, reboot and send me >the logs files? > > >Philip > > >

1 0

SW Probe 1000069 issue
by ripe＠brite.cz 09 Jan '20

09 Jan '20

Hi team, I have probe 1000069 running on Turris Omnia. I followed: https://wiki.turris.cz/doc/en/howto/atlas-probe https://atlas.ripe.net/docs/software-probe/ https://www.ripe.net/ripe/mail/archives/atlas-sw-probes/20191023/000002.html https://www.ripe.net/ripe/mail/archives/atlas-sw-probes/20191023/000004.html I was able to install, register and run. It shows as "connected". But - it seems it was working and sending measurement results for couple of minutes after registration yesterday, and then it stopped sending results since then, although it keeps showing "connected". Not sure what to check. The process is running, I restarted the router couple of times since then. Some outputs: root@turris:~# /etc/init.d/atlas log 01/08/20 10:17:01 net-ok 01/08/20 09:17:01 reg-init 01/08/20 09:17:03 ctrl-init 01/08/20 09:17:04 keep-start 01/08/20 10:20:04 keep-found 01/08/20 10:20:04 net-ok 01/08/20 10:23:04 keep-found 01/08/20 10:23:04 net-ok 01/08/20 10:26:04 keep-found 01/08/20 10:26:04 net-ok Syslog: Jan 8 09:29:04 turris ATLAS[2929]: enough space free, no need to do anything Jan 8 09:29:04 turris ATLAS[2929]: buddyinfo: can't open '/proc/buddyinfo': No such file or directory Jan 8 09:29:04 turris ATLAS[2929]: buddyinfo: can't open '/proc/buddyinfo': No such file or directory Jan 8 09:29:04 turris ATLAS[2929]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt' exists Jan 8 09:29:04 turris ATLAS[2929]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/simpleping' exists I couldn't find what the errors mean... Please advise. Thank you Jiri

3 2

Merry Christmas and a HTTP 302
by Radek Zajíc 02 Jan '20

02 Jan '20

Hi everyone, Merry Christmas (or Festive season, if you prefer) and a happy New Year to everyone! I have just registered my first software RIPE probe. I can see it in my RIPE Atlas probe list. When checking systemd logs, I can see that the probe is registered properly with its control server (which is ctr-fsn01.atlas.ripe.net). When I ran the first measurement from it, the measurement didn’t show up on the web. I see the following error in the systemd journal: pro 24 09:36:38 controller ATLAS[8785]: total size in dir: 5668 pro 24 09:36:38 controller ATLAS[8785]: httppost: before getaddrinfo pro 24 09:36:38 controller ATLAS[8785]: httppost: before connect pro 24 09:36:38 controller ATLAS[8785]: httppost: sending request pro 24 09:36:38 controller ATLAS[8785]: posting file '/var/atlas-probe/data/out/ooq/2' pro 24 09:36:38 controller ATLAS[8785]: posting file '/var/atlas-probe/data/out/ooq/1' pro 24 09:36:38 controller ATLAS[8785]: httppost: getting result pro 24 09:36:38 controller ATLAS[8785]: httppost: POST command failed: '302 ' pro 24 09:36:38 controller ATLAS[8785]: httppost: leaving with error pro 24 09:36:38 controller ATLAS[8785]: ooqd: httppost failed with 1 This conforms to what I see in tcpdump: POST /?PROBE_ID=1000060&SESSION_ID=34f398cd76888d91da4adb236e00ded25abf69bcf959509b748ad7e84b33c2c8&SRC=oneoff HTTP/1.1 Host: 127.0.0.1 Connection: close User-Agent: httppost for atlas.ripe.net Content-Type: application/x-www-form-urlencoded Content-Length: 5759 P_TO_C_REPORT RESULT { ... } HTTP/1.1 302 Location: /manage Content-Length: 0 Date: Tue, 24 Dec 2019 08:14:38 GMT Connection: close The question is: why does the probe (talking via the initiated SSH tunnel at 8080:127.0.0.1:8080) receive such a message from the controller? Is this common or a bug? O/S: Ubuntu 18.04, amd64 SW probe version: atlasswprobe==5000-1 Thanks for any insight and/or hint. Cheers, Radek Zajic

2 2

How many SW probes ...
by Novak Jirka 27 Nov '19

27 Nov '19

... can I register on my RIPE SSO account? Only one or more? Thx, NONES

2 1

Re: [atlas-sw-probes] RIPE Atlas sw probe testing kickoff
by Martin Žák 26 Nov '19

26 Nov '19

Hi, my name is Martin Žák and have SSO account with adress martin(a)commar.cz. How to enter public-key? Send for you? ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDWAfGLFnjvdyjMotZuuo0UcKMXGsLvJNHbYdtAiZyGPFPH BVWvI7NVmm9rzB4pMjHzt129x6g0nTWADGmDc/PmaCLZ9zwlkc3QvQ62C6CkSQI5d+CfE4AATyvG Oxc4RE+HBFX+Hcat+oYrcYf0QnzRD1/Jyfv5t0LgU+PHKZLt6ggFQAldPWIghSWJXiKMvH6BOgSV mFT9AFUKPoWdDhg4n0BiUN1dzcHrVgejhqYV3kUtW0dQt2TbtNCBL+acSM6I7RF8ZPfAj31ILOt9 9FVFIvlOHEaNVRMfq861abMu+rFP0KQpul8RaE6XPKMg4XQv1ca1r+fxQrdyIIFGk3nx turris-atlas Thanks. ================================= Martin Žák <mailto:martin@commar.cz> martin(a)commar.cz Skype: martin_unetice tel.: 603 203 618 soukr. tel.: 777 914 715 prac. qrcode (6)

3 2