Sorry! Been in (still in
) NYC and have had little time for remote sysadmining and monitoring my website let alone all those other FL forums. I have left you off to your own! I will try to make it up for you.
First, that first picture you showed is the perfect screen to redirect your FL client port. Just place port 2303 in BOTH under the Triggered Range column to have "2303 to 2303" range. On the same line under the Forwarded Range just put anything else, like "202303 to 202303" for example. In this case there is no range because there is only one port. Chances are you won't pick a port already used but if you are worried try it or get a program that determines all the ports FL client uses like the DiamondCS Port Explorer.
Esquilax is right, uPnP is not what you want. uPnP is an automatic way of opening INCOMING ports and FL client uses none of those.
Yes, I have heard of people using gateways as simply routers. This is what you are doing for one of your gateways. You must simply pick one of the two gateways to BE the gateway. Seems like you've done this.
I would suggest you call one gateway and the other a router so you could keep them seperate!
Any program, like FL client, that does not need an INCOMING port but needs to transmit data over ports in both directions does it by OUTGOING first! See in the gateway the NAT server (firewall) knows you are sending something out, say a request through your browser (usually port 80) for M$'s home page. The firewall then knows something will come back through that port from M$'s home page so it keeps that info in memory until the webpage comes through. The connection INCOMING couldn't have been made without an OUTGOING request first, hence this port is an OUTGOING port. The firewall is set to believe anything you, on the LAN side, ask for in the WAN (Internet) is OK. Obviously what is NOT OK is anything unasked for INCOMING from the WAN side. The exception are programs like an FL server which has one INCOMING port open for all you FL clients logging into that server. This is still secure though because if the program the firewall is directing all INCOMING data to (that program is of course flserver.exe, the FL server) doesn't recognize the data (say a hack), it discards it!
Darcmarc, FL client should be using the DirectPlay ports of DirectX. The clue as Stinger says is in the Readme.RTF file in the Freelancer directory, ports 2302 to 2304. Since you cannot (not legal), should not (know assembly language?) and I certainly would not mess with the executable and change ports that way, simply use the redirect port method I mention earlier in your gateway.
Did I miss anything?
_____________
Earendil
SysAdmin of Boston Freelancer server
Server community website & forum:
EarendilsPlace.net (
server rules)