Dumb question, did you remember to set sv_lan 1?
On 8/27/2014 7:57 PM, Jeff Nelson wrote:
Ah, good question. Actually when I refer to server browser, I'm referring
to the LAN tab portion of the server browser. I apologize if this has added
confusion, I didn't indicate that in any of my posts. In order for my
servers to appear there, I shouldn't need an internet connection. (Internet
is available to these servers, but i'm not creating special routes or
policies to handle external requests.)
On Wed, Aug 27, 2014 at 6:31 PM, Weasels Lair <[email protected]>
wrote:
This may sound like a stupid question, but if they are not intended to be
"open to the world for availability", then why do they need to appear on
the server list?
Also, if you are binding each instance to specific IP's like that, I would
expect the entire executable to default to using that IP for all of it's
communication - including "+clientport" and "+steamport" ports. If that is
truly the case (all ports get bound to the IP specified), then those ports
on those IP's need to be able to talk to/from the Internet in order to get
authenticated by steam, get published onto the server list, participate in
VAC, etc. If you are specifically not allowing them, that could be your
issue right there (i.e. why they never show-up on the server list).
On Wed, Aug 27, 2014 at 3:44 PM, Jeff Nelson <[email protected]>
wrote:
@Weasels
You are correct. I have 3, in this case, ip addresses added to the same
network card in Linux. These are not virtual interfaces created by a
hypervisor, but simply additional ip assignments to the physical network
interface or "Alias" addresses if you prefer.
These are all behind one firewall. They are not intended to be open to
the
world for availability. We use these servers for our LAN events only so I
do not intend to port forward traffic or create individual NATs.
However, as a quick note, even running one instance of srcds on a linux
box
will yield the same results when specifying an IP address - the game
server
is not shown on the server browser. If you remove the -ip argument, the
correct outcome is presented.
To make it more interesting, if I remove all assigned ip addresses and
use
the native ip on the linux box in the startup command, I get the same
results if I would have used one of the alias addresses - nothing appears
on the server browser. So it appears to me that my additional ip
assignments are not to blame for this issue - at least from what I see.
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
