On 12/12/19, Uwe Düffert via lfs-dev <[email protected]> wrote: > 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...
Am mostly responding the way I did quite a while back by saying... this is familiar with respect to at least a couple threads over at Debian-User. My memory recall is that a User might ask about how to... eh... "force" IPv6 instead of IPv4 and might then receive a little initial static back via others asking... *WHY would you want to do that?!* Above user experience quote sounds pretty likely "echoable" as one of the many user-specific situations out there answering... *THIS is why!!* Perhaps repeatedly having to fiddle around trying to get something to work has some kind of immediately detrimental trickle down effect. Silly example might be... you JUST remembered that the auction for that absolute cherry, one of a kind antique item has FIVE minutes left to go... and here you are... fiddlin' around trying to get to the webpage... AGAIN. Genuinely HATE when that happens... :D If, umm... I don't know.. "fodder" is needed to back up how it's incorporated, maybe creative Internet searches targeting a couple major Linux distributions' newbie and regular/daily/non-professional user lists might yield the real World glitches that are out there that (might) still need addressed in implementations. With ALL the [appliances] that are interconnecting today.... singular, personally identifiable numbers from one many years' old source have SURELY got to run out some day sooner than later. That means already having something else in place to handle when the replacement becomes THE go-to... of the nanosecond. On a related note, I sure like and appreciate being able to point to user-friendly sources just such as LFS when the opportunities arise to show how nice, helpful sorts work together to get it done. :) Cindy :) -- * having JUST recovered from being disconnected from the absolute AND entire rest of the WORLD for 3 weeks AGAIN, currently runs with... renewed interest in helping make sure no one else EVER has to walk in my own Shoes (Ref: device drivers with #HERO /dev/ttyACM0 on Puppy Linux Slacko to the rescue! Salute!) * -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
