Instead of responding to each of the various threads on this...

We found and fixed a bug in the master server last night about 9pm CDT that should fix servers not getting listed. The issue was a server only got listed if a game client connected to it. Once that happened, it stayed listed as long as it was up (or at least as long as the master server stayed up).  

Now, I know some people are going to say - "But I can't see my own server". So, here is a bit more info...

For a server to get listed in the game, 4 things need to take place.
1) Game server needs to send a heartbeat to the master
2) Master now sends 3 different requests to the game server
3) Game server needs to respond to all three, if it does, it gets "listed" on the master
4) The game server needs to respond to a getinfo request from a game client.

Item #4 can cause issues when trying to view your own server in the in-game list, usually when both the server and client are behind the same NAT device.

So, now a NAT primer time to explain what I mean...

Setup:
 NAT box:
   Wan IP (assigned by the ISP)  1.1.1.1
   Local LAN IP: 192.168.0.1
 Game Server IP: 192.168.0.5
 Game Client IP: 192.168.0.10

So, Game server listens on port 20100 by default. It sends a heartbeat to the master. The NAT device will change the IP packet to look like it came from 1.1.1.1:xxxx where xxxx is some semi-random looking port number. Because every client on the local LAN could be using port 20100, the NAT device needs to know which one to send data back to if it gets an IP packet from "somewhere" on the internet. So, if each client used 20100, the world would see each one as some port other than 20100...

Anyway, to explain item #4, The client at 192.168.0.10 queries the master for a list of game servers. One of them will be 1.1.1.1:xxxx. The client now sends a packet to 1.1.1.1:xxxx to "getinfo" about the server and its ping. This packet gets sent to 192.168.0.1 first. The NAT device looks at it and does one of two things:

1) Decides that this packet is meant for it as it is also the IP address 1.1.1.1. Many NAT devices now discard the packet thinking that it was meant for it, and it doesn't know what to do with the packet.

2) NAT device is a bit friendlier and forwards the packet on to 192.168.0.5:20100

If your NAT device does the first thing, the game client then does not get a response from the game server. It figures that the Master server just gave it old data and that game server is no longer running and doesn't show it in the list.

If that is the case, you just need to connect to it via the Local LAN setting.

Direct technical support from Raven is greatly appreciated....unlike many companies that depend on users supplying support it is very rewarding to see one that actually cares enough about customers to directly supply support to help fix problems. Raven Rules!!!!!!

I agree.  This is fantastic news and fantastic info!  Thanks to all at Raven for finding and fixing the bug, as well as providing a detailed technical explanation as to why it was happening (as well as the surrounding other issues involved) and how it was all fixed.

Additional note: Most routers today support the "loopback" function, which allows one to go out to the internet and back in (connect to the router's external IP). Without this function (as I recall), servers hosted behind a router wouldn't show up in one's own internet server list. Those that do not support this function can usually be fixed with a firmware upgrade. The Linksys I have did not support this at first; it was fixed in a later firmware, as was the problem with booting clients off game servers.

Let me add my thanks. Appreciate the support

duck

Let me also say thanks!!! Thanks Guys!!!

Yes thank you very much.  I've learned a lot here already, much of if from Raven employees

Thank you Bryan, Vorik (whoever you are), and all RAVEN.
Ozan-SilentBob-OZ

First of all let me say thanks like everyone else, now to my question.

This is in regards to a router that does not use NAT but rather NAPT.  I have some games that allow the user to assign a port number to the client/server. For instance:
(THIS IS A QUESTION, NOT HOW RAVEN DOES IT)

Heartbeat server list could be on 20100
Dedicated Server could be on 20110
Client could be on 20111
Client #2 would be on 20112
after that additional clients would be 20112+1.

This seems to allow most if not all routers to be able to set port mapping parameters without requiring an ALG (Application Layer Gateway). I would think the method above would be better for game developers since there are so many routers available that to the public and so many companies that do not continue to add ALG support to their products when they change models. Such as End of Lifing a product and replacing it with a newer model, most companies just drop support after 12 months or so. Something to do with cost .

Anyway, it woulod be great if SOF2 worked this way, it may but just not published. If you want to look at an example of how a game developer created such a beast then check out www.papy.com for Papyrus's Nascar Racing 4.

Thanks again,
Tkat13
feel free to email me with questions at tkat13@coserv.net

thanks for the incredible support.