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] shared fate for my two probes
- Previous message (by thread): [atlas] shared fate for my two probes
- Next message (by thread): [atlas] no measurements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Tue Nov 20 11:08:40 CET 2018
On 2018/11/19 17:53 , Jay Borkenhagen wrote: > Philip Homburg writes: > > On 2018/11/16 22:16 , Jay Borkenhagen wrote: > > > > > probe 11171 2018-11-16 14:42:28 UTC. > > > probe 11203 2018-11-16 14:42:33 UTC. > > > > Both probes lost all internet connectivity for a couple of hours. I have > > no idea what happened but Atlas traceroutes stop at hop 1 (and don't > > even reach the local router). > > > > Yes, but the problem was not with the networking infrastructure: For me the most obvious approach is to put the probes behind a switch that supports port mirroring and look at the actual traffic during this period. The fact that it happens to both probes at the same time makes it very unlikely that it is a probe specific hardware problem. I'm not aware of any bugs in the Linux kernel that would affect IPv4 and IPv6 at the same time. So the obvious next step is to check what actually goes over the wire.
- Previous message (by thread): [atlas] shared fate for my two probes
- Next message (by thread): [atlas] no measurements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]