[moonq3]

Hi Raider, Barbatos, et al.,

I run the CTF East server (http://www.gametrack...4.238.89:27961/) and for some reason we're not showing up in the master server list at the moment. Looks like a couple of other folks are not either. Is there something going with the master server?

I was using master.urbanterror.net for our masters, but even after changing to:

set sv_master1 "" //This one will be set automatically by the game-engine, so just leave it blank
set sv_master2 "master.urbanterror.info"
set sv_master3 "master2.urbanterror.info"

and sending a couple of heartbeats we still don't seem to be getting picked up. Your help on this would be greatly appreciated.

Thank you.

-- MooN

[FS |HSO|RaideR]

Error: not in master

Your server is indeed not being listed. I don't know why this would be our end... our network is not banning that IP.

Has your server resolved master.urbanterror.info correctly and are you using any firewall rules which would block the heartbeat?

[moonq3]

Thanks so much for the quick reply Raider.

master.urbanterror.info resolved to 91.121.24.62:27950
master2.urbanterror.info resolved to 91.121.30.80:27950

Those the proper IPs?

Interestingly our jump server by the same IP (different port) is showing up:

qstat -q3m master.urbanterror.info | grep 64.94.238.89
Q3S  64.94.238.89:27967     3/16  0/0  ut4_rabbit_1z      0 / 0      q3ut4 -=UrT4 CTF East=-|Jump Server

I have a bunch of firewall rules, but I just added the following to the top of the list to ensure that the master servers get through, and still no go:

/usr/local/bin/iptables -A INPUT -p tcp -s 91.121.30.80 -j ACCEPT
/usr/local/bin/iptables -A INPUT -p tcp -d 91.121.30.80 -j ACCEPT
/usr/local/bin/iptables -A INPUT -p udp -s 91.121.30.80 -j ACCEPT
/usr/local/bin/iptables -A INPUT -p udp -d 91.121.30.80 -j ACCEPT
/usr/local/bin/iptables -A INPUT -p tcp -s 91.121.24.62 -j ACCEPT
/usr/local/bin/iptables -A INPUT -p tcp -d 91.121.24.62 -j ACCEPT
/usr/local/bin/iptables -A INPUT -p udp -s 91.121.24.62 -j ACCEPT
/usr/local/bin/iptables -A INPUT -p udp -d 91.121.24.62 -j ACCEPT

Also, server has been restarted and the jump server uses the same binary, which is modified off of Barbato's latest code release.
Any thoughts?

If you are using automatic getstatus banning on the master servers, would you mind checking to see if the firewall autobanned us due to a spoofed DRDoS attack, which we seem to be frequent targets of?

Thanks so much.

-- MooN