Joris,
The "easy" way to port forward on Dachstein is to use Echowall. I
recently
used it to set up Quake and Unreal Tournament servers inside my
firewall.
If you want to just forward specific ports for a specific game, find out 
What ports it uses and create entries for it in /etc/ipchains.forward. 
Charles scripts on "Dach" will load the extra rules and forward the
ports.
A sample that works for Unreal Tournament, Quake II & III and FTP
looks like this below. Just create the file and edit the ip addresses 
to point to your server. The variable $EXTERN_IP/32 should work to pick
up your external interface. 

#Unreal Tournament
$IPCH -A input -s 0/0 -d $EXTERN_IP/32 7777:7781 -p udp -j ACCEPT
$IPCH -A input -s 0/0 -d $EXTERN_IP/32 27900 -p udp -j ACCEPT
$IPCH -A input -s 0/0 -d $EXTERN_IP/32 8080 -p tcp -j ACCEPT

$IPMASQADM autofw -A -r udp 7777 7781 -h 192.168.1.200
$IPMASQADM portfw -a -P udp -L $EXTERN_IP 27900 -R 192.168.1.200 27900
$IPMASQADM portfw -a -P tcp -L $EXTERN_IP 8080 -R 192.168.1.200 8080

#Quake
$IPCH -A input -s 0/0 -d $EXTERN_IP/32 4242 -p tcp -j ACCEPT
$IPCH -A input -s 0/0 -d $EXTERN_IP/32 27901 -p tcp -j ACCEPT
$IPCH -A input -s 0/0 -d $EXTERN_IP/32 27901 -p udp -j ACCEPT
$IPCH -A input -s 0/0 -d $EXTERN_IP/32 27910:27961 -p udp -j ACCEPT
$IPCH -A input -s 0/0 -d $EXTERN_IP/32 27950:27952 -p tcp -j ACCEPT

$IPMASQADM portfw -a -P tcp -L $EXTERN_IP 4242 -R 192.168.1.200 4242
$IPMASQADM portfw -a -P tcp -L $EXTERN_IP 27901 -R 192.168.1.200 27901
$IPMASQADM portfw -a -P udp -L $EXTERN_IP 27901 -R 192.168.1.200 27901
$IPMASQADM autofw -A -r udp 27910 27961 -h 192.168.1.200
$IPMASQADM autofw -A -r tcp 27950 27952 -h 192.168.1.200

#FTP
$IPCH -A input -s 0/0 -d $EXTERN_IP/32 20:21 -p tcp -j ACCEPT

$IPMASQADM portfw -a -P tcp -L $EXTERN_IP 20 -R 192.168.1.200 20
$IPMASQADM portfw -a -P tcp -L $EXTERN_IP 21 -R 192.168.1.200 21
$IPMASQADM autofw -A -r tcp 20 21 -h 192.168.1.200


I hope this helps,

Kory Krofft


Joris Kempen wrote:
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of
> > [EMAIL PROTECTED]
> > Sent: Wednesday, January 09, 2002 5:37 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [Leaf-user] MSN & Gaming
> >
> > You will need to look at the readme file for MSN, you want to
> > find out what ports it wants open on the firewall.
> > Alternatively, you 'MAY' be able to send using a SOCKs proxy
> > (tho, I have never used one) that you would have to setup on
> > you Dachenstein system.
> >
> ok i found the port for this one..
> 
> > Again, this is a ports issue, you will need to find out which
> > ports the game needs open and then open them on the firewall.
> >
> also found the port for this one
> 
> how do i easily open ports in the dachstein router?
> 
> I looked at Charles page and found that I need to edit network.conf
> 
> can this been done from the menu interface.. i guess it can. I think i have
> to hookup my monitor & keyboard again :)
> 
> Can't this been done from one of the client machines??? I read a piece of
> text of using a serial cable to access the router box, can't it been done
> using my utp&hub?
> 
> last thing: to host my own games, i always get the ip-address of my
> localmachine 192.168.1.1 but other people on the internet can't use this IP
> i guess? This is for local networks only, that's what I learned at school :)
> 
> is opening the ports enough for this? what ip-address do people see when
> they ping me, for example from IRC? or can't they ping me?
> 
> other thing: i want to read more about (linux)-firewalls, where to start,
> any documents? I read a book internet for school that included a chapter
> about firewalls, but really basic.
> 
> i want to get more into linux & firewalls.
> 
> thanks for any advice
> 
> gr Joris
> 
> _______________________________________________
> Leaf-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/leaf-user


_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user

Reply via email to