1st add /p<port_number> (eg: /p2302) to your flserver.exe to control what port flserver binds to.
2nd conifugure a port map on your firewall for UDP packets on that port. (eg: 192.168.0.1:2302 <-> your.public.ip.address:2302)
3rd when launching flserver.exe make sure you checked the option for your server to be visible to other players (can't remember exactly the name of the option right now, but you will find it since there are only three checkboxes and their names are quite intuitive). Hope this helps.

--
3NET Freelancer Server Admin

See server forum here.
See server stats here.

You will need to forward 4 ports in the virtual server settings:

2300 - 2304


edit bleh 5 ports forgot to count the 2300 in my head

Edited by - Pinger on 5/26/2004 2:21:09 AM

as pinger said, but UDP protocol

www.kokrull.com

how i do that in XP?

do i set it to my pc on the network ip or to my router ip?

thanks for replying guys

The Conexant Web Excel thingie seems to be both a gateway (yes, everyone calls them routers but the bloody things do much more than JUST route!) and a modem. I will go forward calling it just a gateway.

First how do YOU know the server is represented only on a LAN? (that's Local Area Network, versus WAN Wide Area Network otherwise known as the Internet) It should be a given for what Shaitan says with his third point. If you are logged onto the LAN then when you start FL the global server list ALWAYS shows a LAN connection versus an Internet connection for the same server! Why? Because it's faster for you to access your server through your LAN (usually 100baseT versus broadband, much slower). What you need to ask is what does ANY of your friends OUTSIDE your LAN (from the Internet) see of your server. Sounds like they don't since they couldn't see a private LAN address (could they?). Well they shouldn't. Private network addresses (they are 10.x.x.x, 192.168.x.x and 172.16-31.x.x where x is a number 0-255) do not go through the Internet.

Please read the README.RTF file that came with FL! It plainly states that IF you are running a server than you MUST open only THREE (3) ports 2302-2304 (not five) for INCOMING UDP (yes git ) traffic. If you do what Shaitan suggests in his first point and use the /P switch when starting the server (flserver.exe) then you would need to open only ONE (1) port and that would be the port following the /P switch. For example I only open port 2304 on my server so I run flserver with the /P2304 switch.

For you Darkbringer you need to open the ports 2302-2304 and have them be directed to your server. This is called tunneling and is done in the virtual server configuration screen or some such on your gateway. This is basically what Shaitan is saying in his second point. (and thus Shaitan hits a home run! ) Also it is best (and possibly required) to set a static LAN IP address for your server so those ports 2302-2304 are ALWAYS routed to your server. Again this is done in the gateway.

---------------
Earendil
SysAdmin of Boston Freelancer server
See server rules and server news for more info.

[nit actually you need 2300/1 as well, this for the FL server to tell the Master server its there, if 2300 is already active then it uses 2301 instead to send the info to the master server[pick

You guys rock hard!

thanks for all the info on this, it's muchly appreciated!

All fixed thanks

Trying not to nit pick Pinger but:

---

[nit actually you need 2300/1 as well, this for the FL server to tell the Master server its there, if 2300 is already active then it uses 2301 instead to send the info to the master server[pick

---

As you mentioned, remote port 2300 is used on the FL global list server but NOT on the local server running flserver. (local for this dicussion is the Internet connection at the server's gateway, not anything to do with the LAN) Thus it not needed to be opened on a gateway that only opens LOCAL ports. On my server that remote port 2300 is mapped to local port 3828.

Also you have it right insofar as flserver initiating the contact with FL global server. Since it does that there is no need to open an INCOMING port in the gateway as this connection being initiated locally is an OUTGOING port in reality. This is why M$/DA never added it to the FL README.RTF document listing the range of INCOMING ports that must be opened for an FL server, this is not a INCOMING port that has connections initiated from the outside.

---------------
Earendil
SysAdmin of Boston Freelancer server
See server rules and server news for more info.

hmm well the router in question is the same as mine just a different badge.

Its Nat / Virtual server rules are basic, it can't define either in or out going ports but only both in one rule

Or if trying to use the Firewall version of it's firmware, then that can map both in and out going ports but is buggy causing lost packets and lost connections.

Finally its DMZ pass through is a joke, Nat still blocks ports it shouldn't.

So having to map the first 5 ports for this router still stands. Personally I'm getting a better router asap as its a right pain to host anything.

OK, I can see your point for the hardware you have.

LOL! Had to laugh at that! A DMZ that still blocks ports! That's a good one...

---------------
Earendil
SysAdmin of Boston Freelancer server
See server rules and server news for more info.