<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sat Jan 11 07:17:54 UTC 2025

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Mojang Studios Jira</title>
    <link>https://bugs.mojang.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en</language>    <build-info>
        <version>9.12.2</version>
        <build-number>9120002</build-number>
        <build-date>10-01-2024</build-date>
    </build-info>


<item>
            <title>[BDS-1458] BDS forces different ports for ipv4 and ipv6</title>
                <link>https://bugs.mojang.com/browse/BDS-1458</link>
                <project id="11700" key="BDS">Bedrock Dedicated Server</project>
                    <description>&lt;p&gt;Bedrock Server forces to use different port nubers for ipv4 (19132) and ipv6 (19133). This can lead to connection problems.&lt;/p&gt;

&lt;p&gt;Example 1: A connection to &lt;span class=&quot;error&quot;&gt;&amp;#91;ipv6-address&amp;#93;&lt;/span&gt;:19132 will always fail&lt;/p&gt;

&lt;p&gt;Example 2: A connection to &lt;span class=&quot;error&quot;&gt;&amp;#91;ipv4-address&amp;#93;&lt;/span&gt;:19133 will always fail&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Example Setup:&lt;br/&gt;
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.&lt;br/&gt;
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.&lt;/p&gt;

&lt;p&gt;So the client-side user needs to know which port to use, which is a difficult Task for a normal user.&lt;/p&gt;


&lt;p&gt;Possible Solution:&lt;br/&gt;
Allow to use the same port number for ipv4 and ipv6 (as in java edition)&lt;/p&gt;</description>
                <environment></environment>
        <key id="260680">BDS-1458</key>
            <summary>BDS forces different ports for ipv4 and ipv6</summary>
                <type id="1" iconUrl="https://bugs.mojang.com/secure/viewavatar?size=xsmall&amp;avatarId=18903&amp;avatarType=issuetype">Bug</type>
                                    <status id="5" iconUrl="https://bugs.mojang.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="2">Won&apos;t Fix</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="nicoru">Nico Rumpeltin</reporter>
                        <labels>
                            <label>feature-check</label>
                    </labels>
                <created>Wed, 18 Sep 2019 14:02:27 +0200</created>
                <updated>Thu, 4 Jan 2024 21:02:43 +0100</updated>
                            <resolved>Thu, 4 Jan 2024 18:30:56 +0100</resolved>
                                    <version>1.8.1.2</version>
                    <version>1.14.32.1</version>
                                                            <votes>6</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="1298360" author="timriker" created="Thu, 4 Jan 2024 21:02:43 +0100"  >&lt;p&gt;Closed as Won&apos;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.&lt;/p&gt;

&lt;p&gt;Please reconsider fixing this.&lt;/p&gt;</comment>
                            <comment id="911262" author="nicoru" created="Wed, 3 Feb 2021 19:51:20 +0100"  >&lt;p&gt;UDPv4 and UDPv6 are technically different protocols. There are no &quot;shared ports&quot; 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&#160;used protocol from the user.&lt;/p&gt;

&lt;p&gt;So let the client-software decide which protocol to use and not the user.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Another possible workarround would be to NAT the UDPv6 port to the UDPv4 port number or vice versa. But this tends to be&#160;more difficult to setup than differnt dns records and a waste of ressources for the NAT.&lt;/p&gt;</comment>
                            <comment id="910434" author="JIRAUSER603871" created="Tue, 2 Feb 2021 18:15:48 +0100"  >&lt;p&gt;Yes in my opinion it&apos;s crazy to have separate ports for v4 and v6 for exactly the reason the OP describes. The only way around it is to have separate DNS records like v4.example.com resolving to the v4 address and v6.example.com resolving to the v6 address. Nobody does this it&apos;s insane. Please try to just have the server run one one port.&lt;/p&gt;</comment>
                            <comment id="737484" author="timriker" created="Mon, 22 Jun 2020 06:17:01 +0200"  >&lt;p&gt;DNS uses port 53 on both tcp and udp for both IPv4 and IPv6 on Windows and Posix platforms.&lt;/p&gt;

&lt;p&gt;In short, yes. it&apos;s very possible with tcp and/or udp.&lt;/p&gt;</comment>
                            <comment id="736760" author="ionicecko" created="Sun, 21 Jun 2020 04:55:53 +0200"  >&lt;p&gt;I don&apos;t believe this is possible due to the use of UDP rather than TCP but could be completely wrong.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_11500" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>ADO</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>384882</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10303"><![CDATA[Confirmed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_11700" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i12vnb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    </customfields>
    </item>
</channel>
</rss>