3 ms·

IPv6 offers randomly assigned addresses from the nice large subnet that you should have been given -- a /64 is 2^64 addresses, comfortably insanely larger than

by dsr_ 5y ago

IPv6 offers randomly assigned addresses from the nice large subnet that you should have been given -- a /64 is 2^64 addresses, comfortably insanely larger than the entire IPv4 internet. Your ISP can look at how many addresses you sent traffic from in a particular time period, but that's not indicative of how many machines or NICs you have.

rhn_mk1 5y ago
That would have been true if parcelling out a /64 was actually easy or common. In practice, it's designed that one /64 is one device, and it's really hard to split up that subnet, with SLAAC outright making it impossible. It's possible with some static configuration, but that's not something an average Joe is going to use, and router software I came across usually considers it an unsupported option. EDIT: disregard that, the /64 is actually the smallest subnet. It does hinder subnetting fun, but not allocation to devices. I'll leave the invalid post for the sake of transparency.
- tuyiown 5y ago
  What do you mean ? All my computer, I and suspect most ipv6 stacks updated in the last decade, assigns at least two address now by default, on linux, one showed as global, assigned by router, typically static, and others temporary ones, random /64 and used by default for outbound connections.
HWR_14 5y ago
> /64 is 2^64 addresses, comfortably insanely larger than the entire IPv4 internet. Yes. I get it is technically very possible. I still don't want most of my devices able to be identified when they poll the internet. > Your ISP can look at how many addresses you sent traffic from in a particular time period, but that's not indicative of how many machines or NICs you have. Until they start charging by the address and OS manufacturers respond by keeping them more static. Or hell, until say streaming services start counting different IPv6 addresses as machines for licenses.
- dsr_ 5y ago
  IPv4 household situation: one external IPv4 public address at your router/firewall, 2^16 invisible addresses NATted behind it - streaming service embeds a UUID in your client and reports it every time you make a request. IPv6 household situation: 2^64 external addresses at your router/firewall, 1 to N of them remain static so you can get ACK packets from the outside, up to 2^64 -1 of them are randomly reassigned every so often at the mercy of your client OS's privext implementation. Streaming service embeds a UUID in your client and reports it every time you make a request.

by dsr_ 5y ago

rhn_mk1 5y ago

That would have been true if parcelling out a /64 was actually easy or common. In practice, it's designed that one /64 is one device, and it's really hard to split up that subnet, with SLAAC outright making it impossible. It's possible with some static configuration, but that's not something an average Joe is going to use, and router software I came across usually considers it an unsupported option. EDIT: disregard that, the /64 is actually the smallest subnet. It does hinder subnetting fun, but not allocation to devices. I'll leave the invalid post for the sake of transparency.

tuyiown 5y ago
What do you mean ? All my computer, I and suspect most ipv6 stacks updated in the last decade, assigns at least two address now by default, on linux, one showed as global, assigned by router, typically static, and others temporary ones, random /64 and used by default for outbound connections.

HWR_14 5y ago

> /64 is 2^64 addresses, comfortably insanely larger than the entire IPv4 internet. Yes. I get it is technically very possible. I still don't want most of my devices able to be identified when they poll the internet. > Your ISP can look at how many addresses you sent traffic from in a particular time period, but that's not indicative of how many machines or NICs you have. Until they start charging by the address and OS manufacturers respond by keeping them more static. Or hell, until say streaming services start counting different IPv6 addresses as machines for licenses.

dsr_ 5y ago
IPv4 household situation: one external IPv4 public address at your router/firewall, 2^16 invisible addresses NATted behind it - streaming service embeds a UUID in your client and reports it every time you make a request. IPv6 household situation: 2^64 external addresses at your router/firewall, 1 to N of them remain static so you can get ACK packets from the outside, up to 2^64 -1 of them are randomly reassigned every so often at the mercy of your client OS's privext implementation. Streaming service embeds a UUID in your client and reports it every time you make a request.