This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Reconnecting probe 3508 - troubleshooting
- Previous message (by thread): [atlas] Reconnecting probe 3508 - troubleshooting
- Next message (by thread): [atlas] Atlas Sagan error_message
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Budiwijaya
budiwijaya at ipv6.or.id
Wed Aug 24 03:43:32 CEST 2016
The best way I think is to request newer probe. Thank you budiwijaya On Wed, Aug 24, 2016 at 2:51 AM, Gert Doering <gert at space.net> wrote: > 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
- Previous message (by thread): [atlas] Reconnecting probe 3508 - troubleshooting
- Next message (by thread): [atlas] Atlas Sagan error_message
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]