[mohaa] ...any troubles yet?

[Chris Nims]

How about for cases when the gaming server is on a private network 
behind a router/firewall?  In my case my server has an IP address of 
192.168.0.x and I have the firewall doing port forwarding for udp 12203 
which seems to be working fine.  A few of us at work played over lunch 
connecting to my system at home...but we just had to know the name/ip of 
the box to be able to connect since it doesn't show up in the master 
list.   What IP should I set net_ip to on the command line in this case?

-Chris

Ryan C. Gordon wrote:

>>Speaking of binding - when the server launches, does it bind
>>itself to every interface on a multihomed machine? Does this/Will
>>this cause confusion when talking to the gamespy/2015 master
>>servers? What determines what the server presents itself as
>>to the master servers?
>>    
>>
>
>The interface to bind to is determined by the "net_ip" cvar which defaults
>to "localhost".
>
>Perhaps contrary to what you'd think, specifying "localhost" does not bind
>to the loopback interface (127.0.0.1), but uses INADDR_ANY when calling
>bind() (which binds to all local interfaces).
>
>You are still best off specifying a value for net_ip on the command line.
>
>--ryan.
>
>  
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/mohaa/attachments/20020717/9f247559/attachment.htm>