[atlas]Falling back to IPv4 if IPv6 connectivity is lost?
Kenneth Aalberg kenneaal at abohelse.onmicrosoft.com
Thu Jul 7 18:40:01 CEST 2011
Greetings, Probers. (Yes, that was the first name that came to mind. :P ) I've joined the probecloud, and it is working fine. However, I am on an IPv6 tunnel behind a NAT that doesn't let me configure protocol 41 to be forwarded to one specific host (my linux router). Thus, the AYIYA tunnel is in a NAT table as a normal connection, and will sometimes be cycled out if it is the oldest connection and a new one is attempted, regardless of whether the NAT entry has seen traffic recently or not. The probe receives an IPv6 address, and uses this correctly. However, if the tunnel should go down, the probe will also be marked as down, even if it is actually still alive and can communicate through IPv4. Is there any kind of fallback option to try IPv4 connections before declaring a probe host down? Or would it make more sense for me to disable IPv6 on the probe to ensure it accurately represents the actual state of my connectivity? Best regards, Kenneth Aalberg Probe 737. -------------- next part -------------- An HTML attachment was scrubbed... URL: https://www.ripe.net/ripe/mail/archives/ripe-atlas/attachments/20110707/7612ba8e/attachment.html