[atlas] Reconnecting probe 3508 - troubleshooting

Hi,

On Tue, Aug 23, 2016 at 08:24:17PM +0100, Michael-John Turner wrote:
> 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).

Well, it can *send*.  It might not be able to *hear* the answer to the
DNS requests, so the fact that the SOS messages are seen at Atlas Central
doesn't really say anything about receiving of packets after the initial
DHCP packet...

So, it could just be borderline broken... if cold enough, it works, if
the room is warming up, it no longer receives packets...

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: </ripe/mail/archives/ripe-atlas/attachments/20160823/712c8e53/attachment.sig>