Topic: Game servers ?

[Trevor Drake-Brockman]

Anyone have any success in running a game server under Mitel ???

Need help in setting up a game server to run SOF2 or Quake.

[Terry Brummell]

Try doing a search for "Quake", there's a huge thread from last month that dealt with this very issue.

Terry

[Trevor Drake-Brockman]

Trevor Drake-Brockman wrote:
>
> Anyone have any success in running a game server under Mitel
> ???
>
> Need help in setting up a game server to run SOF2 or Quake.

Thanks I will see if it helps resolve the problems.

[Adam Hampton]

All I can say is I have had great experience with this package for hosting games

[Trevor Drake-Brockman]

Adam Hampton wrote:
>
> All I can say is I have had great experience with this
> package for hosting games

What games have you run as server?
What ports did you open ??

[Holger]

I had Return To Castle Wolfenstein running on my server - no problems
used 32MB and hardly any of my cpu - 10% or something of the 300MHz
I made a list of what I did if you're intrested....
I believe quake is pretty much the same.

[Trevor Drake-Brockman]

Holger wrote:
>
> I had Return To Castle Wolfenstein running on my server - no
> problems
> used 32MB and hardly any of my cpu - 10% or something of the
> 300MHz
> I made a list of what I did if you're intrested....
> I believe quake is pretty much the same.

When you say you had Castle Wolfenstein running do you mean a LAN game or a server visible to the Interent.  As I can get most games to run over the local LAN but problem is trying to make them visible on the Internet.

Yes very interested in your notes could you post on this board or email me directly on trevor@tdb.com.au

Thanks

[Holger]

If you poke a hole in your firewall it will be both on LAN and internet

ipchains -A input -p udp -s 0/0 27960 -j ACCEPT
ipchains -A input -p udp -s 0/0 27950 -j ACCEPT

Should do the trick if you use the standard ports

And assuming you have all of the dedicated server stuff installed.

nohup wolfded +set com_hunkmegs 64 +set sv_maxrate 9000 +set com_zonemegs 32 +set dedicated 2 +set sv_hostname "-- your cool hostname --"  +exec rotate.cfg +vstr m_rotate1

hope this helps!

[Holger]

and some more ressources:
# http://zerowing.idsoftware.com/linux/wolf/QUICKSTART
# http://zerowing.idsoftware.com/linux/wolf/
# http://cyber-euskadi.com/howtos/Howto-Install-Unreal-Tournament-Server-on-SME-5.1.2.htm
# http://www.e-smith.org/docs/howto/contrib/final-cstrike-howto.html

[Trevor Drake-Brockman]

Holger wrote:
>
> If you poke a hole in your firewall it will be both on LAN
> and internet
>
> ipchains -A input -p udp -s 0/0 27960 -j ACCEPT
> ipchains -A input -p udp -s 0/0 27950 -j ACCEPT
>
> Should do the trick if you use the standard ports
>
> And assuming you have all of the dedicated server stuff
> installed.
>
> nohup wolfded +set com_hunkmegs 64 +set sv_maxrate 9000 +set
> com_zonemegs 32 +set dedicated 2 +set sv_hostname "-- your
> cool hostname --"  +exec rotate.cfg +vstr m_rotate1
>
> hope this helps!


Thanks Holger, I will give this a try later.  Just one question why are the two ipchains lines exactly the same?

Thanks

[Charlie Brady]

Trevor Drake-Brockman wrote:

> > ipchains -A input -p udp -s 0/0 27960 -j ACCEPT
> > ipchains -A input -p udp -s 0/0 27950 -j ACCEPT
...
> Thanks Holger, I will give this a try later.  Just one
> question why are the two ipchains lines exactly the same?

They're not

The question remains as to what they are intended to achieve. You really want to protect services, and services usually listen on particular ports. If you accept inbound packets based on their source port, then you open up attack to any of your ports which you wish to protect.

If Holger had intended to allow inbound UDP packets directed to ports 27950 and 27960 then he should use -d. However that's not actually required, as inbound UDP packets are blocked only if directed to ports less than 1025. (This will change with the next release, where the packet firewall is implemented with the 2.4 kernel's netfilter/iptables. The connection tracking feature of netfilter allows all packets to be blocked, except those related to an active outbound connection or with an open service).

Regards

Charlie

[Holger]

> Trevor Drake-Brockman wrote:
>
> > > ipchains -A input -p udp -s 0/0 27960 -j ACCEPT
> > > ipchains -A input -p udp -s 0/0 27950 -j ACCEPT
> ...
> > Thanks Holger, I will give this a try later.  Just one
> > question why are the two ipchains lines exactly the same?
>
> They're not

> If Holger had intended to allow inbound UDP packets directed to ports 27950
> and 27960 then he should use -d. However that's not actually required, as
> inbound UDP packets are blocked only if directed to ports less than 1025.
> (This will change with the next release, where the packet firewall is
> implemented with the 2.4 kernel's netfilter/iptables. The connection
> tracking feature of netfilter allows all packets to be blocked, except those
> related to an active outbound connection or with an open service).

I stand corrected!  

I think you (Charlie) are right - maybe it just works with no modification. It's been a while since I ran that configuration, so I
can't really test it for you Trevor.

We're all looking forward to 2.4 especially because of iptables.

Regards

Holger