[atlas] Reconnecting probe 3508 - troubleshooting

On Tue, Aug 23, 2016 at 10:52:58AM +0200, Philip Homburg wrote:
> One possible explanation is that the probe doesn't actually receive any
> packets (i.e. the receive circuitry at the ethernet level is broken).
> The only way to know for sure is to open up the probe and attach a
> serial console. But I'm not aware of any software failure mode that
> leads to this behavior.

Hmm. The odd thing is that the first time I powered it on (after it had
been powered off for a long time), it received the lease correctly. When
that expired and it needed to renew, the problems started gain (and exactly
the same DHCP problem I had that caused me to disconnect it some years
back).

Oddly, even after receiving an IP the first time, it was able to do DNS
requests (they showed up in the SOS log on the Atlas site), but it wasn't
able to report via ssh on 443 (which works fine from other hosts on the
same network).

Argh, this is so frustrating :(

Is it possible to open a V1 probe and connect a serial console without
damaging it?

Cheers, MJ
-- 
Michael-John Turner * mj at mjturner.net * http://mjturner.net/