It certainly is for Source (SRCDS), but for HLDS you have to use +ip.
Perhaps it's just a bug, but on Windows HLDS -ip would not bind to the
specified IP; instead it would bind to the primary/main IP on the dedicated
server.
I know this is the Linux list, but perhaps my experiences with the
To: hlds_linux@list.valvesoftware.com; hlds@list.valvesoftware.com
Subject: Re: [hlds_linux] question on if this is normal (-ip/+ip)
It certainly is for Source (SRCDS), but for HLDS you have to use +ip.
Perhaps it's just a bug, but on Windows HLDS -ip would not bind to the
specified IP; instead
] question on if this is normal (-ip/+ip)
It certainly is for Source (SRCDS), but for HLDS you have to use +ip.
Perhaps it's just a bug, but on Windows HLDS -ip would not bind to the
specified IP; instead it would bind to the primary/main IP on the
dedicated server.
I know this is the Linux list
@list.valvesoftware.com
Subject: Re: [hlds_linux] question on if this is normal (-ip/+ip)
It certainly is for Source (SRCDS), but for HLDS you have to use +ip.
Perhaps it's just a bug, but on Windows HLDS -ip would not bind to the
specified IP; instead it would bind to the primary/main IP on the
dedicated
Original message from ploc:
yeah gave me a error that it couldn't bind to that ip or something I
figured it was just that im using cable threw a router so figured it
couldn't bind it cause the ip wasn't actually accessable threw that
computer or that computer didn't know the ip as its own
5 matches
Mail list logo