CSGO Dedicated Server Connectivity: Remote Works; Inside LAN disconnects

All Discussions > Tools & Servers > Source Dedicated Server (Linux) > Topic Details

<johnny>bravo 22 May, 2020 @ 4:48am

Stood up a CSGO dedicated server in an Ubuntu container. Server key generated, firewall and NAT rules connect just fun (no logs indicating drops). connects great when connecting from the outside. For example, cell phone hot-spot. Take the same computer, connect on the internal network, and connectivity fails. Resets to the main menu from the client side.

sv_lan 0 is setup
Gameserver logs into steam and receives identity
VAC Secure mode is noted with a server id
Attempted to use the container referenced by steam community server guide, custom built ontop of core ubuntu, and native ubuntu install all with the same experience.
Internal connectivity has been tested on different subnet as well as on the same subnet.
Address space is within reserved address spaces, but not RFC1918. 198.18.x.x

Summary for later searches:
Connectivity from outside is successful, however internal fails

< >

Showing 1-15 of 15 comments

Blaquicat 22 May, 2020 @ 6:42am

probably a loopback issue.

Are you trying to connect using the external ip or the internal ip?

<johnny>bravo 22 May, 2020 @ 7:14am

Thanks for the though. Attempt to connect via internal ip internall, external ip externally. DNS can resolve to the correct IP both internally and externally.

[N]ebsun 22 May, 2020 @ 7:19am

what port - does nat translate to a different port from outside?
have you used -ip in the command line config? try using -ip 0.0.0.0

Blaquicat 22 May, 2020 @ 7:30am

Originally posted by <johnny>bravo:
Thanks for the though. Attempt to connect via internal ip internall, external ip externally. DNS can resolve to the correct IP both internally and externally.

DNS does not resolve ip, as its function is to resolve names into ips..
Try this:

Originally posted by Nebsun:
have you used -ip in the command line config? try using -ip 0.0.0.0

You can try with your internal ip or 0.0.0.0, most people 0 works, for me i had to put the internal ip..

./srcds_run -maxplayers 12 -ip 192.168.0.10 -port 25595 -game csgo -console -usercon +game_type 1 +game_mode 0 +mapgroup mg_armsrace +map ar_shoots +sv_setsteamaccount *IDHERE* -net_port_try 1

like that..

Last edited by Blaquicat; 22 May, 2020 @ 7:31am

<johnny>bravo 22 May, 2020 @ 9:00am

Thanks for the continued thoughts.

I can attempt 0.0.0.0 for the -ip setting, but seems that is only beneficial to binding within a multiple interfaced server (not the case here). It currently is using the internal IP address (198.18.2.100) with the +net_public_adr being the DNS entry.

NAT is being used only from external connection (which are successful), but port 27015 is not being altered. Upon connecting internally, the firewall shows the UDP packets passed.

Blaquicat 22 May, 2020 @ 9:31am

Originally posted by <johnny>bravo:
Thanks for the continued thoughts.

I can attempt 0.0.0.0 for the -ip setting, but seems that is only beneficial to binding within a multiple interfaced server (not the case here). It currently is using the internal IP address (198.18.2.100) with the +net_public_adr being the DNS entry.

NAT is being used only from external connection (which are successful), but port 27015 is not being altered. Upon connecting internally, the firewall shows the UDP packets passed.

According to the cs go cvars page, +net_public_adr is supposed to be your external ip.

net_public_adr 0 For servers behind NAT/DHCP meant to be exposed to the public internet, this is the public facing ip address string: ('x.x.x.x')

[N]ebsun 22 May, 2020 @ 11:08am

Originally posted by <johnny>bravo:
Thanks for the continued thoughts.

I can attempt 0.0.0.0 for the -ip setting, but seems that is only beneficial to binding within a multiple interfaced server (not the case here). It currently is using the internal IP address (198.18.2.100) with the +net_public_adr being the DNS entry.

NAT is being used only from external connection (which are successful), but port 27015 is not being altered. Upon connecting internally, the firewall shows the UDP packets passed.

Not sure why you would need to specify a DNS entry to the game command line..
DNS just resolves domain names to ip addresses, so if you had a domain "example.com" pointing to the public ip of your game server, you can use "connect example.com:port" in game to connect (or just example.com if using default ports). It's not something you should need to specify on the game server itself - and I don't think this would be resolved by the game server either

0.0.0.0 ip is useful if you don't care what ip or interface your server really uses, so if you add another interface or changed the ip in the future all you would need to update would be the nat ports.

Last edited by [N]ebsun; 22 May, 2020 @ 11:10am

<johnny>bravo 22 May, 2020 @ 7:38pm

From previous testing, the dns name as the +net_public_addr would be entered into the "save as a favorite" so if i ever changed IP's, the dns could be maintained. This keeps the representation of your server should you switch providers or your service provider change IP's.it has been a few years (2016?) since my last server hosting when this was used.

After switching out to my public ip, no success for LAN connectivity.

thanks for reading still :)

<johnny>bravo 22 May, 2020 @ 7:42pm

through testing, i have added the sv_region and +clientport with no success. Below is the launch script for reference. Thanks for the continued input!

cat serverlaunch.sh
#!/bin/bash

/home/steam/csgo-dedicated/csgo/./srcds_run -game csgo -tickrate 128 -port 27015 -condebug -usercon +game_type 0 +game_mode 1 +sv_setsteamaccount <topsecret> -net_port_try 1 +mapgroup mg_active +map de_dust2 +ip <internal ip> +net_public_adr <external IP or DNS> +sv_region 0 +clientport 27005

Last edited by <johnny>bravo; 23 May, 2020 @ 5:17am

Blaquicat 22 May, 2020 @ 8:55pm

Originally posted by <johnny>bravo:
From previous testing, the dns name as the +net_public_addr would be entered into the "save as a favorite" so if i ever changed IP's, the dns could be maintained. This keeps the representation of your server should you switch providers or your service provider change IP's.it has been a few years (2016?) since my last server hosting when this was used.

After switching out to my public ip, no success for LAN connectivity.

thanks for reading still :)

Does not make any sense putting the DNS there, you dont even need dns to play on most servers, as they dont have names..
You need for browsing..

+clientport this dont do anything on the server side, you can remove.

Last edited by Blaquicat; 22 May, 2020 @ 8:56pm

#10

THE ONE AND ONLY 9 Jun, 2020 @ 10:15am

...

#11

<johnny>bravo 24 Jul, 2020 @ 2:02pm

Solved:

Steam / CSGO does not support RFC5735. As soon as the internal addressing (198.18.0.0/15 range) was moved to a RFC1918 address (192.168.0.0/16 range), the server was accessible.

Thanks!

#12

Aaaa 24 Sep, 2020 @ 7:50am

it's not supported

#13

irem 12 Oct, 2020 @ 12:41pm

what port - does nat translate to a different port from outside?
have you used -ip in the command line config? try using -ip 0.0.0.0

#14

<johnny>bravo 18 Oct, 2020 @ 5:56pm

Outside worked fine due to NAT. It is not a steam server issue, but a steam client issue. If the client resolves from the outside the public IP and connects via the public IP, it is unaware of the NAT. Internal clients would break as there is no NAT involved, resolving directly to the 198.18.0.0/15 address.

#15

< >

Showing 1-15 of 15 comments

Per page: 1530 50

All Discussions > Tools & Servers > Source Dedicated Server (Linux) > Topic Details

Date Posted: 22 May, 2020 @ 4:48am

Posts: 15

Start a New Discussion