Topic: Running Quake3Arena server on 5.5

[Denis Johansen]

Hi there,

I’ve installed a game server after reading the contributed HOW-TO on this subject. (http://cyber-euskadi.com/howtos/Howto-Install-Unreal-Tournament-Server-on-SME-5.1.2.htm ) (http://cyber-euskadi.com/howtos/Howto-Install-Unreal-Tournament-Server-on-SME-5.1.2.htm )

It runs great on LOCAL network, but internet users are not allowed to connect.

My SME is version 5.5 and it runs in server-gateway mode. I’ve installed Darrell Mays Port forwarding, and has tried to forward the correct port ( 27960 – Quake3 server) to the internal port 192.168.100.2 with no success. I’ve also tried to forward to 127.0.0.1 and to localhost, and even to the “red NIC” 192.168.1.15 with NO success at all.

What do I do wrong?

I’ve been running Quake3 servers on Linux for 2 years on different RedHat installations with great success and with no worries. It’s obviously a firewall/masq problem but I can’t see the problem.


Anyone please help.

Best Regards

Dennis Johansen

[chris meredith]

I haven't used the port forwarding rpm, so I don't know if this is applicable or not, but...

Have you checked to make sure a rule exists so that the box is accepting packets on that port?  I know the rpm creates a forward rule, but does it also create the input accept rule?

[Denis Johansen]

chris meredith wrote:
>
> I haven't used the port forwarding rpm, so I don't know if
> this is applicable or not, but...
>
> Have you checked to make sure a rule exists so that the box
> is accepting packets on that port?  I know the rpm creates a
> forward rule, but does it also create the input accept rule?

How do i check that ?

/ Dennis

[chris meredith]

Look in the /etc/init.d/masq file for a rule that specifies that port.  There should be a line something like:

ipchains --append input -p tcp -s 0/0 -d $OUTERNET  27960 -j ACCEPT

You can try typing that in at the console as well if it doesn't exist.  If you type it in, substitute $OUTERNET with your external IP.  If that works you need to edit the template for the masq file so your settings don't get lost.

[Denis Johansen]

chris meredith wrote:
>
> Look in the /etc/init.d/masq file for a rule that specifies
> that port.  There should be a line something like:
>
> ipchains --append input -p tcp -s 0/0 -d $OUTERNET  27960 -j
> ACCEPT
>
> You can try typing that in at the console as well if it
> doesn't exist.  If you type it in, substitute $OUTERNET with
> your external IP.  If that works you need to edit the
> template for the masq file so your settings don't get lost.

I have these lines in the masq file

"  /usr/sbin/ipmasqadm portfw -a -P tcp -L 192.168.1.15 27960 -R 192.168.100.2 27960
    /sbin/ipchains --append input -p tcp -s 0/0 -d $OUTERNET 27960 -j ACCEPT
"
Should I change somthing here ?

/ Dennis

[chris meredith]

That looks right.  You can make sure its active:

/etc/init.d/masq restart

So,  you have connections coming from the WAN side (192.168.1.15) forwarding to a machine on the LAN side (192.168.100.2)?  That 192.168.1. address is still a private IP.  Are connections coming in from the 192.168.1 network or are you forwarding 27960 from the Internet to the SME box?

If you just go to a Quake console and do a

connect 192.168.1.15

What does it say?

[Nathan Fowler]

Quake3 runs on 27960 UDP, it also has a control port.  So allowing TCP 27960 won't do much for you.  You also have a TCP port that talks to the master server so it can propogate the server list and heartbeat to the master server.

Check out:
http://www.tsmservices.com/masq/cfm/detail.cfm?AppID=157

Consequently, I'm the guy who contributed that

Nathan

[steve]

Hey Denis,
I want to get a Quake2 server running on Linux but the documentation/instructions that I tried do not seem to work.

can you help me?

thanks,
steve

[Denis Johansen]

steve wrote:
>
> Hey Denis,
> I want to get a Quake2 server running on Linux but the
> documentation/instructions that I tried do not seem to work.
>
> can you help me?
>
> thanks,
> steve

Hi Steve,

I will look into it tomorrow morning, Danish time...

I've never run a quake2 server, but I’m sure that it’s not so different from the quakeworld server, witch is quite easy.

I’ll come back to you on this matter, but I still believe that you will face the same problems with the outside connections that I did. I haven’t solved this problem yet.

Regards

Dennis

[Denis Johansen]

Nathan Fowler wrote:
>
> Quake3 runs on 27960 UDP, it also has a control port.  So
> allowing TCP 27960 won't do much for you.  You also have a
> TCP port that talks to the master server so it can propogate
> the server list and heartbeat to the master server.
>
> Check out:
> http://www.tsmservices.com/masq/cfm/detail.cfm?AppID=157
>
> Consequently, I'm the guy who contributed that
>
> Nathan

Dear Nathan,

I’m not interesting in the master server option, so I run the server in Dedicated 1 mode, witch don’t send heartbeat to master server.

Regards

Dennis

[Johnny]

Maybe, these link's can help you a bit

http://linuxquake.com/howto/
http://www.linuxgames.com/quake/

[Denis Johansen]

Nathan Fowler wrote:
>
> Quake3 runs on 27960 UDP, it also has a control port.  So
> allowing TCP 27960 won't do much for you.  You also have a
> TCP port that talks to the master server so it can propogate
> the server list and heartbeat to the master server.
>
> Check out:
> http://www.tsmservices.com/masq/cfm/detail.cfm?AppID=157
>
> Consequently, I'm the guy who contributed that
>
> Nathan

Hi Nathan,

I’ve been reading your contribution with interest, but just to be sure, I send you the lines I have in my /etc/init.d/masq

/usr/sbin/ipmasqadm portfw -a -P tcp -L 192.168.1.15 27960 -R 192.168.100.2 27960
    /sbin/ipchains --append input -p tcp -s 0/0 -d $OUTERNET 27960 -j ACCEPT
    /usr/sbin/ipmasqadm portfw -a -P udp -L 192.168.1.15 25000 -R 127.0.0.1 25000
    /sbin/ipchains --append input -p udp -s 0/0 -d $OUTERNET 25000 -j ACCEPT
    /usr/sbin/ipmasqadm portfw -a -P udp -L 192.168.1.15 27960 -R 127.0.0.1 27960
    /sbin/ipchains --append input -p udp -s 0/0 -d $OUTERNET 27960 -j ACCEPT

These lines are made by the port forwarding rpm I installed on the SME.

Should I erase these lines?

Where exactly do I put your line “/usr/sbin/ipmasqadm autofw -A -r udp 27960 -h www.xxx.yyy.zzz” in?

Should I use the red NIC’s IP address (192.168.1.15) or should I use the routers public IP address?

Regards

Dennis

[steve]

Denis
actually i had a Q2 server running on a win2k box behind my e-smith box and just port forwarded tcp and udp port 27910 to it and it worked fine.
people could connect from outside and everything was ok
I did this from the linux command line I remember, not from the port forwarding add-on, although it should work either way
then the p200 it was running on died and i now have another computer running redhat 7.2 and want to set it up as a server
i have followed some instructions, copied all the files onto the server
but when I do a
./quake2.exe
it gives some permissions error
this is when I am logged in as root
is this the correct command to run an executable file under linux??
./
i am a total newbie, but i am learning

thanks for your help

steve

[Denis Johansen]

Hi Steve,

Go to http://files.idstuff.dk/quake2/unix/

Download the quake2-3.20-6.i386.rpm and run the command as root in the console  “rpm –Uvh quake2-3.20-6.i386.rpm”

You can’t run windows executable files under linux.

After you have installed the rpm go to your quake2 dir and run the following command

./quake2 +set game dm +set dedicated 1 +set port 27910 +exec server.cfg

Normally it’s a good idea to make a user called gameserver or what ever, due to security issues it’s not advisable to run gameservers as root.

If you need support about commands to run in the quake console then look http://www.gameadmins.com/guides/q2/q2serversetup.htm


Good luck.

/ Dennis
P.s. I don’t have quake2 my self so I couldn’t test the actually setup, but should be like that, as I looks very much like the good old Quakeworld server.

[Nathan Fowler]

“/usr/sbin/ipmasqadm autofw -A -r udp 27950 27960 -h www.xxx.yyy.zzz” should replace your portfw line.

www.xxx.yyy.zzz is the IP address of your internal box running the Q3 server.  I've had problems with PORTFW before, I assure you, you'll want to use autofw.

For whatever reason, E-Smith has stopped emailing me when there are replies to a thread, despite that the email address is valid and the checkbox has been checked.

Nathan