Quote:
Originally Posted by wickedd
Did you forward your ports?
|
Yes:
Code:
$ sudo iptables -L
Chain INPUT (policy DROP)
target prot opt source destination
[...]
ACCEPT udp -- anywhere anywhere udp dpt:27015
[...]
Quote:
|
Originally Posted by addons_zz
How you are connecting to your server?
|
I am using a Steam client on Windows 8.1.
I am not using the "connect 192.168.0.100:27015" command but I am using the graphical user interface where I can press a button to specify the IP address in a text field.
In this text field, I type 192.168.0.100:27015 but nothing happens after that.
On the server side, I tested also with the 0.0.0.0 IP address as suggested by addons_zz:
Code:
./hlds_run -insecure -game cstrike +maxplayers 32 +ip 0.0.0.0 +port 27015 1>stdout.log 2>stderr.log &
But it does not help.
I am always unable to join my server.
The only difference is on the server side because I see the 0.0.0.0 IP address instead of my public IP address:
Code:
$ cat stdout.log
Auto-restarting the server on crash
Console initialized.
Protocol version 48
Exe version 1.1.2.7/Stdio (cstrike)
Exe build: 13:12:29 Aug 29 2013 (6153)
STEAM Auth Server
Server IP address 0.0.0.0:27015
couldn't exec listip.cfg
couldn't exec banned.cfg
$ cat stderr.log
Using breakpad crash handler
Setting breakpad minidump AppID = 10
Forcing breakpad minidump interfaces to load
Looking up breakpad interfaces from steamclient
Calling BreakpadMiniDumpSystemInit
I also tested that it was not something related to permissions on files:
Code:
$ sudo chmod -R 777 steamcmd/
But it does not help.
My server has two network interfaces:
- the one connected to my local area network (private IP address)
- the one connected to my ADSL modem (public IP address)
So, I guess it explains why I am using "+ip".
Why should I use my LAN IP address?
If I do that, my server will not be available on the Internet but only in my local area network.
So, you don't use "+ip" but your server is available online?
If I remove "+ip" from my command line as you suggest, I get:
Code:
./hlds_run -insecure -game cstrike +maxplayers 32 +port 27015 1>stdout.log 2>stderr.log &
Is it what I should use?
Anyway, the port seems to be opened by hlds_run on my server on all my network interfaces:
Code:
$ sudo nmap -sT -sU -p1-65535 192.168.0.100
[...]
27015/udp open|filtered halflife
[...]
$ sudo nmap -sT -sU -p1-65535 78.199.90.154
[...]
27015/udp open|filtered halflife
[...]
So, maybe the server is working correctly.
Maybe the problem is only on the client side.
Is it possible to communicate with my server through telnet or something like that?
Code:
$ telnet 192.168.0.100 27015
Trying 192.168.0.100...
telnet: connect to address 192.168.0.100: Connection refused