Ports für battelcom und msn, Nur archiv

[Tekbaron]

echo "#####################"
echo "# B A T T E L C O M #"
echo "#####################"
echo " "
$AUTOFW -A -v -r udp 2300 2400 -h 192.168.1.2
$AUTOFW -A -v -r tcp 2300 2400 -h 192.168.1.2
$AUTOFW -A -v -r tcp 47624 47625 -h 192.168.1.2
$AUTOFW -A -v -r udp 47624 47625 -h 192.168.1.2
$AUTOFW -A -v -r udp 28800 28900 -h 192.168.1.2
echo "#########"
echo "# M S N #"
echo "#########"
echo " "
$AUTOFW -A -v -r tcp 1863 1863 -h 192.168.1.2
$AUTOFW -A -v -r tcp 6890 6901 -h 192.168.1.2
$AUTOFW -A -v -r udp 6901 6901 -h 192.168.1.2

[Tekbaron]

A special thanks to those users who wrote in and told us what they did to get this working.


Description
This article describes how to configure IP Masquerade on Linux to allow BattleCom to work through it.


Requirements
You must be familiar with Linux, Linux configuration and configuration of IP Masquerade. You must also have a Linux system with IP Masquerade support.

Issue
How to get BattleCom to work through an IP Masquerade.

Solution - Client
To use BattleCom Client from within a network which is connected to the Internet through an IP Masquerade you must forward the appropriate ports to the PC behind the masquerade.

Step 1: You need to have root or su access.
Step 2: Find the ipmasqadm rpm for ipchains or the ipautofw rpm if you're using ipfwadm and install the RPM (if not already installed... can be found at rpmfind.net)
Step 3: For IP Chains use this command set:

ipmasqadm autofw -A -v -r udp 2300 2400 -h www.xxx.yyy.zzz
ipmasqadm autofw -A -v -r tcp 2300 2400 -h www.xxx.yyy.zzz
ipmasqadm autofw -A -v -r tcp 47624 47624 -h www.xxx.yyy.zzz
ipmasqadm autofw -A -v -r udp 47624 47624 -h www.xxx.yyy.zzz
ipmasqadm autofw -A -v -r udp 28800 28900 -h www.xxx.yyy.zzz

For ipfwadm:

ipautofw -A -v -r udp 2300 2400 -h www.xxx.yyy.zzz
ipautofw -A -v -r tcp 2300 2400 -h www.xxx.yyy.zzz
ipautofw -A -v -r tcp 47624 47624 -h www.xxx.yyy.zzz
ipautofw -A -v -r udp 47624 47624 -h www.xxx.yyy.zzz
ipautofw -A -v -r udp 28800 28900 -h www.xxx.yyy.zzz

You should replace www.xxx.yyy.zzz with the IP Address of the PC behind the masquerade that will be running the BattleCom Client.

For IPTABLES/NETFILTER (2.3.99 kernel):

See http://netfilter.kernelnotes.org on how to get iptables working. Setup a simple NAT for all private IP's on your LAN.

iptables -t nat -A PREROUTING -d xx.xx.xx.xx -p tcp --destination-port 2300:2400 -i eth0 -j DNAT --to yy.yy.yy.yy
iptables -t nat -A PREROUTING -d xx.xx.xx.xx -p udp --destination-port 2300:2400 -i eth0 -j DNAT --to yy.yy.yy.yy
iptables -t nat -A PREROUTING -d xx.xx.xx.xx -p tcp --destination-port 47624 -i eth0 -j DNAT --to yy.yy.yy.yy:47624

Where xx.xx.xx.xx. is the public/external IP address of your firewall, and yy.yy.yy.yy is the local/private IP of the
machine running BattleCom.  Note: only one machine behind the firewall can run BattleCom.
Solution - Server
The same settings will work for the BattleCom Standalone Server. You may even run multiple servers, but they must all reside on the same machine. You may also run a client on the same machine as the one running the server.

Limitations
You will only be able to give ONE PC the ability to communicate with outside clients. This is because of the nature of IP Masquerading and the design of BattleCom. You can however run any combination of standalone servers and clients on that single PC.