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/[email protected]/
[atlas] Your RIPE Atlas Probe (ID: 17523) is not connected to our network
- Previous message (by thread): [atlas] [User Defined Measurements] status settings
- Next message (by thread): [atlas] Your RIPE Atlas Probe (ID: 17523) is not connected to our network
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Joachim Tingvold
joachim at tingvold.com
Tue Aug 4 19:15:13 CEST 2015
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
- Previous message (by thread): [atlas] [User Defined Measurements] status settings
- Next message (by thread): [atlas] Your RIPE Atlas Probe (ID: 17523) is not connected to our network
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]