Re: [atlas] Your RIPE Atlas Probe (ID: 17523) is not connected to our network
On 3 Aug 2015, at 1:40, RIPE Atlas wrote:
We have noticed that your probe (#17523 with description SHL46-jocke) is not connected to our infrastructure and has been disconnected since 2015-07-26 23:39 UTC.
Hi, Having some issues getting my probe to work in an v6-only environment. Doing only SLAAC (and no v4) made it unable to connect (which makes kinda sense). Made it connect temporarily via v4 so that I could set static v6-address and DNS. Waited a while, then removed v4. I could see it on the ND-table of my router, and it even replied to ping on the static v6 address I assigned it. However, it still showed up as "offline" on the Atlas portal. After some mocking around, it now seems to be in some kind of stale status (the switchport doesn't even learn the MAC address of the probe). Any takers? (-: -- Joachim
Hi Joachim, On 2015/08/04 19:15 , Joachim Tingvold wrote:
Having some issues getting my probe to work in an v6-only environment.
Doing only SLAAC (and no v4) made it unable to connect (which makes kinda sense). Made it connect temporarily via v4 so that I could set static v6-address and DNS. Waited a while, then removed v4. I could see it on the ND-table of my router, and it even replied to ping on the static v6 address I assigned it. However, it still showed up as "offline" on the Atlas portal.
After some mocking around, it now seems to be in some kind of stale status (the switchport doesn't even learn the MAC address of the probe).
Probes can be IPv6-only for a while now. They pick up DNS servers from Routing Advertisements. Even without DNS, a probe should continue trying to contact the reg. servers. Your probe last contacted reg. servers on July 26. In one instance you gave it an IPv6 DNS resolver. The second time that was no longer there. I have no idea what else happened to the probe. Philip
participants (2)
-
Joachim Tingvold -
Philip Homburg