<![CDATA[IPv6 adoption statistics – Google]]>This post did not contain any content.
Link Preview Image
IPv6 – Google

favicon

(www.google.com)
]]>https://isurg.org/topic/8a681b79-3c33-4702-9b41-039b91d102f1/ipv6-adoption-statistics-googleRSS for NodeFri, 01 May 2026 05:07:00 GMTSat, 25 Apr 2026 06:26:17 GMT60<![CDATA[Reply to IPv6 adoption statistics – Google on Mon, 27 Apr 2026 20:17:56 GMT]]>

I’m concerned about the privacy implications of MAC addresses being sent to everybody and their mother.

Unless something has drastically changed from my understanding MAC addresses only operate on Layer 2 (Data Link). Anything IP related is handled at Layer 3 (Network). MAC addresses aren't routable, so the chatter where MAC addresses would happen don't make it to the other side of a router on another network interface.

]]>https://isurg.org/post/https://lemmy.world/comment/23440010https://isurg.org/post/https://lemmy.world/comment/23440010Mon, 27 Apr 2026 20:17:56 GMT<![CDATA[Reply to IPv6 adoption statistics – Google on Sun, 26 Apr 2026 04:05:48 GMT]]>

From the perspective of the internet, and any properly configured routing infrastructure, they should only ever be interested in the first 64 bits when routing, the second 64 should be exclusively the domain of the last segment.

Interesting. But routers don't actually strip that, do they? So the endpoint I'm communicating with will still get the full /128 address? I'm concerned about the privacy implications of MAC addresses being sent to everybody and their mother.

]]>https://isurg.org/post/https://lemmy.zip/comment/26111710https://isurg.org/post/https://lemmy.zip/comment/26111710Sun, 26 Apr 2026 04:05:48 GMT<![CDATA[Reply to IPv6 adoption statistics – Google on Sat, 25 Apr 2026 23:44:14 GMT]]>The only legitimate v6 prefix smaller than /64 is /127, to be used for point to point links, similar to /31’s in v4, but these aren’t processed for routing outside of the boxes the link is configured on.

The concepts of addressing for v4 and v6 don’t map 1:1.

From the perspective of the internet, and any properly configured routing infrastructure, they should only ever be interested in the first 64 bits when routing, the second 64 should be exclusively the domain of the last segment. It’s like inserting an additional type of addressing between the routing portion and the protocol port.

You kind of have this with v4, but it’s variable, particularly since CIDR shot the v4 address classes in the head, so the equipment had to be able to process the entire address with every routing lookup and other functions.

]]>https://isurg.org/post/https://sh.itjust.works/comment/25030499https://isurg.org/post/https://sh.itjust.works/comment/25030499Sat, 25 Apr 2026 23:44:14 GMT<![CDATA[Reply to IPv6 adoption statistics – Google on Sat, 25 Apr 2026 21:52:52 GMT]]>You can't subnet below a /64 at all? Or it just makes things like SLAAC/auto-addressing using the MAC address unusable?

]]>https://isurg.org/post/https://lemmy.zip/comment/26107633https://isurg.org/post/https://lemmy.zip/comment/26107633Sat, 25 Apr 2026 21:52:52 GMT<![CDATA[Reply to IPv6 adoption statistics – Google on Sat, 25 Apr 2026 20:09:51 GMT]]>An IPv6 subnet must be /64. Anything else breaks stuff. If you want a separate network for guests or IoT devices, a single /64 won't be enough because it can't be divided up any smaller.

]]>https://isurg.org/post/https://discuss.tchncs.de/comment/25400588https://isurg.org/post/https://discuss.tchncs.de/comment/25400588Sat, 25 Apr 2026 20:09:51 GMT<![CDATA[Reply to IPv6 adoption statistics – Google on Sat, 25 Apr 2026 19:51:02 GMT]]>Doesn't a /64 already give me more than I'll ever use?

]]>https://isurg.org/post/https://lemmy.zip/comment/26106045https://isurg.org/post/https://lemmy.zip/comment/26106045Sat, 25 Apr 2026 19:51:02 GMT<![CDATA[Reply to IPv6 adoption statistics – Google on Sat, 25 Apr 2026 18:59:18 GMT]]>You need to find out if your ISP supports prefix delegation. A /64 will only give you one subnet. An ISP should supply a /56 if your router requests it. There are some bad ISPs out there that won't though.

]]>https://isurg.org/post/https://discuss.tchncs.de/comment/25399607https://isurg.org/post/https://discuss.tchncs.de/comment/25399607Sat, 25 Apr 2026 18:59:18 GMT<![CDATA[Reply to IPv6 adoption statistics – Google on Sat, 25 Apr 2026 18:13:59 GMT]]>I gotta suck it up and learn IPv6. My ISP now provides me with a /64. But I feel like I have a lot of knowledge gaps on their features so I'm worried about security. Especially with all the new features like SLAAC.

What's the best crash course these days? Go through Cisco materials or something?

]]>https://isurg.org/post/https://lemmy.zip/comment/26104595https://isurg.org/post/https://lemmy.zip/comment/26104595Sat, 25 Apr 2026 18:13:59 GMT