04.09.2023 23:23, gene heskett wrote: ..
Ah contraire, Eduardo. My location since 1984 is in the middle northern area of WV, USA, And I am a minimum of 150 kilometers from the nearest ipv6 enabled network connection. I'm not even sure my cable modem, furnished by Shentel about 7 to 10 years ago, even can be configured to handle ipv6.
Not my choice, except where I live, place is free & clear & has been for 24 years now, good neighbors in a small county seat town. Retired for 21 years, no reason to move unless I leave in a box.By not accommodating the ipv6-less yet masses with a too bad, so sad attitude is unbecoming. You may have ipv6 at your router input, but there are millions not so lucky. You apparently have the power to fix it, please do so.
This is apples and oranges. Lack of IPv6 conectivity might be quite common still, I dunno. But lack of IPv6 *support* in the system is very uncommon. For many years v6 worked to co-exists with v4 nicely, and if there's no v6 connectivity, to fall back to v4 transparently. It just works (but I must admit, this works less and less good, since fallback code paths are tested less and less often). If you disable something on your own system which is commonly used (v6 support), it is your task to deal with the consequences. Maintainers can help in some cases or can make this easier, but this is definitely not a priority, esp. once a trivial work-around exists (to configure a package to use v4-only).
/mjt