[ previous ] [ next ] [ threads ]
 
 From:  "gummy" <gummy at dgwarp dot is dash a dash geek dot org>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Game server port forwarding and UDP source port mismatch
 Date:  Thu, 27 Jan 2005 11:55:42 +0100 
Hello,
Just a simple question for you fw gurus  

I have a linux server hosting a Sof2 server (192.168.5.250). I have a NAT
rule to translate WAN:20100 to 192.168.5.250:20100. So joining the server
from the outside is not a problem, if you have the WAN address. But
it seems that game server browsers use the port number the udp packet is
originated from.
Ex :

from 192.168.5.250 to monowall, the packet come from port 20100.
Then Monowall sends the packet to master.sof2.ravensoft.com, but the packet
coming from monowall now come from port, say, 64216.
master.sof2.ravensoft.com receive the packet, and try to connect to
monowall:64216 instead of monowall:20100 ...

So, is there a mean to specify that all trafic coming from
192.168.5.250:20100 must be nated to monowall:20100 ?
I know that this implies a reserved port on the WAN side of monowall, and
that only one LAN computer could be nated for each reserved port, but is
this possible ?

I mean, without DMZing the server ?

Thank you,

Jeremy Longo