We're starting FtB servers (Server 2008 R2, FTB Beta A 12, no extra mods) with the following settings in the config file:
We've noticed that the server binds to 0.0.0.0 for the query port, rather then using 208.167.251.112 (as the normal Minecraft server does). The easiest way to verify this is to start up the server, then use Process Explorer (double click the java.exe process and use the TCP/IP tab).
See attached screenshot, it's binding to the correct IP for the main server port, but 0.0.0.0 for the query port.
This is pretty critical to us, as we rely on the ability to set unique IP/port combinations in order to host multiple servers on the same machine. If we can't set the IP address, it's pretty tough to run any significant number of servers.
Code:
server-ip=208.167.251.112
server-port=25565
query.port=25566
enable-query=trueWe've noticed that the server binds to 0.0.0.0 for the query port, rather then using 208.167.251.112 (as the normal Minecraft server does). The easiest way to verify this is to start up the server, then use Process Explorer (double click the java.exe process and use the TCP/IP tab).
See attached screenshot, it's binding to the correct IP for the main server port, but 0.0.0.0 for the query port.
This is pretty critical to us, as we rely on the ability to set unique IP/port combinations in order to host multiple servers on the same machine. If we can't set the IP address, it's pretty tough to run any significant number of servers.
