Is there any way for the server to tell the client that his ports arent forwarded properly? Seems like that feature would be nice too.
I've been toying with the idea of the FS2NetD server doing a trace to the proper game port on the client side and if a connection/response doesn't pan out, to notify the user via a popup (via the already established FS2NetD connection) that there is a problem. Of course, this all assumes that the user setup the port properly to connect to FS2NetD in the first place (which if they didn't do with the new code, it will boot them back to the mainhall anyway).
The big problem with the idea is that it will only check the standard port, and if they aren't then it's either a useless message, or we have to force use of only the standard port and that idea sucks too.
And even bigger problem is that, though this would be a perfect thing to get into the new FS2NetD code, I'm so behind on it right now that it's time to cut my losses and get it tested. It's either as feature complete as it is going to get, or it doesn't get into 3.6.9. And that assumes that there aren't too many bugs in the new code since if there are, regardless of how needed the new code might be, it just isn't going to make it. 3.6.9 ships at the end of this month, no more excuses, and there is still a lot of other things to do before then.