[themanualstates]

What is this article even on about? The stuff on my network assigns itself ipv6 addresses based on their mac address? That's how you can do stateless ipv6?

Regardless, ipv6 was to have more IP addresses because of ipv4 exhaustion and NAT?

My Xbox tells me my network sucks because it doesn't have ipv6, but this is a very North-American perspective regardless.

[jcgl]

> The stuff on my network assigns itself ipv6 addresses based on their mac address? That's how you can do stateless ipv6?

Nit: per RFC8064[0], most modern, non-server devices do/should configure their addresses with "semantically opaque interface identifiers"[1] rather than using their MAC address/EUI64. That stable address gets used for inbound traffic, and then outbound traffic can use temporary/privacy addresses that are randomized and change over time.

Statelessness is accomplished simply by virtue of devices self-assigning addresses using SLAAC, rather than some centralized configuration thing like DHCPv6.

[0] https://datatracker.ietf.org/doc/rfc8064/ [1] https://datatracker.ietf.org/doc/rfc7217/

[themanualstates]

OMG I love nick picking. Thanks!

Learning of RFCs is a pain lol. A random RFC8064 just appeared IMHO.

The terminology are bangers also: - semantically opaque interface identifiers - SLAAC, OUID and EUI64 - NAT64 / DNS64 - '6-in-4', '6-over-4' and '6-to-4' are different protocols - link local, ULA and GULA - DS Lite (the Nintendo?)

What even?

[dijit]

> My Xbox tells me my network sucks because it doesn't have ipv6

Pretty sure that it's complaining about lack of upnp. Which, yes, would not be an issue if we had ipv6... but ironically consoles typically have been slow to adopt ipv6 support themselves, so I'm curious if the xbox even supports it..

[badgersnake]

No they complain about ipv4 because they’re worried about layers of cgnat introducing latency which for gaming is bad.

Xbox live has had it for years because ipv6 means no nat and lower latency. It’s been there since at least the 360.

[elcritch]

Steam and Meta Quest are both terrible at ipv6. At least from a year or so back. My home netowkr supported good ipv6 networking on two providers. Steam games would mess up constantly and Quest would take minutes to load.

Steam having issues makes sense given its been around ages. Meta Quest is all new OS and code yet they managed to bork ipv6. Super annoying.

[jcgl]

Ironic, considering that Meta is one of the more notable companies to run IPv6-only internally.

[hdgvhicv]

Does Xbox work if there’s no IPv4? Because my corporate windows device doesn’t and I know other gaming consoles don’t.

[bombcar]

It’d be interesting to compile a list of hardware/software that works fine in an ipv6 only network.

[pocksuppet]

All Apple devices and iPhone apps are mandated to work on these networks, or you don't get into the app store. This is because many mobile networks are IPv6-only. IPv4-only servers are accessed through a separate gateway server provided by the network operator, with a 10-20% latency penalty, and limited throughput.