Re: [atlas] dead v1 probe
i have a few dead v1s. but they are a kkm away, where we would have to send remote hands in :( randy
Re: [atlas] dead v1 probe
On 2020/06/02 20:28 , Gert Doering wrote: > have there been software updates for v1 probes recently? I've heard > about a few v1 probes that have died "just last week" - mine among > them (#461), fell off the net with "Firewall Problems Suspected", > but it's no longer even ARPing properly (= either it totally lost > its config and wants DHCP now, which there isn't in this network, > or it just died)... No there haven't been any software updates for a very long time. For this reason they should be considered obsolete. However, we currently still support them, and we will try to release new firmware if there is a security issue. It seems that v1 and v2 probes are now starting to die faster. I have no idea what part is wearing out. Unfortuantely, due to corona, we are out of v4 probes. So the best thing to do at the moment is to replace dead v1/v2 probes with software probes. Philip signature.asc Description: OpenPGP digital signature
Re: [atlas] dead v1 probe
Gert Doering wrote on 02/06/2020 19:28: have there been software updates for v1 probes recently? I've heard about a few v1 probes that have died "just last week" - mine among them (#461), fell off the net with "Firewall Problems Suspected", but it's no longer even ARPing properly (= either it totally lost its config and wants DHCP now, which there isn't in this network, or it just died)... So knowing whether this is a more widespread issue and possible reasons would help me to decide how much effort to invest in debugging this. as you mention it, one of my v1 probes died on sunday: Your probe 127 has been disconnected from the RIPE Atlas infrastructure since 2020-05-31 21:55:58 UTC. Did this coincide with a software update or something on the control side? Nick
Re: [atlas] dead v1 probe
My v1 probe is working fine. My v3 probe unfortunately is not. IPv4 was out for some weeks (IPv6 working fine), but i fixed it yesterday (changed the usb stick). It's now reachable over IPv4 (ICMP) but somehow it can't register itself... Regards, Carlos On Tue, 2 Jun 2020 at 20:08, Hugh Saunders wrote: > > > On Tue, 2 Jun 2020 at 19:29, Gert Doering wrote: > >> Hi, >> >> have there been software updates for v1 probes recently? I've heard >> about a few v1 probes that have died "just last week" - mine among >> them (#461), fell off the net with "Firewall Problems Suspected", >> but it's no longer even ARPing properly (= either it totally lost >> its config and wants DHCP now, which there isn't in this network, >> or it just died)... > > > My v1 probe died a few months ago and the ripe team replaced it with a > current one. I guess the v1s are ageing out. > > — > Hugh Saunders >
Re: [atlas] dead v1 probe
On Tue, 2 Jun 2020 at 19:29, Gert Doering wrote: > Hi, > > have there been software updates for v1 probes recently? I've heard > about a few v1 probes that have died "just last week" - mine among > them (#461), fell off the net with "Firewall Problems Suspected", > but it's no longer even ARPing properly (= either it totally lost > its config and wants DHCP now, which there isn't in this network, > or it just died)... My v1 probe died a few months ago and the ripe team replaced it with a current one. I guess the v1s are ageing out. — Hugh Saunders
Re: [atlas] dead v1 probe
On 02.06.2020 20:34, Gert Doering wrote: > On Tue, Jun 02, 2020 at 08:32:30PM +0200, Carsten Schiefner wrote: >> Mine is fine, Gert. :-) > > Then it's maybe just old age (and the location is not particularily > well air-conditioned)... Seems that your probe eventually got to its Roy Batty moment then: https://www.youtube.com/watch?v=NoAzpa1x7jU=155
Re: [atlas] dead v1 probe
Hi, On Tue, Jun 02, 2020 at 08:32:30PM +0200, Carsten Schiefner wrote: > Mine is fine, Gert. :-) Then it's maybe just old age (and the location is not particularily well air-conditioned)... Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 signature.asc Description: PGP signature
Re: [atlas] dead v1 probe
Mine is fine, Gert. :-) On 02.06.2020 20:28, Gert Doering wrote: > Hi, > > have there been software updates for v1 probes recently? I've heard > about a few v1 probes that have died "just last week" - mine among > them (#461), fell off the net with "Firewall Problems Suspected", > but it's no longer even ARPing properly (= either it totally lost > its config and wants DHCP now, which there isn't in this network, > or it just died)... > > So knowing whether this is a more widespread issue and possible reasons > would help me to decide how much effort to invest in debugging this. > > gert
[atlas] dead v1 probe
Hi, have there been software updates for v1 probes recently? I've heard about a few v1 probes that have died "just last week" - mine among them (#461), fell off the net with "Firewall Problems Suspected", but it's no longer even ARPing properly (= either it totally lost its config and wants DHCP now, which there isn't in this network, or it just died)... So knowing whether this is a more widespread issue and possible reasons would help me to decide how much effort to invest in debugging this. gert -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 signature.asc Description: PGP signature
Re: [atlas] RIPE Atlas Software Probes and Ubuntu 20.04 / glibc 2.31
Hi Bernd, On 2020/05/24 13:04 , Bernd Strehhuber wrote: > with newer Linux Dists / glibc Versions (tested on Ubuntu 20.04 LTS) > stime() has been deprecated and replaced with clock_settime(). > Busybox got the following commit back in 11/2019: > > https://git.busybox.net/busybox/commit/?id=d3539be8f27b8cbfdfee460fe08299158f08bcd9 > > Compiling on the latest Ubuntu version I applied the attached diff > to get things working again. I was working on removing busybox code that is not used by the Atlas measurement code. That makes it unnecessary to patch the busybox code. Replacing an stime call directly with clock_settime is not going to work (that code never runs on software probes, so I understand why it works for you). I'll work on a better patch. In any case, thanks. Philip
