<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
My guess is that your IPv6 address changed on the 15 July. <br>
I think that you need to log onto your RIPE account and enter the
new IPv6 settings under the "Network" tab.<br>
========================================<br>
<div class="moz-cite-prefix">On 22/01/2022 3:08 pm, Edward Lewis
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:F95D0C79-63F2-4162-A7FF-B0AB64FAA5D4@cox.net">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Thanks - yes, Cox is my ISP. But I think all’s well in the ISP
IPv6 set up.
<div class=""><br class="">
</div>
<div class="">I have active IPv6 for other machines in the
house. I can ’ssh -6' out of my house using a laptop to a remote
VM, over v6. Checking other devices, a phone on the house wi-fi
has an IPv6 address, same /64 prefix as the laptop. Ditto for a
wired desktop. I didn’t look at everything (that would take all
night).</div>
<div class="">
<div><br class="">
</div>
<div>I mention the “wired desktop” as it is “wired" to the same
physical ethernet hub as the probe, then wired up to the ISP
CPE, etc.</div>
<div><br class="">
</div>
<div>Is it possible that the probe isn’t set up to ask for a v6
address? It seems to be playing the odd-ball here, all the
other devices do IPv6.</div>
<div><br class="">
</div>
<div>
<blockquote type="cite" class="">
<div class="">On Jan 21, 2022, at 20:35, Darin Martin <<a
href="mailto:derwood@naebunny.net"
class="moz-txt-link-freetext" moz-do-not-send="true">derwood@naebunny.net</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="auto" class="">Ed, assuming Cox is your ISP this
page has info from them regarding IPV6: <a
href="https://www.cox.com/residential/support/ip-version-6.html"
class="moz-txt-link-freetext" moz-do-not-send="true">https://www.cox.com/residential/support/ip-version-6.html</a>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">They say that as long as your
modem and router are capable, you should get IPV4 and
IPV6 addresses at the same time. Your router,
firewall, DHCP and DNS are all a big part of that.
Each one of those has to be capable and have it
enabled for the Atlas device to get an IPV6 address.
If they are, then Cox would be the next one to
contact.</div>
</div>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Jan 21, 2022 18:12, Edward
Lewis <<a href="mailto:edlewisjr@cox.net"
class="moz-txt-link-freetext" moz-do-not-send="true">edlewisjr@cox.net</a>>
wrote:<br type="attribution" class="">
<blockquote class="quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word" class="">General
question…
<div class=""><br class="">
</div>
<div 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?</div>
<div class=""><br class="">
</div>
<div class="">I did change my ISP connection
equipment about that time, so something did
change on my end.</div>
<div class=""><br class="">
</div>
<div class="">But IPv6 works for other devices.
When I go to <a href="http://www.ripe.net/"
class="" moz-do-not-send="true">www.ripe.net</a> it
tells me I came from an IPv6 address.</div>
<div class=""><br class="">
</div>
<div class="">The device has been pretty steady -
99.71% the last week, 99.91% for the last month
(30days). It was off-line 29 minutes earlier
today (the notice made me think to look), but
never off line more than 10 minutes since
mid-July. There’s one stretch of 34d+ of
continuous uptime. Run-of-the-mill home
connection via a cableTV company.</div>
<div class=""><br class="">
</div>
<div class="">Is there anyway to ask a probe why
it doesn’t have an IPv6 address (via DHCP)?</div>
<div class=""><br class="">
</div>
<div class="">Ed</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
<br>
</body>
</html>