Re: [atlas] Running a probe behind a NAT66

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

[atlas] No probes working today?

DNS measurements don't start today, no probes are selected for a long time. See for instance (long delay) or (no probes)

Re: [atlas] No probes working today?

On Tue, Jun 12, 2018 at 03:50:25PM +0200, Robert Kisteleki wrote a message of 21 lines which said: > The data storage backend had a few hickups today, meaning results > were queued and served with a delay around 10:00, 11:30 and > 13:30-15:00. No results were lost. I confirm it now works.

Re: [atlas] No probes working today?

On 2018-06-12 15:06, Stephane Bortzmeyer wrote: > DNS measurements don't start today, no probes are selected for a long > time. > > See for instance (long > delay) or > (no probes) Dear Stephane,

Re: [atlas] Running a probe behind a NAT66

Hello, Sorry for the noise, it appears the issue was due to a local misconfiguration after all, the GUA IP used for NAT66 was getting removed and instantly readded back to its interface every time DHCPv6 client renewed its lease from the ISP, which was every 30 minutes. Not surprisingly that