Announcement

Collapse
No announcement yet.

Linux dedicated server issues.

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Linux dedicated server issues.

    Is anyone using a Cisco ASA and watching logs. I have forwarded/allowed the three Ports everyone talks about. I have been watching the logs there is a ICMP being blocked, whois does not show any significants of the owning
    destination. I have modified the UTGame.ini and well just about every other. I am patched with the latest for Linux. I disabled the OS firewall. I checked the Host file which looks correct(local IP with host name). I have a successful Windows server, which is not behind the same firewall. I can connect to the server w/open. . . . :

    Any Ideas.. also one more question. My command line is as short as I can get it I think. How do I lose the "Cut down URL"?

    Thanks
    Kulaa
    Tags: None
    #2
    Does it appear in the browser at all?

    Does your Cisco do filtering on outbound traffic? Exactly which local address does your host file contain for your hostname (not localhost)?

    "Cut down URL"?

    Comment

      #3
      example

      Code:
      ScriptLog: Cut down URL ?Name=Player?team=255?bIsDedicated=True?bShouldAdvertise=True?PureServer=1?bIsLanMatch=False?ServerDescription=119000119000119000046000099000108000097000110000100000105000101000046000099000108000097000110000115000046000112000108000

      Comment

        #4
        The Cisco Firewall blocks Blocks everything! As this server is hosted at work, we are watching the logs on both sides and the ICMP is the only thing still being blocked. I have not opened it as the IP destination seems to change.

        The host file contains 127.0.0.1 and 10.90. . . inside address w/actual host name. It will not show in browser.

        As bobekk stated, mine is similar but I do not have the server description listed, as with the latest patch its not needed, if I am correct.

        Comment

          #5
          Originally posted by NoNameAirman View Post
          The Cisco Firewall blocks Blocks everything! As this server is hosted at work, we are watching the logs on both sides and the ICMP is the only thing still being blocked. I have not opened it as the IP destination seems to change.
          I take it you have opened ports as you saw hits in the logs then?

          If not I would suggest that you verify that you can use the server login/password to login with the client and be verified. It seems only accounts created through the client work, i.e. not from other games, web page etc.

          Otherwise, what ICMP is being blocked and what ports did you open for what protocol and in which direction? In my experience the minimal ports required to forward is the game port (UDP, incoming) and the two master list ports (27900 and 29900, TCP/UDP outgoing) but I haven't dug into it for lack of time.

          Originally posted by NoNameAirman View Post
          The host file contains 127.0.0.1 and 10.90. . . inside address w/actual host name. It will not show in browser.
          That should be enough, but you might want to check that it bound the query port (6500/UDP) to this IP, or 0.0.0.0. The code is a bit braindead in this respect. :P

          Originally posted by NoNameAirman View Post
          As bobekk stated, mine is similar but I do not have the server description listed, as with the latest patch its not needed, if I am correct.
          I have no idea about that, I don't have it in my 1.1 server log (I haven't tried 1.2 yet).

          Comment

            #6
            Ports have been opened as they are hit, except the ICMP. The problem w/ the IMCP, they are not going to the same address nor are they the same ports.

            Ports opened so far 7777, 6500, 13000, and I will post more later. There were numerous that I can not remember.

            Comment

              #7
              Ok watching the logs more | more and over and over. The Windows server looks for 27900 and 29900 as NakedApe stated, the Linux server does not seem to look for the same. I will be putting it in a DMZ tonight to test.

              Does anyone else have any ideas?

              Comment

                #8
                The Windows UT3 server is showing in the browser now, I can not say the same for Linux. All I can do is reread the setup again and see if I missed anything.

                Ports 29910/UDP, 27900/TCP have been forwarded for both. I am not seeing the Linux box talking to 27900/TCP, which then allowed Windows to be seen.

                Comment

                  #9
                  What did you get from
                  Code:
                  netstat -nul
                  regarding port 6500 primarily?

                  Comment

                    #10
                    Router setups can vary. Sometime port forwarding has the ports to forward as ranges and some have as a source to destination. That got me on my actiontech for a couple of hours. The source should be blank or any. This may or may not be applicable depending on the router. just something to check.

                    Comment

                      #11
                      Ok, everything is fixed as of 10:30 last night. I will post the ports needed later. It is as secure as it can be. There are a few destination IPs with specific ports, and the obvious ports everyone knows about. It is a lot easier to put servers in a DMZ, but where is the fun in that(oh yeah you get to play faster).

                      alright I will post the ports later. One thing I remember is that UDP over 6500 is not valid until there is jump start to 207.38.11.34:27900 TCP.

                      Comment

                      Previous template Next
                      Working...
                      X