Spaztic_One
Refugee
Dedicated A18.3 (b4) running on same computer as client
Ubuntu 18.04.1 (kernel 5.3.0-26-generic #28~18.04.1-Ubuntu SMP)
CPU: Ryzen 3700X
RAM: 64 GB
GPU: nVidia 1080 - 8 GB - Driver Version: 435.21
Client and Server logs
Server is configured to run on 26900 (forwarded tcp and udp on my router) and I can connect via loopback without issue, but my friend as of version 18.3 could not connect by my public IP. This was working before the upgrade on 18.2 fine. I was foolishly using the default file name serverconfig.xml for the dedicated server and when the 18.3 update rolled out, it overwrote my configs without backing up the file(!). I've reset the configs as best as I can remember and I was playing fine using loopback on 26900.
Now after a lot of poking around on the forums, dedicated server config guides here and there, looking at my system's `ss -natup` output and both my client and server logs, I determined that the clients are trying to connect via 26902 for some reason. I did a port range forward of 26900-26902 and was able to connect via my public IP, and then for the sake of curiosity I set the forward to 26902 ONLY and even though the server is running on 26900 and I told the client to connect on 26900, I was able to connect to my dedicated server via public IP.
Is this intended behavior? Is it documented anywhere other than the Valve link above? Just going off of the serverconfig.xml and my experience with 18.2, when you set ServerPort that should be the only port that is used.
Ubuntu 18.04.1 (kernel 5.3.0-26-generic #28~18.04.1-Ubuntu SMP)
CPU: Ryzen 3700X
RAM: 64 GB
GPU: nVidia 1080 - 8 GB - Driver Version: 435.21
Client and Server logs
Server is configured to run on 26900 (forwarded tcp and udp on my router) and I can connect via loopback without issue, but my friend as of version 18.3 could not connect by my public IP. This was working before the upgrade on 18.2 fine. I was foolishly using the default file name serverconfig.xml for the dedicated server and when the 18.3 update rolled out, it overwrote my configs without backing up the file(!). I've reset the configs as best as I can remember and I was playing fine using loopback on 26900.
Now after a lot of poking around on the forums, dedicated server config guides here and there, looking at my system's `ss -natup` output and both my client and server logs, I determined that the clients are trying to connect via 26902 for some reason. I did a port range forward of 26900-26902 and was able to connect via my public IP, and then for the sake of curiosity I set the forward to 26902 ONLY and even though the server is running on 26900 and I told the client to connect on 26900, I was able to connect to my dedicated server via public IP.
Is this intended behavior? Is it documented anywhere other than the Valve link above? Just going off of the serverconfig.xml and my experience with 18.2, when you set ServerPort that should be the only port that is used.
