I spent a week without IPv4 (2023)

Re:I spent a week without IPv4 (2023) by WarOnPrivacy on Saturday December 20, 2025 @02:26PM (#46338812)

> Every time I look at a [long] ipv6 address my brain goes “fack this”.

I do get that but I also get 'There are so many I could have all I wanted ... or I could if any of our fiber ISPs would support it, that is'

[ Parent | on HN ]

Re:I spent a week without IPv4 (2023) by hdgvhicv on Saturday December 20, 2025 @04:21PM (#46339743)

I finally clicked when I worked out it was 2^64 subnets . You have a common prefix of you /48, which isn’t much longer than an ipv4 address - especially as it seems everything is 2001::/16, which means you basically have to remember a 32 bit network prefix just like 12.45.67.8/32.

That becomes 2001:0c2d:4308::/48 instead

After that you just need to remember the subnet number and the host number. If you remember 12.45.67.8 maps to 192.168.13.7 you might have

2001:0c2d:4308:13::7

So subnet “13” and host “7”

It’s not much different to remebering 12.45.67.8>192.168.13.7

[ Parent | on HN ]

Re:I spent a week without IPv4 (2023) by WarOnPrivacy on Saturday December 20, 2025 @04:53PM (#46339984)

> especially as it seems everything is 2001::/16

I was sort of expecting that this week.

I had to transcribe a v6 addy for a WAN-WAN test (a few mi apart).

That's when I noticed that Charter (Spectrum) had issued

   2603:: for one WAN and 
   2602:: for the other WAN.

ref: https://bgp.he.net/AS33363#_prefixes6

[ Parent | on HN ]

Re:I spent a week without IPv4 (2023) by themafia on Saturday December 20, 2025 @11:23PM (#46342240)

The current global unicast space is actually limited to just 2000::/3.

https://www.iana.org/assignments/ipv6-address-space/ipv6-add...

[ Parent | on HN ]