[Witarea] Re: [v6ops] How to make an elegant IPv4 outage
Phillip Hallam-Baker <[email protected]> Thu, 11 Jun 2026 16:01:57 -0400
| Newsgroups | gmane.ietf.tsv-area,gmane.ietf.general,gmane.ietf.v6ops |
|---|---|
| Message-ID | <CAMm+LwiAZ==Wqt208ZDoh7vQtfrciYEBe8KkWM+JSKumZ3pK+Q@mail.gmail.com> |
--===============4985921980469950186== Content-Type: multipart/alternative; boundary="000000000000c949d60653ffd5a7" --000000000000c949d60653ffd5a7 Content-Type: text/plain; charset="UTF-8" Just got off the phone with a very large ISP after a failed attempt to get an IPv6 address. Turns out that I can have IPv6 but only dynamic and only if I am on dynamic IPv4. I cannot get IPv6 for my service with static IPv4 addresses. Seems to me that we are still a long way away from being able to shutter IPv4 completely. What I have not yet tried but should is trying to use the IPv6 mapping of my IPv4 addresses. --000000000000c949d60653ffd5a7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">Jus= t got off the phone with a very large ISP after a failed attempt to get an = IPv6 address.</div><div class=3D"gmail_default" style=3D"font-size:small"><= br></div><div class=3D"gmail_default" style=3D"font-size:small">Turns out t= hat I can have IPv6 but only dynamic and only if I am on dynamic IPv4. I ca= nnot get IPv6 for my service with static IPv4 addresses.</div><div class=3D= "gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_def= ault" style=3D"font-size:small">Seems to me that we are still a long way aw= ay from being able to shutter IPv4 completely.</div><div class=3D"gmail_def= ault" style=3D"font-size:small"><br></div><div class=3D"gmail_default" styl= e=3D"font-size:small">What I have not yet tried but should is trying to use= the IPv6 mapping of my IPv4 addresses.</div></div> --000000000000c949d60653ffd5a7-- --===============4985921980469950186== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline LS0gCldpdGFyZWEgbWFpbGluZyBsaXN0IC0tIHdpdGFyZWFAaWV0Zi5vcmcKVG8gdW5zdWJzY3Jp YmUgc2VuZCBhbiBlbWFpbCB0byB3aXRhcmVhLWxlYXZlQGlldGYub3JnCg== --===============4985921980469950186==--