Bedrock Server forces to use different port nubers for ipv4 (19132) and ipv6 (19133). This can lead to connection problems.
Example 1: A connection to [ipv6-address]:19132 will always fail
Example 2: A connection to [ipv4-address]:19133 will always fail
Example Setup:
In my setup I use the domain example.com which resolves to the ipv4 AND the ipv6 address of my Server. In this setup every client can choose which protocol to use.
If trying to connect to example.com:19132 the connection will only succeed if the client chooses to use ipv4. Vice Versa for Port 19133.
So the client-side user needs to know which port to use, which is a difficult Task for a normal user.
Possible Solution:
Allow to use the same port number for ipv4 and ipv6 (as in java edition)
Comments 15
I don't believe this is possible due to the use of UDP rather than TCP but could be completely wrong.
I don't believe this is possible due to the use of UDP rather than TCP but could be completely wrong.
DNS uses port 53 on both tcp and udp for both IPv4 and IPv6 on Windows and Posix platforms.
In short, yes. it's very possible with tcp and/or udp.
DNS uses port 53 on both tcp and udp for both IPv4 and IPv6 on Windows and Posix platforms.
In short, yes. it's very possible with tcp and/or udp.
UDPv4 and UDPv6 are technically different protocols. There are no "shared ports" beetwen this two protcols. But the whole idea behind dual stack is to use the same port number for the same application to hide the actual used protocol from the user.
So let the client-software decide which protocol to use and not the user.
Another possible workarround would be to NAT the UDPv6 port to the UDPv4 port number or vice versa. But this tends to be more difficult to setup than differnt dns records and a waste of ressources for the NAT.
UDPv4 and UDPv6 are technically different protocols. There are no "shared ports" beetwen this two protcols. But the whole idea behind dual stack is to use the same port number for the same application to hide the actual used protocol from the user.
So let the client-software decide which protocol to use and not the user.
Another possible workarround would be to NAT the UDPv6 port to the UDPv4 port number or vice versa. But this tends to be more difficult to setup than differnt dns records and a waste of ressources for the NAT.
Closed as Won't Fix? This should be a simple fix. There could even be a command line option to specify the ports and allow the user to decide to pick the same ports.
Please reconsider fixing this.
Closed as Won't Fix? This should be a simple fix. There could even be a command line option to specify the ports and allow the user to decide to pick the same ports.
Please reconsider fixing this.
I don't believe this is possible due to the use of UDP rather than TCP but could be completely wrong.