DDoS Updates

[Kongo]

Are you online now? I can not connect.


My public IP is 85.***.221.27. The website says:

"Your current connection is not on the whitelist."

When I try to connect, the client stays on "Connecting...".

From Linux, I also tested the realm connection directly:

play.octowow.st → 92.114.107.111

92.114.107.111:3724 times out, while the TCP connection never receives a SYN-ACK.

Could you please check whether my IP is being blocked by the server firewall/DDoS protection or needs to be whitelisted?

Thank you.

Same issue here on Linux over the weekend... SYN sent, no SYN-ACK ever comes back, it just times out. Not my network, tested 3 different source IPs so ruled out ISP, VPN, and local stuff. I made a few changes and had immediate success. The login is slow though, like it is fighting through the handshake, but it slowly gets through and was in.

sudo iptables -t mangle -A OUTPUT -p tcp -d 92.114.107.48 --dport 3724 -j TTL --ttl-set 128
sudo iptables -t mangle -A OUTPUT -p tcp -d 92.114.107.59 --dport 3724 -j TTL --ttl-set 128
sudo sysctl -w net.ipv4.tcp_timestamps=0
sudo sysctl -w net.ipv4.tcp_window_scaling=0

Swap the IPs for whatever yours resolves to if different, I've seen at least 3 in the rotation (.48, .59, .111). Window scaling being off will cap your max throughput on big downloads but doesn't matter for gameplay.... Can revert anytime by flushing the mangle rule and flipping those two sysctls back to 1.

You're a fucking legend.
Give this hero his cape!

[Toptimmy]

Tinman, it work for me too.
Thanks.

So I have to do every time I restart, wtf?

[Paulelstak]

Are you online now? I can not connect.


My public IP is 85.***.221.27. The website says:

"Your current connection is not on the whitelist."

When I try to connect, the client stays on "Connecting...".

From Linux, I also tested the realm connection directly:

play.octowow.st → 92.114.107.111

92.114.107.111:3724 times out, while the TCP connection never receives a SYN-ACK.

Could you please check whether my IP is being blocked by the server firewall/DDoS protection or needs to be whitelisted?

Thank you.

Same issue here on Linux over the weekend... SYN sent, no SYN-ACK ever comes back, it just times out. Not my network, tested 3 different source IPs so ruled out ISP, VPN, and local stuff. I made a few changes and had immediate success. The login is slow though, like it is fighting through the handshake, but it slowly gets through and was in.

sudo iptables -t mangle -A OUTPUT -p tcp -d 92.114.107.48 --dport 3724 -j TTL --ttl-set 128
sudo iptables -t mangle -A OUTPUT -p tcp -d 92.114.107.59 --dport 3724 -j TTL --ttl-set 128
sudo sysctl -w net.ipv4.tcp_timestamps=0
sudo sysctl -w net.ipv4.tcp_window_scaling=0

Swap the IPs for whatever yours resolves to if different, I've seen at least 3 in the rotation (.48, .59, .111). Window scaling being off will cap your max throughput on big downloads but doesn't matter for gameplay.... Can revert anytime by flushing the mangle rule and flipping those two sysctls back to 1.

Legend! This works for me as well.

Edit: for reference I'm on Bazzite

[Tinmann]

Tinman, it work for me too.
Thanks.

So I have to do every time I restart, wtf?

You can make them permanent. I personally would just rather have it reset because I don't plan on keeping it this way as I assume at some point their filtering will be fine-tuned enough to not do passive OS filtering of sorts as well as the IP has changed a few times. I would rather just quickly change on boot-up before I start to play. But, if you want it permanent, you can run this.

sudo tee /etc/sysctl.d/99-octowow-fix.conf <<'EOF'
net.ipv4.tcp_window_scaling=0
EOF
sudo sysctl --system

sudo iptables -t mangle -A OUTPUT -p tcp -d 92.114.107.111 --dport 3724 -j TTL --ttl-set 128
sudo iptables -t mangle -A OUTPUT -p tcp -d 92.114.107.53 --dport 3724 -j TTL --ttl-set 128
sudo iptables -t mangle -A OUTPUT -p tcp -d 92.114.107.56 --dport 3724 -j TTL --ttl-set 128

sudo apt install -y iptables-persistent
sudo netfilter-persistent save

[Fany88]

just solved all of my issues by setting my IPV4 DNS IP to cloudflare (tutorials on internet)... couldnt play normally for past few days and this changed everything. Might not be your reason why u cant play, but worth try it. Also its best manual DNS server anyway, so just use it even if it doesnt work for wow.

