Bill Marquette wrote:
On 1/27/06, Adam Gibson <[EMAIL PROTECTED]> wrote:
I need quake4 UDP master server updates to try and keep the real source
port when going through NAT. The master servers use the src port that
they receive when listing your server. I noticed that pf does support
that capability through the static-port option but I do not see a way of
adding that to the pfsense rules.
I read somewhere in the pfsense discussions that this might be a 1.0
Beta2 feature addition. I am currently testing the 20060125 snapshot
and do not see an obvious feature addition for that. Anyone know if
this will be added sometime in the future?
It's in outbound nat. You'll have to create an advanced rule for this.
Thanks for the direction. I found the static-port setting. Someone has
probably already noticed the bug but the NAT listing does not display
properly for the rule I just created(the fields are in the wrong spot in
the table but editing the rule looks like it is setup correctly). I
wont be able to test it until later tonight. This is the xml that was
generated. The UDP packets in question that originate from the OPT1
network are src=192.168.1.140 srcport=28004 dst=192.246.40.28
dstport=27650 .
<rule>
<source>
<network>192.168.1.140/32</network>
</source>
<sourceport>28004</sourceport>
<descr>Attempt to keep quake4 server src port on the SVC network
static through NAT for q4master updates</descr>
<target/>
<interface>wan</interface>
<staticnatport/>
<destination>
<any/>
</destination>
<natport>28004</natport>
<dstport>27650</dstport>
</rule>
