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] SixXS issues
- Previous message (by thread): [atlas] SixXS issues
- Next message (by thread): [atlas] SixXS issues
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rolf Sommerhalder
rolf.sommerhalder at alumni.ethz.ch
Wed May 11 10:07:22 CEST 2016
Hi Philip, On Tue, May 10, 2016 at 2:56 PM, Philip Homburg <philip.homburg at ripe.net> wrote: > It seems that your IPv6 connection has issues. Around the time the ssh > connection fails, I also see IPv6 traceroutes with problems. But it is > relatively far from the probe, so it is hard to be sure about the source > of the problem. Thanks for looking into this. I have just noticed that my v3 Probe #16258 now also has a problem with IPv6. But its in a different site with quite a different setup, which is still under construction, and I plan to look after it later today :-) Just to make sure we are talking about the same v1 Probe #2922 which sits at home (on a DOCSIS cable connection, behind a NAT firewall). This is the one which had worked quite stable for months, even years, also through the SixXs tunnel. Something must have changed earlier this year when it began to go down and up every few minutes, most likely due to some (new?) issue with IPv6. Did you test indeed #2922? And from which side did you origin your traceroutes on IPv6, e.g. from this probe, or to this probe from some other location? Thanks, Rolf
- Previous message (by thread): [atlas] SixXS issues
- Next message (by thread): [atlas] SixXS issues
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]