I can find no documentation as to how to do this, or if it is even possible.
But I have a server on which 7 Days to Die somehow interferes with another (TF2 Classic) servers Sourcemod installation, for some reason.
Figuring it has to do with some sort of weird port collision, I'd like to assign a different IP to the server, as our server has 5 IPs assignable.
Posted Aug 29, 2020, 7:52 PM UTC
If you're using Linux, binding to the port is pretty simple. LGSM even has the option in the config file to make it stupid easy.
If you're on Windows, not so easy. Just another reason why all servers should be run on Linux, and not Winblows.
Unfortunately, many dedicated servers only run under Windows, so that is what we must use. And there's also the little bit where we have some users working on servers that would be absolutely mystified getting around Linux (let alone using SSH properly) so it's much easier to just have them a Windows desktop to remote into.
I WOULD use WSL, but unfortunately, WSL doesn't support using x86 libraries, and as such, SteamCMD won't even function with it. So I'm stuck to either using a VM that has been assigned a specific IP, or somehow changing the IP the game uses, which one would think would be a command line option like with most other games.
You could run the servers in VM's, and bind the VM to a specific adapter. You'll lose performance doing that though unless you've got pretty good hardware.
WSL is basically a joke. It can do some basic things, but nothing as advanced as you would require. Been there, done that.
Would also note that you can run TF2 on Linux, and headless Linux isn't nearly as hard as most people think. You'll get better performance, and access to a lot of extra tools that you don't have in Windows.
I'm aware of the performance implications, but if I have to do it, I guess I will do it. Luckily, the host hardware is a Xeon E-2288G with 32GB of RAM (with a lot of unused resources), so I think we'll be fine there.
And yeah, WSL 1, at least, is a joke. WSL 2 shows a lot of promise though, a lot of the I/O performance issues have been cleared up, and it generally runs fairly close to a native Linux experience.
I know all source engine games do, but those aren't the games I'd be worried about losing access to. I'm very well aware as to what we lose out on by not using Linux, but again, for some folks, it's just easier to stick with a current version of Windows Server, and so we do. A lot of people are terrified of a command line, but everyone understands the Windows desktop.
Maybe one day we can transition... One day...
You can just assign the port number in the serverconfig.xml file. Default is 27900.
I use 27900, 27910, and 27920 to run 3 at the same time
The IP is the same, you just have to point to the correct port. example 123.456.789.123:27910
I know this, but this issue happens no matter what port I assign, and I haven't been able to sniff out what the actual issue is, because of just how unusual the issue is.
I specifically want to know if there is a way to assign a specific, different IP, either at startup, or in the config file, so that it's running on, say, 111.222.255.191 rather than 111.222.255.190.
If I can't do this, I'll have to spin up an Ubuntu VM, I suppose, until I can figure this out.