5 ms·
Absolutely not. Most ISPs will allocate you a fixed /64. You may well have privacy IPs in this /64, the prefix will always be the same.. A though day for privac
by Faaak 7y ago
Absolutely not.
Most ISPs will allocate you a fixed /64. You may well have privacy IPs in this /64, the prefix will always be the same..
A though day for privacy activists
- jedberg 7y agoSure, just like with an IPv4 they allocate you a fixed /32. But you get slightly more privacy by having the client able to randomize the other 1/2 of the address and use multiple addresses, which would confuse trackers. Or the trackers just look at the first /64 and ignore the rest and you're no worse off than you were with your ipV4 /32.
- saurik 7y agoYou are worse off as now you have some introspection into computers on the other side of that firewall; with NAT you could have thousands of computers and they would all get melded together as one, but unless you very carefully generate a new IP address for every single connection you make (which is how you can get back to where you were with NAT), you now have the ability to somewhat differentiate users who before would have been mixed. So it is at best the same but probably worse, at which point why not use the thing that is always at least as good if not much better?...
- Avamander 7y agoSounds like we need shorter IPv6 leases and more rotation between the prefixes, but that somehow goes a bit against what IPv6 should provide us - freedom to hold on to an address.
- zrm 7y agoSome systems already have a solution for this, since devices can have multiple IPv6 addresses at once. They have one permanent IPv6 address which is not used for outgoing connections but can be used for incoming connections, and then temporary IPv6 addresses used for outgoing connections which can be rotated arbitrarily often. The first address is permanent but can only be used if you already know it. An improvement on this would for services to request the machine to hold a specific address, permitted if the address is valid on the current network and not already in use. Then services could each have their own address (generated on first use and then requested when they start) which is effectively permanent but not the same as the addresses used by other services on the same machine.
- mirimir 7y agoIt's a wash, I think. Anyone who cares uses VPNs and/or Tor. You can do either IPv4 or IPv6 with VPNs, but the methodology is different. With IPv4, it's just NAT. With IPv6, VPN servers must assign a public address. And with Tor, sites only see the exit address.
- orbital-decay 7y ago>just like with an IPv4 they allocate you a fixed /32 Many (most?) ISPs that give you unique IPv4 addresses also use dynamic pools. Just reconnect your router and blend into the pool. Or, if you're behind NAT, you're already indistinguishable from others.
- aledalgrande 7y agoMy router is connected for months on end, and I think this is the norm, not an exception. Even if I reconnect, most of the time my provider assigns me the same IP. The only solution here is a good VPN.
- yetihehe 7y agoWhen I first installed my connection, provider forcefully disconnected my router every 23 (yes, 23) hours to prevent me from having static ip (and hosting servers on fast home connection). Now it seems my public ipv4 actually changes every several minutes, probably some kind of ipv6to4 gate. But ipv6 of one computer is unchanged since several years.
- deleted 7y ago[deleted]
- allarm 7y agoWhat do you mean by fixed /32? A PPP link?
- samoa42 7y ago> Most ISPs will allocate you a fixed /64 not really. the case where someone in a household power-cycles the router and it gets a new ipv6-addy and then one has to power-cycle all networked devices too because they have no way of knowing that the old prefix is dead, is very common.
- badrabbit 7y agoTo add on this,many will allocate a much smaller prefix. If you are being tracked by IP, the whois of your v6 address will contain what prefix is delegated,but even if they don't use whois they can simply track "subnets" (prefixes) as a data point, if a cookie or browser fingerprint is seen on multiple addresses, the address part will help pin point a specific user. With v4 you have NAT and CGNAT now that obscures your public address a bit, you lose that with v6. For privacy, you need your address to be shared by many other users. This is one reason VPNs are useful, your public IP is shared by many. It's the same problem with browser fingerprinting, the more you try to prevent it, the more trackable data points you create (e.g.: one more extension or one less default setting that makes you a few steps more unique than everyone else).