Temporary Connectivity Fix for Linux Users
Posted: Wed Oct 07, 2026 8:21 pm
Thanks to the awesome work of Tinmann in this post:
https://octowow.st/forum/viewtopic.php? ... =50#p16470
It would seem that the connection issues for Linux users stems from the hosting provider responsible for the 92.114.107.0/25 IP addresses using traffic fingerprinting. If the server fingerprints you as Linux, then it won't even respond. Tinmann's solution is the "mangle" the TCP headers for any traffic to any 92.114.107 IP and set the TTL to 128, thus making the traffic look more "windows-ish" (I guess).
He used iptables to accomplish this. Because I'm on a newer Fedora install, I wanted to avoid using iptables. Instead, I was able to implement it using firewalld/firewall-cmd as follows:
Then, to test if it has been set:
I'm a little worried that this is still not an actual fix, since all we are doing is evading the identification of Linux traffic. The ultimate problem is they're using "Linux traffic is DDoS traffic" as a heuristic. Yeah, it probably works, but it's killing us legit players on Linux.
I certainly hope the devs pay attention to this and sort it out.
https://octowow.st/forum/viewtopic.php? ... =50#p16470
It would seem that the connection issues for Linux users stems from the hosting provider responsible for the 92.114.107.0/25 IP addresses using traffic fingerprinting. If the server fingerprints you as Linux, then it won't even respond. Tinmann's solution is the "mangle" the TCP headers for any traffic to any 92.114.107 IP and set the TTL to 128, thus making the traffic look more "windows-ish" (I guess).
He used iptables to accomplish this. Because I'm on a newer Fedora install, I wanted to avoid using iptables. Instead, I was able to implement it using firewalld/firewall-cmd as follows:
Code: Select all
>>] sudo firewall-cmd --permanent --direct --add-rule ipv4 mangle OUTPUT 0 -p tcp -d 92.114.107.0/25 --dport 3724 -j TTL --ttl-set 128
[sudo] password for *****:
success
>>] sudo firewall-cmd --reload
success
Code: Select all
>>] sudo firewall-cmd --direct --get-all-rules
ipv4 mangle OUTPUT 0 -p tcp -d 92.114.107.0/25 --dport 3724 -j TTL --ttl-set 128
I certainly hope the devs pay attention to this and sort it out.
