Jonathan Martinez
Assigned
Reported
Comments
This is needed for servers using bump in the line firewalls where the server has public IPv4 and IPv6 addresses bound to its interface.
Although, its technically not a bug, it is a glaring omission for a dedicated server instance to be unable to bind to a specific IP address.
I am having an issue that is indicative of this behavior. The bedrock server appears to bind to all IP addresses using 0.0.0.0:19132. If I already have another server bound to an IP with the same port as bedrock 19132 it causes the bedrock server to fail to boot because it can't bind to an IP. I can put in the config to bind to a specific IP like the java version, but it does not appear to do anything.
This is causing an issue that prevents multiple bedrock servers from being able to run on the same box.
Trying to run two servers:
A Survival server on IP1:19132
A Creative server on IP2:19132
22% of Internet users in the USA is on IPv6. This is a large group of people that you would be affecting by disabling the IPv6 Stack.
I run a private cloud that only uses native IPv6. This seems like a large oversight to disable a fundamental networking protocol in this day and age.
This is constantly a repeating issue affecting server operators as noted in: BDS-7707, BDS-2100, BDS-163
Please consider looking into this to help us host multiple instances on the same server. Thank you!
This missing feature makes it difficult to run multiple instances on a hosting server that has public IP's bound to its interface. This can be done behind a firewall and securely. Additionally, it can leave open ports on IP's that server operators do not wish to be open or interfere with other public IP's dedicated to other hosted instances on the same system. Although, its technically not a bug, it is a glaring omission for a dedicated server instance to be unable to bind to a specific IP address.