Page 2 - Routing with SUSE 8.0

Thx, but was that reminder really necessary? I've got to go back to school tomorrow

I don't know BattleCom well enough to be sure (I've never used it), but summed up:
- You should have routing enabled (that's what you wanted so it probably is).
- The firewall should allow outgoing traffic on TCP port 47624 (it usually will).
- If you want to run a BattleCom server behind the firewall, you must forward the requests on port 47624 to your server. Since that is quite a breach of security, you should limit the forwarding to the IPs of the players who'll be coming in from the internet:

(If 123.45.67.8 is the client outside the firewall and 192.168.0.2 in your LAN runs the BattleCom server. If you wanted to allow access for anyone (unless BattleCom has reliable authentication, you should not do that), the first IP would be 0.0.0.0)
- In any case, you must forward comms on TCP and UDP ports 2300-2400. Make sure that you have no other services running behing the firewall which listen on these ports and that you do not offer any service on the firewall inside the range. Untested example (I'm not sure about the syntax) which would allow BattleCom connections from 192.168.0.2 to 123.45.67.8:

(If you also want to run a server, add the value given above to these two, separated by a space.)

General notes:
1. Backup your firewall config before doing anything.
2. Allowing incoming traffic is always a risk. If BattleCom is not regularly used (for connections to the internet) on your LAN, you should consider making a separate config file for the BattleCom rules and only starting the firewall with that rules when necessary. (However, that's a lot of work.)
3. You should run a firewall on 192.168.0.2 (replace by the address you use for the rules). (I recommend ZoneAlarm.) Grant server rights to the BattleCom software and deny these rights to everything else (unless needed).

I've taken my info from a BattleCom site, you should read it too: http://www.battlecom.org/proxyfirewalls.html

HTH (However, I have not tested any of the above. Most likely you'll have to change it or do (additionally) something else to get the thing working. There seems to be no record on Google of how to do this, so write down your steps and if you succeed publish the method (e. g. ask the people at battlecom.org to put it on their site).)

Hmmm. Thanks for YOUR work. So I think this one should have worked:

FW_FORWARD_MASQ="62.80.111.253,192.168.0.2/3,udp,2300:2400 62.80.111.253,192.168.0.2/3,tcp,2300:2400 62.80.111.253,192.168.0.2/3,udp,47624 62.80.111.253,192.168.0.2/3,tcp,47624 62.80.111.253,192.168.0.2/3,tcp,28800:28900 62.80.111.253,192.168.0.2/3,udp,28800:28900"

because that where the port descriptions i found. But it doesn't.

62.80.111.253 is the static ip BC server we want to connect to.
But if we try connecting with the settings above, bc returns an error "could not find a server at that adress" even though it is for sure that there are BC servers

My intention with these setting is that 192.168.0.2 + 192.168.0.3 could use BattleCom ist that the right syntax or are there any other errors ?

Try it for just one IP, i. e. remove the /3 from 192.168.0.2/3. (Maybe it can somehow work for multiple IPs, but I'm not sure how that would be done.)