<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">After 3 months, I found time to revisit this...<br class=""><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jan 24, 2022, at 03:46, Philip Homburg <<a href="mailto:philip.homburg@ripe.net" class="">philip.homburg@ripe.net</a>> wrote:</div><div class=""><div class="">On 2022/01/22 0:12 , Edward Lewis wrote:<br class=""><blockquote type="cite" class="">General question…<br class="">My probe was doing IPv6 until 15 July 2021 but not it is not. Is there any way to discover why it is no longer IPv6’ing?<br class=""></blockquote>If your IPv6 prefix is stable enough, you could manually assign an IPv6 address to the probe and see what happens.<br class=""></div></div></blockquote></div><br class=""></div><div class="">I could I manually assign an IPv6 address to the probe (22382)?</div><div class=""><br class=""></div><div class="">What I can’t get my head around is how to directly manage or query [in the sense of managing it, not measurements] the probe. I have an IPv4 address for it, so I can send it packets, but if it has a SSH service, I certainly wouldn’t have a password much less a key.</div><div class=""><br class=""></div><div class="">There is no reason I can see keeping the probe from setting up an IPv6 address. On the machines I’ve looked (at least one MacAir and one wired MacMini), IPv6 is apparently fully functional in the home network.</div><div class=""><br class=""></div><div class="">I don’t think it is a network environment problem, although, prior to July last year IPv6 worked and I did swap out some CPE equipment at the time IPv6 stopped working. In July I went from a mundane cable modem bridge in front of a NATting WIFI router to a new cable modem which I am running in bridge mode in front of the same NATing WIFI router. This switch did start the IPv6 problems for the probe. What would help is asking the probe what it sees, hence the need for something like management console access.</div><div class=""><br class=""></div><div class="">BTW, The SOS History lists AAAA queries but nothing about responses. For 18 April, it shows “no-usb” but for 19 April, that’s cleared. This just confuses me (I did replace the usb stick a few months ago), I can’t tell if the usb is still an issue. I keep staring at the log and it doesn’t seem to tell me anything. This is on </div><div class=""><br class=""></div><div class=""><a href="https://atlas.ripe.net/probes/22382/#tab-network" class="">https://atlas.ripe.net/probes/22382/#tab-network</a></div><div class=""><br class=""></div><div class="">PS - As far as the probe’s name "<span style="color: rgb(88, 89, 91); font-family: "Open Sans", Helvetica, Arial, sans-serif; orphans: 2; widows: 2; background-color: rgb(252, 252, 252);" class="">Looks like something Apple would sell</span>”, this comes from a question on a form when I registered the probe that asked for a description to it. And that’s what I thought best described the probe, didn’t realize this would become the name. ;)</div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>