[atlas] "down" probe resurrection
Philip Homburg philip.homburg at ripe.net
Mon Nov 5 16:01:37 CET 2012
On 11/5/12 14:09 , Artur Russu wrote: > Hello dear ripe community, > > I am trying to resurrect a "down" status ripe v1 probe. > > Probe is connected to a router and is auto configured for both ipv4 and ipv6. > For test purposes, ipv6 has been disabled. > > Facts: > 1 - Probe ID: 98 > 2 - probe was down for ~ 1 year (sorry) > 3 - from router I have both ipv4 and ipv6 connectivity. > 4 - sniffing shows traffic: pings, dns queries, ssl. For 22 minutes 58 seconds dumped 3.7 megabytes. > 5 - probe has old firmware - 4.030 (force upgrade?) > 6 - probe is rebooting every 5 minutes ! > 7 - ssl sessions (usually last less than 5 minutes) are finished by probe (sends FIN packet) > 8 - probe is still down > 9 - probe is natted, in the atlas interface the ipv4 is not updated > 10 - last 25 connections show nothing for ipv4 (for test purposes we are ipv4 only now, earlier we had enabled ipv6, connections were logged but no data was updated) > 11 - nothing in charts > > Please help me resurrect this baby. ;) > > The probe is continuously trying to upgrade itself. I have no idea why it doesn't succeed. After failing to upgrade, the probe continues with its normal initialization. It gets part way through and then it restarts. I now disabled the firmware upgrade, but it takes a couple of days before the probe finds out. In the mean time, the only reason we know at why the probe would reboot is if traceroute is somehow blocked. Maybe you can check where UDP based traceroute works from the network the probe is on.