CS:GO, server up, cannot connect.

[sinister3vil]

Hello, I'm trying to run a CS:GO server.

Server launches normally but no one can connect to it. Shows up as "not responding" in the server browser (added manually). No errors while connecting, it just retries 10 times and then fails.

The server is running on a linux box, with direct access to the internet (no NAT) but where all connections to foreign IPs are null routed, only domestic IPs are routed normally. This is fine, since it's supposed to be a community server and I don't care about getting foreign traffic/players. Domestic IP's though cannot connect to the server.

Any input would be gladly appreciated.

[sinister3vil]

So yeah, 14 views later no one has anything of value to add?

[Jejeleponey]

Hi,

Maybe the 14 viewers cannot help you ? ;-)

If you don't have an internet box, it's probably because you have a firewall on your linux box (like iptables). Have you set any rules on it ?

Try a tcpdump and connect to your server.
- If you see the connection packets, it's work, but you are dropped by the firewall
- If you don't see packets, the problem is somewhere else.

[sinister3vil]

Hi Jejeleponey,

As I explained in my original post, the box has a direct connection to the Internet but all traffic to non-domestic IPs is null routed, on a BGP level, by the ISP.

The actual question is : does a srcds need to call home, in order to accept incoming player connections?

BTW, apparently 1000 viewers cannot help me, since I've practically made this same thread in the past.
Normally I'd be ok with that, if I was posting on consolegamer.com/forum, but not a single response, in over a year, on a site supposedly dedicated to source dedicated servers, even if it is community managed, is kinda far fetched, don't you think?

[Jejeleponey]

All traffic on all port is null routed or lot of ports are allowed for traffic incoming ? If you don't know or don't have list of opened port, try a nmap for detect which port are allowed for traffic. After that, you can launch the server on this port (for example port 80 if it's open).
It's not the best solution of course, but i think it's the only solution with your ISP restriction.

The linux box is hosted at your home ? I don't understand how your network is set if the linux box have a direct connection to internet without an internet box. Your PC is connected with an other connection to internet ?

[sinister3vil]

(09-19-2014, 08:51 PM)Jejeleponey Wrote:  All traffic on all port is null routed or lot of ports are allowed for traffic incoming ? If you don't know or don't have list of opened port, try a nmap for detect which port are allowed for traffic. After that, you can launch the server on this port (for example port 80 if it's open).
It's not the best solution of course, but i think it's the only solution with your ISP restriction.

The linux box is hosted at your home ? I don't understand how your network is set if the linux box have a direct connection to internet without an internet box. Your PC is connected with an other connection to internet ?

Ports are not a matter in this context. The ISP does not route non-domestic traffic, on purpose.

The linux box is hosted in a datacenter, it's directly connected to one of the ISPs gateways, using a public IP (as in, the NIC has a public IP configured).

[Jejeleponey]

Ok, i was thinking your server was hosted at your home and you are unable to connect to it due to an ISP restriction.

Now, i think it's a server configuration problem. The first idea i have, it's you are runing your server in LAN mode (serveur launch normally but can't connect)

Can you copy past the server.cfg, starting command line and the console output message after starting ?

[sinister3vil]

Server runs fine if I bind it to a second NIC that routes all traffic normally. I can only do this for testing purposes though, can't have the server running that way.

Code:

sv_lan
"sv_lan" = "0"                                                                   - Server is a lan server ( no heartbeat, no authentication, no non-class C address

As I said, the question is does the server need to call home in order to accept connections?

Edit: Just want to add that this server seemed to work, with exactly the same configuration, when I first set it up, at least for a couple of hours. I only noticed it was not connecting a couple of days later and haven't been able to make it work since.

[Jejeleponey]

I don't understand what you say when you wrote "need to call home" ?
If it's mean the server need to connect to steam servers before accepting connection, it's no. Having lot of times "can't etablish connection to steam servers" in my console after startup and i was able to connect to them.
You probably have a problem with your linux box configuration if it's works fine on a second NIC, but don't know where is the problem :\