Hi all,
On Wed, 11 Dec 2019, Bruce Dubbs via lfs-dev wrote:
Only in the case that the ISP does not have any ipv4 addresses
available is it really needed. I don't know how common that is.
I can't really tell either, but it will get more common and it happened to
me a few times in the past weeks. My ISP provides me an IPv4 and an IPv6
address, and for years I usually only ever used the IPv4 one. But
recently it happened a few times that there was no internet connectivity
on the IPv4 one while IPv6 was working flawlessly - with unchanged hard
and software (i.e. its the same device routing both). I'd guess they
distributed more IPv4 addresses than they had at prime time. This would
fit rather good to recent news:
https://www.ripe.net/publications/news/about-ripe-ncc-and-ripe/the-ripe-ncc-has-run-out-of-ipv4-addresses
It was quite enlightening to see what worked with IPv6 and what didn't, if
your were *suddenly* forced to use it. I was kind of surprised that most
issues were rather easy to fix - usually, software is "already" prepared
to it nowadays. Just nobody cared to configure it so far. Prominent
example: The domain of my ISPs support website only resolves to an IPv4
address... So I appreciate your effort to push IPv6. And yes, dual stack,
not IPv6 only. You can't really tell what "the other side" is doing. One
domain might only resolve to IPv4 at all, while the other resolves to both
but only IPv6 is working properly...
Uwe
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
