3 ms·
Taking into account the DKMS + reboot + config setup - the automation like this saves time and headaches. How stable the obfuscation has been over time — do ISP
by kraftaa 6mo ago
Taking into account the DKMS + reboot + config setup - the automation like this saves time and headaches.
How stable the obfuscation has been over time — do ISPs eventually catch up?
- bivlked 6mo agoBeen running 2.0 on Russian DPI for a few months - works fine. The old version (1.x) randomized packet headers, but ISPs figured out that random bytes are themselves a fingerprint and started throttling (~3 Mbit on some mobile ISPs here). 2.0 is smarter - packets mimic actual QUIC or DNS traffic instead of looking random. ISPs can't easily filter that without breaking real QUIC, which is half the internet at this point.
- kraftaa 6mo agoMy first thought was be that randomized traffic would be the solution, but it makes sense that it stands out more than traffic that blends in by mimicking real stuff. Fingers crossed they won't figure it out quickly. I'll ask my friends if they are up to trying it, for now they are just using different VPNs.