Announcement

Collapse
No announcement yet.

Weird Server Problems - Linux ded svr

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Weird Server Problems - Linux ded svr

    Hello all, I've been beating myself over the head trying to figure this out for nearly a month now, hopefully someone here has an idea of what may be wrong.

    A little background of the problem and what i've already done/tried

    The Problem: Server shows up in server listings, with a ping of N/A and matches are not recorded and scores not sent to the UTStats page. People can still join the server from the server browser however.

    The server itself is a custom built box, 2 ghz, 1 gig ram, not the beefiest of machines but enough to run a 8-10 player vctf server. OS is SUsE linux enterprise, only base packages installed for server, no GUI or X-Server installed. APACHE and PHP4 run alongside UT on the box.

    Now, this server has been up and running for almost 8 months, with no issues until now. Unfortunately the router i had it on before was a royal POC and from time to time would crash, causing everyone to reconnect. Upon renewing my contract with verizon, i made them send me a dsl modem as opposed to the router/modem combo they gave me before. Works great, have it hooked into a Linksys WRT54G which routes it between my wireless devices, and port 1 has a nice little length of CAT5 going to the server.

    DSL connection is Verizon buisness class DSL (static ip)
    Server is static ip on the lan, using an ip that CANNOT be DHCP'd out.
    LAN is secure, Wireless is secure (as wireless can get...) with mac filtering, and WEP enabled. (just ruling out the possibility of an ip conflict)

    Yes, i did forward the ports
    42292
    28902
    7777-7788
    27900

    hell, i've even tried putting it in the DMZ (though that would be a purely temporary solution)

    Needless to say, didn't work.

    My old router, ****ty as it was, forwarded the same ports, and worked fine. Though i suspect as it didn't work in the DMZ it's not a port problem.

    The UT2004.ini file has not changed since my old router. Though for testing, i have both enabled and disabled "Server Behind NAT", neither way works. The master servers are correctly entered in the INI.

    I have to say im compeltely baffled, with the way it it setup, it SHOULD work. Any ideas on what could be wrong, and how to fix it (OTHER than putting my old router back in :P ) are greatly appreciated. I fear i may have already lost what small (but loyal) player base my server had.

    ...sigh...

    ut2004://72.87.203.246

    #2
    Sure sounds like the NAT bug. Search this forum for "NAT bug" for more information on why, how to test and what to do.

    Comment


      #3
      ****! My fear is confirmed, Thanks NakedApe, you tipped me to the right area to look.

      After some research, the specific chipset/firmware combination on my Linksys router has known problems with VOIP which is due to the fact VOIP requires port translation to preserve the source port. This can be fixed by upgrading to third-party firmware available at...
      https://sourceforge.net/projects/wifi-box/
      and
      http://www.sveasoft.com/

      Unfortunately, the hardware version I have (V5) is incompatable and rejects the third party firmware upgrades.

      I am, for all intents and purposes, screwed. Looks like i need a new router. I'll just keep this one as my wireless access point (for wireless and PLAYING the games it's actually been really good, great signal), and set up a 4 port router as my main.

      Thanks for the swift reply

      Comment


        #4
        Originally posted by NickAnton
        After some research, the specific chipset/firmware combination on my Linksys router has known problems with VOIP which is due to the fact VOIP requires port translation to preserve the source port. This can be fixed by upgrading to third-party firmware available at...
        https://sourceforge.net/projects/wifi-box/
        and
        http://www.sveasoft.com/
        Interesting, this confirms what I thought I heard, that there are Linksys routers who do suffer from this bug. Linksys has usually been considered the safe bet as far as the NAT bug goes.

        Comment

        Working...
        X