unhappy_mage
[H]ard|DCer of the Month - October 2005
- Joined
- Jun 29, 2004
- Messages
- 11,455
I want to run a few Minecraft servers, each with its own set of mods. I have tunneled IPv6 connectivity, so I was planning on giving each server its own static IPv6 address and telling them to bind to that address on the standard port 25565. Then players who also have IPv6 connectivity can connect to the server they want by connecting to minecraft-vanilla.mydomain, minecraft-rails.mydomain, etc.
The problem comes with IPv4-only players. I theorize that one should be able to NAT their connections, so connecting to wan.mydomain on port 25568 gives you a connection to minecraft-rails.mydomain:25565, but my PFsense 2.1-BETA0 box doesn't seem to want to do NAT from the IPv4 WAN connection to the internal IPv6 address of the Minecraft servers. What could I do to get around this? I suppose I could also supply each of the servers with in internal-only IPv4 address and have the server bind to both IPv4 and IPv6, then set up standard NAT, but that seems inelegant. Thoughts?
The problem comes with IPv4-only players. I theorize that one should be able to NAT their connections, so connecting to wan.mydomain on port 25568 gives you a connection to minecraft-rails.mydomain:25565, but my PFsense 2.1-BETA0 box doesn't seem to want to do NAT from the IPv4 WAN connection to the internal IPv6 address of the Minecraft servers. What could I do to get around this? I suppose I could also supply each of the servers with in internal-only IPv4 address and have the server bind to both IPv4 and IPv6, then set up standard NAT, but that seems inelegant. Thoughts?