Yes, exactly, that's what I use.
Instead of trying to solve the problem of Fingerprinting by completely disabling and then finding ways of enabling/disabling, you can solve the problem by just spoofing the fingerprinting.
Helps to present the problem first, instead of the solution you think is best but can't find an answer for. Usually the reason is that there is a better solution.
Test the implementation here: https://browserleaks.com/
Well I appreciate the downvote from ya but this is likely an x-y problem.
Was going to suggest an extension to create false fingerprinting since I can't think of any other reason.
Why do you disable it at all?
I thankfully have never had the misfortune of cgnat
Yeah dropping Nat is the biggest net benefit I agree but I think the avg person won't really find that much value in it when Nat works ok
Go to the Google page with pixel images, you'll see for April/may some "A2" releases specifically for vzw and tmo.
These were created because the original releases had some sort of incompatibility with the networks.
If you weren't affected it's because of staged roll outs working as expected. Once google saw devices being affected the stopped the rollout. That's why back in April people were complaining about late releases.
Google: Verizon pixel update and you get a ton of threads for it. Here's one example acknowledging it but not fully talking about it https://support.google.com/pixelphone/thread/270770116/2nd-pixel-april-update-needs-to-fix-all-cellular-network-issues-for-each-pixel-affected?hl=en
It's the first thing I pulled up I don't have time to go backwards on a known topic.
Modem firmware going through vzw and tmo QA.
Because the last two months security updates kicked people off these networks completely and they had to provide 2nd updates for these modems.
Your prefix can change yes but the recommendation is that it shouldn't in practice. You'll find ISPs doing it right will extend your PD lease infinitely unless you release it for a long enough period of time. Similar to ipv4.
The privacy is similar to ipv4 also. All your traffic on ipv4 looks like it's coming from your WAN IP... Your PD is in this sense equivalent (though not literally equivalent for all the pedants reading) to your WAN IP.
It's honestly super simple to set up. Outside of your ISP config it's almost all autoconfig. 100% of the complication (at least for me) comes from knowing ipv4 first for 20 years and then trying to incorrectly map those concepts to V6.
As soon as I "let go" it was fine.
There's not a huge net benefit you're right. I mostly wanted to learn and I hope to be at the front edge of disabling ipv4 in the near distant future.
It's a re-election tactic. He knew all along.
I agree with this but I would say the prefix is the only thing you should focus on.
It's important that ISPs don't regularly rotate your PD and it's part of the rfc recommendations that they don't. And the remainder of the prefix is your vlan space that is as important for VLAN routing as always.
But disabling it creates a whole slew of issues, hence the post. Turns out there's much better solutions.