TCP/UDP Port mapping - Quake using winded.exe to host

[dhahlen]

I am not sure how to get all of this working, perhaps I do not understand enough about what ports are being used and how quake 1 works over a wan. I am going to post what I've been doing and the problems I am running into. Perhaps someone can help.

I am using winded.exe to run the dedicated server using these commands:

winded.exe -game bombsqd -dedicated 8 -port 26000 -startport 26001 -map hstart

Everything works internally.

When I try to connect externally, I receive this message on the server:

SV_ReadClientMessage: NET_GetMessage failed
Client unconnected removed
SV_ReadClientMessage: client disconnected
Client unconnected removed

The client says "connection accepted", but doesn't load. I assume the server has already dropped the connection, as noted above.

I am running a pix 506e, here is what I've done.

Internal Server IP: 172.17.17.20

I've natted 26000-26009 UDP ports for the server.

static (inside,outside) udp interface 26000 172.17.17.20 26000 netmask 255.255.255.255 0 0
static (inside,outside) udp interface 26001 172.17.17.20 26001 netmask 255.255.255.255 0 0
static (inside,outside) udp interface 26002 172.17.17.20 26002 netmask 255.255.255.255 0 0
static (inside,outside) udp interface 26003 172.17.17.20 26003 netmask 255.255.255.255 0 0
static (inside,outside) udp interface 26004 172.17.17.20 26004 netmask 255.255.255.255 0 0
static (inside,outside) udp interface 26005 172.17.17.20 26005 netmask 255.255.255.255 0 0
static (inside,outside) udp interface 26006 172.17.17.20 26006 netmask 255.255.255.255 0 0
static (inside,outside) udp interface 26007 172.17.17.20 26007 netmask 255.255.255.255 0 0
static (inside,outside) udp interface 26008 172.17.17.20 26008 netmask 255.255.255.255 0 0
static (inside,outside) udp interface 26009 172.17.17.20 26009 netmask 255.255.255.255 0 0

I've set my access-list to temporarily allow all UDP traffic.

I don't mind using something else to host, if someone can point me in the right direction. I am still waiting on the official server files to host the "Da Bomb" mod, but right now I just want to be able to connect to the server externally.

Thanks

[dhahlen]

switched over to wqpro, works using wqpro server/client.

[dhahlen]

blah, stopped working, seems to still be udp issue despite having all udp ports open

[dhahlen]

seems the problem is NAT, i have all ports open but it does not do any good unless there is a nat translation for the port.

26000 works fine, but the random ports are an issue.

[dhahlen]

Ran a netstat -ano

UDP 172.17.17.20:26000 *:* 152

152 is the PID and the UDP port it pulls is

UDP 0.0.0.0:1935 *:* 152

1935

I did a static nat translation for port 1935, still no dice.

Odd thing is, it worked earlier.

[dfsp_spirit]

If your router allows this, you could try setting your Quake server as a DMZ host. This is no long-term solution for security reasons though.

(You gotta be aware that this will expose this host to various attacks from the internet but since you know about netstat -ano I guess you know that by yourself.)

[Baker]

Standard NetQuake uses a ton of ports. You have to have them all open for the server. One method to forward all UDP ports to 26000 on the server side.

Even then, only NAT-fixed can connect without "hacks" or "stupid tricks" due to the NetQuake connection handshake.

[There is a server-side NAT-fix running at quake.ihoc.net by Yugo2Heck since 2003 which does not require a client-side fix. Obviously ports of vanilla Quake like the PSP and Wii favor that server because every port uses buggy standard Quake and inherits the flaw...]

The all inclusive list of NAT-fixed clients = ProQuake 3.4 and above, DarkPlaces since July 2003, JoeQuake 0.14 and above, Qrack, DirectQ (later versions), Tremor (inherited from JoeQuake). There are no other fully NAT-fixed NetQuake clients.

I hope that information helps.

[dhahlen]

Thanks.

I am using ProQuake 4.52, it's odd that it worked and now it doesn't.

I'll try forwarding all UDP ports to 26000

I've opened all UDP ports to the server, and I'm still getting the connection issue:

SV_ReadClientMessage: NET_GetMessage failed
Client unconnected removed
SV_ReadClientMessage: client disconnected
Client unconnected removed

[Baker]

For the moment, try using ancient wqpro.exe 3.50 as the server executable:

ftp://ftp.runequake.com/quake/engine...0/wqpro350.zip

ProQuake 4.52 is beta and has not been exhaustively tested on a server because I'm doing heavy revisions to ProQuake and probably won't do that until version 5.0.

But ProQuake 3.50 has run on servers for 8 years so it can serve a good test case.

Let me know if ProQuake 3.50 as a server has the same issues or if it resolves the problem.

And if it doesn't solve the problem, at least it will be more clear what is going on.

AND also use ProQuake 3.50 as the client for testing your connection.

I didn't notice the 172.*.*.* --- try ProQuake 3.50 and if that works --- it very well may --- I'll then tell you what you need to get 4.52 working as the server (it should be easy if 3.50 works for you).

[dhahlen]

Funny, I had it working with 3.x

I'll swap it now and test out.

Same issue, using 3.50 server and client, same getmessage failed issue

You're more than welcome to check it out....

server is dhahlen.com

Also, if you would like to take a look at the server itself, I can provide RDP access to it.

[Baker]

Try adding -ip x.x.x.x to your command line.

Where x.x.x.x is obviously the ip you want it to bind to.

(Continue using ProQuake 3.50 for now as both client and server. You can switch it to 4.52 after it is running on 3.50 but until you get it running on 3.50 you can't be 100% sure you won't hit some undiscovered server bug in 4.52).

If that still fails, consider at least briefly using DarkPlaces as a server.

http://icculus.org/twilight/darkplaces/

If DarkPlaces somehow runs where ProQuake 3.50 fails, it might be a clue to what is up.

[dhahlen]

Binding does not work either. I have dark places, I'll try that as well.

I tried it with and without the mods...

Trying now...

[dhahlen]

Darkplaces works

[dhahlen]

here is the line i am using to launch darkplaces

darkplaces.exe -dedicated 8 -noipx -ip 172.17.17.20 -condebug -heapsize 32768 -zone 1024 -udpport 26000 +map start

[R00k]

goto your network connection details panel on the machine running the server

look for the ipv4 address ie 192.168.1.100

then in your router config (192.168.1.0), in applications/gaming section, look for port range forwarding, set app to Quake, port range to 26000 - 26666 (for example, protocol UDP, ip address set to the machine thas running the server, ie 192.168.1.100 then [ check ] enable.

This of course is an example setup ising a linksys router.

Edit
-udpport and -port are interchangeable..