09-23-2012, 10:47 AM
(This post was last modified: 09-23-2012, 11:01 AM by sinister3vil.)
Obviously an Internet connection is required, I'm asking for specifics.
For example, "you need TCP port 27000 for VAC", that kind of thing.
At the very least I need to know if :
-all traffic appart from the game traffic is TCP, and
-when advertised on the master server, does it say "server running here" or "server running on ip:port given in the srcds"?
edit: Maybe I should elaborate on the specifics of my case :
We have 2 subnets, lets say a.b.c.x and a.b.d.x.
a.b.c.x is fully networkable. a.b.d.x will only route towards local (in the same country) destinations. Any traffic towards foreign IPs is null-routed.
Scrds will be running on d.x, for more than one reasons, and will only be accessed by local players by design. I need these srcds to be fully working though, with VAC, community features, the works. Being able to update directly would also be great.
I can't put scrds on c.x nor can I change d.x's null-route policy. What I can do is route specific traffic from d.x through c.x. To do that I either need the IPs of Steam content servers or, at the very least, what exact traffic srcds has, besides the game traffic.
I also need to make sure that the srcds never appear anywhere with the a.b.c.x IP, only with the a.b.d.x IP.
For example, "you need TCP port 27000 for VAC", that kind of thing.
At the very least I need to know if :
-all traffic appart from the game traffic is TCP, and
-when advertised on the master server, does it say "server running here" or "server running on ip:port given in the srcds"?
edit: Maybe I should elaborate on the specifics of my case :
We have 2 subnets, lets say a.b.c.x and a.b.d.x.
a.b.c.x is fully networkable. a.b.d.x will only route towards local (in the same country) destinations. Any traffic towards foreign IPs is null-routed.
Scrds will be running on d.x, for more than one reasons, and will only be accessed by local players by design. I need these srcds to be fully working though, with VAC, community features, the works. Being able to update directly would also be great.
I can't put scrds on c.x nor can I change d.x's null-route policy. What I can do is route specific traffic from d.x through c.x. To do that I either need the IPs of Steam content servers or, at the very least, what exact traffic srcds has, besides the game traffic.
I also need to make sure that the srcds never appear anywhere with the a.b.c.x IP, only with the a.b.d.x IP.