3 ms·
This is how the majority of ipv6 is deployed where I live. The router in a coffee shop gives you an ULA, and NATs everything to a single globally routable publ
by aboardRat4 7mo ago
This is how the majority of ipv6 is deployed where I live.
The router in a coffee shop gives you an ULA, and NATs everything to a single globally routable public ipv6 address.
- fulafel 7mo agoThat's completely f'd of course (and unlike any deployment i've seen).
- aboardRat4 7mo agoIt's not. It's simple, understandable, straightforward. Only natting to a single address is flawed, but also understandable, because they want to charge you for a prefix.
- simoncion 7mo ago> It's not [fucked up]. It's simple, understandable, straightforward. Things that are fucked up can also be simple, understandable, and straightforward. Unless you're claiming that DHCPv6 is not simple, understandable, and straightforward... in which case: DHCPv4 is "Give me an IP address, please.". DHCPv6 is "Give me an IP address, please. And also give me what I need for all of my directly-connected friends to have one, too, if you don't mind.".
- aboardRat4 7mo agoDhcpv6 is not simple because it's not universally available. A lot of devices don't support it and likely never will.
- simoncion 7mo agoIf your edge router supports IPv6, it almost certainly can make a DHCPv6-PD request and handle advertising the assigned prefix on its LAN side. Because of Google's continued (deliberate?) misunderstanding of what DHCPv6 is for, Android clients don't do anything sane with it. That doesn't mean that DHCPv6 isn't simple. Again, DHCPv6 is "Please give me an IP address, and maybe also what my directly-attached friends need to get IP addresses.". Simple, straightforward, and easy to understand. Even if it were relevant, Google's chronic rectocranial insertion doesn't change that.
- aboardRat4 7mo agoIf a protocol can be misunderstood (especially deliberately), it means that it isn't simple.