steps to Change DNS Settings
• Open the Start menu, type Control Panel, and press Enter.
• Click on Network and Internet, then go to Network and Sharing Center.
• Click Change adapter settings on the left menu.
• Right-click your active connection (Wi-Fi or Ethernet) and select Properties.
• Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
• Select Use the following DNS server addresses.
• Enter Cloudflare's IPv4 address numbers:
• Preferred DNS server: 1.1.1.1
• Alternate DNS server: 1.0.0.1

[Aind]

just solved all of my issues by setting my IPV4 DNS IP to cloudflare (tutorials on internet)... couldnt play normally for past few days and this changed everything. Might not be your reason why u cant play, but worth try it. Also its best manual DNS server anyway, so just use it even if it doesnt work for wow.

steps to Change DNS Settings
• Open the Start menu, type Control Panel, and press Enter.
• Click on Network and Internet, then go to Network and Sharing Center.
• Click Change adapter settings on the left menu.
• Right-click your active connection (Wi-Fi or Ethernet) and select Properties.
• Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
• Select Use the following DNS server addresses.
• Enter Cloudflare's IPv4 address numbers:
• Preferred DNS server: 1.1.1.1
• Alternate DNS server: 1.0.0.1

It didn’t help me.

[Pindarf]

Are you online now? I can not connect.


My public IP is 85.***.221.27. The website says:

"Your current connection is not on the whitelist."

When I try to connect, the client stays on "Connecting...".

From Linux, I also tested the realm connection directly:

play.octowow.st → 92.114.107.111

92.114.107.111:3724 times out, while the TCP connection never receives a SYN-ACK.

Could you please check whether my IP is being blocked by the server firewall/DDoS protection or needs to be whitelisted?

Thank you.

Same issue here on Linux over the weekend... SYN sent, no SYN-ACK ever comes back, it just times out. Not my network, tested 3 different source IPs so ruled out ISP, VPN, and local stuff. I made a few changes and had immediate success. The login is slow though, like it is fighting through the handshake, but it slowly gets through and was in.

sudo iptables -t mangle -A OUTPUT -p tcp -d 92.114.107.48 --dport 3724 -j TTL --ttl-set 128
sudo iptables -t mangle -A OUTPUT -p tcp -d 92.114.107.59 --dport 3724 -j TTL --ttl-set 128
sudo sysctl -w net.ipv4.tcp_timestamps=0
sudo sysctl -w net.ipv4.tcp_window_scaling=0

Swap the IPs for whatever yours resolves to if different, I've seen at least 3 in the rotation (.48, .59, .111). Window scaling being off will cap your max throughput on big downloads but doesn't matter for gameplay.... Can revert anytime by flushing the mangle rule and flipping those two sysctls back to 1.

Worked like a charm, THANKS!

[Aind]

This solution helped me. I downloaded it, ran it, and everything worked.
https://octowow.st/forum/viewtopic.php?p=16585#p16585

[Choochootrain]

Are you online now? I can not connect.


My public IP is 85.***.221.27. The website says:

"Your current connection is not on the whitelist."

When I try to connect, the client stays on "Connecting...".

From Linux, I also tested the realm connection directly:

play.octowow.st → 92.114.107.111

92.114.107.111:3724 times out, while the TCP connection never receives a SYN-ACK.

Could you please check whether my IP is being blocked by the server firewall/DDoS protection or needs to be whitelisted?

Thank you.

Same issue here on Linux over the weekend... SYN sent, no SYN-ACK ever comes back, it just times out. Not my network, tested 3 different source IPs so ruled out ISP, VPN, and local stuff. I made a few changes and had immediate success. The login is slow though, like it is fighting through the handshake, but it slowly gets through and was in.

sudo iptables -t mangle -A OUTPUT -p tcp -d 92.114.107.48 --dport 3724 -j TTL --ttl-set 128
sudo iptables -t mangle -A OUTPUT -p tcp -d 92.114.107.59 --dport 3724 -j TTL --ttl-set 128
sudo sysctl -w net.ipv4.tcp_timestamps=0
sudo sysctl -w net.ipv4.tcp_window_scaling=0

Swap the IPs for whatever yours resolves to if different, I've seen at least 3 in the rotation (.48, .59, .111). Window scaling being off will cap your max throughput on big downloads but doesn't matter for gameplay.... Can revert anytime by flushing the mangle rule and flipping those two sysctls back to 1.

Excellent work, sir! 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

Then, to test if it has been set:

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'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 problem is they're using "this traffic is likely from a Linux host... it 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.

[Hataph]

This solution helped me. I downloaded it, ran it, and everything worked.
https://octowow.st/forum/viewtopic.php?p=16585#p16585

I have tested the DLL and it seem to work too without modifying the iptables or hosts entry.
Not sure about the security aspect of it thou.

https://github.com/fmustafayaman/OctoLogin