Doubts regarding how GoodbyeDPI works

Community software GoodbyeDPI
1

Hey, I had a question about GoodbyeDPI. In a comment on Hacker News, the author mentioned that GoodbyeDPI uses something called “Fragmentation” which actually refers to shrinking the TCP window size to force the operating system to send smaller TCP packets.

Does this mean GoodbyeDPI is splitting TCP packets into smaller pieces? So, if I run GoodbyeDPI with a modeset of 6 (which sets the HTTP/HTTPS fragmentation value to 2), does that mean all HTTP/HTTPS traffic gets chopped up into twice as many packets? Could that introduce latency or reduce performance for online multiplayer games? Could the extra fragmentation from GoodbyeDPI impact smoothness of gameplay?

2

Current GoodbyeDPI version supports both Window Size shrinking and real segmentation by splitting the request into two pieces, optionally sending them in reverse (second piece first, then first piece).

Window size shrinking applies only to TCP connections, you could see the latency only in the beginning of the connection, as after some time Window Size gets automatically adjusted for optimal network conditions.

Segmentation also applies only to TCP connections, only to recognized HTTP/HTTPS requests, and if you use blacklist, only to blacklisted domains.
It may introduce latency only for the first several packages in the connection.

No.