aixo

That's very useful, thank you.

Is it technically possible to enter the password and get the IP:PORT info without actually appearing in game lobby as a joined user? If so, does lobby have any logging possibilities which could show what users entered the password to a specific game? IMO It depends on the type of connection. I had public IP on my home router in the past, and I did get simple UDP flood DDOS attacks which targeted my public IP on various ports and caused internet link saturation and/or overloading my router. As I said I am currently behind Carrier NAT so I am exposed to the Internet only through my

Hi, I wanna ask just something to have correct expectations. I am hosting a24 games behind Carrier NAT which means that I do not have a public IP on my home router. The game host IP is public IP of my provider shared with many others. That means that the IP:PORT of each game I host is different - the port always changes since It's the NAT. I set the password (new feature in a24) for joining the game lobby. I got ddosed. Does it mean that someone had to enter the password and joined my game to get the IP:PORT information? Am I right to expect that IP:PORT of games are exposed only aft

I've installed a24 from flathub on Fedora33 (https://flathub.org/apps/details/com.play0ad.zeroad) and seems to be working well, and since native Fedora repositories still have a23 and It uses different locations for userdata I can keep both versions side by side for now. It should work for any major distro of debian/fedora/opensuse flavors.

This is how tcpdump stdout with filter for incoming UDP packets, iptables dropping any UDP packet over 10 packets per 1 second per one source and being behind my ISP NAT (so targetting only one port) looks like under the attack