On 2018/06/11 20:42 , Roman Mamedov wrote:
I fully expect that you didn't account for such a setup in the controller infrastructure or possibly various "local IP is valid" checks and whatnot, but why this used to work fine before? Has there been any change on your side in April that would break this kind of setup?
I started a TCP traceroute on your probe toward it's controller, but it consistently fails after hop 2. I have no idea if that is related to your NAT box. https://atlas.ripe.net/measurements/14364300/ In general it is worth noting that Atlas has support for IPv4 NAT, such as keeping track of the public address of a probe. This support in not implemented for IPv6. So if you put a probe behind some kind of IPv6 NAT, the results may be confusing to other Atlas users. Philip