James Knott wrote:
IPv6 has been around for years. Why don't some people get with the program, instead of coming up with hacks to get around the address shortage. Even with this block, there still won't be enough IPv4 addresses just for mobile devices, let alone everything else. The longer people take to move to IPv6, the worse the problem is going to get.
[off-topic] My guess - many of the larger access providers have yet to feel the pain. You have mentioned it yourself, your IPv4 address virtually never changes, versus my example of hosts on a Swiss mobile network changing every other day. The latter suggests a higher contention ratio.
Why are we wasting our time trying to squeeze more life out of something that should have been retired years ago?
We will have dual-stack for years to come. No public server will go IPv6-only, unless in restricted or controlled environments, not on the world-wide internet. So even when those larger providers do start with IPv6 deployment, they cannot give up on IPv4.
Incidentally, this block represents less than 0.4% of the IPv4 address space. Will it really make a difference?
A full class A network is not to be laughed at. Enabling it in Linux is a good thing. [1] The regional internet registries (RIPE, ARIN et al) are being very tight with what remains of IPv4 addresses. Since 2015, these are all RIPE announcements regarding recovered ranges, in chronological order: [ncc-announce] [news] RIPE NCC Receives a /13 from IANA's Recovered [ncc-announce] [news] RIPE NCC Receives a /14 from IANA's Recovered [ncc-announce] [news] RIPE NCC Receives /15 from IANA's Recovered [ncc-announce] [news] RIPE NCC Receives /18 from IANA's Recovered [ncc-announce] [news] RIPE NCC Receives /19 from IANA's Recovered [ncc-announce] [news] RIPE NCC Receives /20 from IANA's Recovered [ncc-announce] [news] RIPE NCC Receives /21 from IANA’s Recovered Pool [ncc-announce] [news] RIPE NCC Receives /22 from IANA’s Recovered Pool [ncc-announce] [news] RIPE NCC Receives /23 from IANA’s Recovered Pool (all composed of non-contiguous /24 ranges). A rough calculation says the total is a mere 5% of a full class A. [1] An interesting question might be - how many applications will have a problem with that 0.0.0.0/8 range? Usually all zeros have meant all addresses or no address. Or default route. -- Per Jessen, Zürich (14.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org