This is technically a feature request. However it is a simple feature that is already available in the java server and is trivial to implement in Bedrock server.
When the server starts up, it binds to the configured server-port (19132 by default). The server is hard coded to bind on all addresses (0.0.0.0:19132). The bind address should be configurable (like in java edition) with a server-ip property in the server.properties file. This would allow users to configure their host with multiple virtual ip addresses and run a separate bedrock server process on each ip.
Local server discovery is done using UDP broadcast on port 19132. This means that hosting multiple Bedrock Servers on the same host can't be done using different ports. The servers running on non-standard ports will never be discovered. Using multiple virtual ip addresses would allow for multiple servers on the same host being automatically discovered rather than needing to be manually configured in clients.
This issue was raised in BDS-163 but it was apparently misunderstood and dismissed. No one expects the server-ip property to actually configure the ip address of the machine. The property is intended to allow the server owner to have control over which of their already configured ip addresses the Bedrock Server binds to.
Comments 9
This is also an issue on multi-homed hosts (e.g. home routers) where one interface is on the Internet and one is on the local net; running a server on such a host means accepting connections from the Internet.
You may be able to work around this by running the server in a Docker container where you can use the --port directive to bind a specific address.
This is also an issue on multi-homed hosts (e.g. home routers) where one interface is on the Internet and one is on the local net; running a server on such a host means accepting connections from the Internet.
You may be able to work around this by running the server in a Docker container where you can use the --port directive to bind a specific address.
Thank you for your report!
However, this issue is Invalid.
You have posted a feature request or a suggestion. This site is for bug reports only.
For suggestions, please visit Minecraft Suggestions on Reddit or visit the Feedback website.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
However, this issue is Invalid.
You have posted a feature request or a suggestion. This site is for bug reports only.
For suggestions, please visit Minecraft Suggestions on Reddit or visit the Feedback website.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
However, this issue is Invalid.
You have posted a feature request or a suggestion. This site is for bug reports only.
For suggestions, please visit Minecraft Suggestions on Reddit or visit the Feedback website.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
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.Â
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.Â
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.Â
This is also an issue on multi-homed hosts (e.g. home routers) where one interface is on the Internet and one is on the local net; running a server on such a host means accepting connections from the Internet.
You may be able to work around this by running the server in a Docker container where you can use the --port directive to bind a specific address.