Announcement

Collapse
No announcement yet.

SV_ReadClientMessage: NET_GetMessage failed

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

    SV_ReadClientMessage: NET_GetMessage failed

    WELL...I got my linux server up...kinda....

    I start it up with...

    ./sqpro -dedicated 8 -game cax -noipx -condebug -heapsize 32768 -zone 1024 -ip 204.248.57.146 -udpport 26000 +map e1m7

    I then go into Quake, connect to the domain, it says connected, spits out that its a ProQuake server, then after 30 seconds or so, the server console spits out "SV_ReadClientMessage: NET_GetMessage failed"

    If I connect via the IP it says "Network Error"

    I opened port 26000 port but for UDP only, is that a prob? Should it be for TCP also?

    Thanks again guys!
    Tags: None
  • #2
    This the proquake 3.50 server right?

    Lets start simple. Just run the server with no command arguments. Can you connect in that case? If you're running the server on the same box as the client can you connect to 127.0.0.1 ? Quake doesn't do anything with tcp by the way, so only udp is required. Are you possibly having firewall/routing issues which may cause connect errors?
    "If we fight for money I'll stop hitting you when you ask me to. If we fight for honor, I'll stop hitting you when I feel like it." - Rickson Gracie

    Comment

    • #3
      Originally posted by mavness View Post
      I opened port 26000 port but for UDP only, is that a prob? Should it be for TCP also?

      Thanks again guys!
      The main problem you are going to run into is that opening port 26000 by itself isn't enough with ProQuake. ProQuake will want a lot of different ports available because the original Quake protocol uses a lot of different ports at random for some reason.

      The easiest options go like this:

      Option 1: Let ProQuake have unrestricted UDP port access.
      Option 2: Use Yugo2Heck's experimental port 26000-only patch (it's run on a couple of servers for years, but none of the currently busy ones).

      I'm thinking about adding Yugo2Heck's port 26000-only patch into ProQuake 3.99 as a commandline option (not as the default) in the future. This issue reminded me of why I want to have it available for testing.

      The thread on the 26000-only patch is available here:

      http://www.quakeone.com/forums/showthread.php?t=641
      Quakeone.com - Being exactly one-half good and one-half evil has advantages. When a portal opens to the antimatter universe, my opposite is just me with a goatee.

      So while you guys all have to fight your anti-matter counterparts, me and my evil twin will be drinking a beer laughing at you guys ...

      Comment

      • #4
        Darkplaces servers don't have this problem. Just a fyi in case you're interested. Not sure if Darkplaces can host CAx though.

        Comment

        • #5
          Originally posted by Canadian*Sniper View Post
          Darkplaces servers don't have this problem. Just a fyi in case you're interested. Not sure if Darkplaces can host CAx though.
          Unforunately, DarkPlaces cannot run CAx.
          Quakeone.com - Being exactly one-half good and one-half evil has advantages. When a portal opens to the antimatter universe, my opposite is just me with a goatee.

          So while you guys all have to fight your anti-matter counterparts, me and my evil twin will be drinking a beer laughing at you guys ...

          Comment

          • #6
            Originally posted by mithril View Post
            This the proquake 3.50 server right?

            Lets start simple. Just run the server with no command arguments. Can you connect in that case? If you're running the server on the same box as the client can you connect to 127.0.0.1 ? Quake doesn't do anything with tcp by the way, so only udp is required. Are you possibly having firewall/routing issues which may cause connect errors?
            Yeah ProQuake 3.50

            And its not on my machine so I cant connect to local host.

            From what I am reading, I will just setup a secondary box where I can open more UDP ports and not worry.

            What range should I open up? I want to run cax so I guess darkplaces is out of the question for now :\

            Thanks again guys for all the continual help!

            Comment

            • #7
              Originally posted by mavness View Post
              What range should I open up?
              It uses random port numbers, so all of them

              (UDP only. )
              Quakeone.com - Being exactly one-half good and one-half evil has advantages. When a portal opens to the antimatter universe, my opposite is just me with a goatee.

              So while you guys all have to fight your anti-matter counterparts, me and my evil twin will be drinking a beer laughing at you guys ...

              Comment

              • #8
                Originally posted by Baker View Post
                It uses random port numbers, so all of them

                (UDP only. )
                I found this post...
                http://www.quakeone.com/forums/showp...10&postcount=3

                And of course that didnt do squat. I guess I will open up all the UDP and see if that does it for me or not. Kinda crappy but I guess thats what you get with a 12 year old game haha

                Comment

                • #9
                  Yup, opening ALL ports fixed it...what a crappy solution that is :\

                  Oh well, at least I know what I am up against now.

                  Thanks for all the help guys!

                  Comment

                  • #10
                    I'm not 100% on this but I'm sure you don't need to have ports 0-1024 open when hosting a quake server. Those are service ports and shouldn't be open unless absolutely necessary.

                    Comment

                    Previous template Next
                    Working...
                    X