<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 11:53:04 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>[MC-1030] Custom ip/port for lan multiplayer</title>
                <link>https://bugs.mojang.com/browse/MC-1030</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;Not being able to select costume IP to launch multiplayer server from singleplayer sucks!!!&lt;br/&gt;
Also minecraft on linux selects 127.0.0.1 as lan IP and it should be something like 192.168.1.56!!&lt;/p&gt;</description>
                <environment>all</environment>
        <key id="12329">MC-1030</key>
            <summary>Custom ip/port for lan multiplayer</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="3">Duplicate</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="hyperfang">hyper fang</reporter>
                        <labels>
                            <label>IP</label>
                            <label>multiplayer</label>
                    </labels>
                <created>Sun, 28 Oct 2012 15:08:48 +0100</created>
                <updated>Tue, 5 May 2015 00:17:04 +0200</updated>
                            <resolved>Fri, 9 Nov 2012 01:45:49 +0100</resolved>
                                    <version>Minecraft 1.4.2</version>
                                                                        <votes>1</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="19805" author="kumasasa" created="Fri, 9 Nov 2012 01:45:49 +0100"  >&lt;p&gt;Fixed in 1.4.4&lt;/p&gt;</comment>
                            <comment id="15355" author="emorodney" created="Tue, 30 Oct 2012 11:24:41 +0100"  >&lt;p&gt;The behaviour can be seen in Java outside of Minecraft:&lt;/p&gt;

&lt;p&gt;System.out.println (java.net.InetAddress.getLocalHost().toString());&lt;/p&gt;

&lt;p&gt;which prints different IP addresses according to the various circumstances already described (ie Windows vs Linux and modified /etc/hosts)&lt;/p&gt;</comment>
                            <comment id="15325" author="emorodney" created="Tue, 30 Oct 2012 08:46:11 +0100"  >&lt;p&gt;Should the localhost issue be reported as a separate bug, seeing as it is, well totally separate to the bug mentioned in the title.&lt;br/&gt;
It DOES matter to which IP the server is bound because the IP specifies the interface and localhost is not the same interface as Ethernet. Services which are bound to all interfaces are shown in netstat with a * instead of an IP address. Also you talk about binding to *:25565 - that&apos;s the server, the client&apos;s publish-to-LAN functionality doesn&apos;t use that port.&lt;br/&gt;
I have discovered some more about this that may be a work-around to Linux users and possibly a clue to developers: The IP address selected is the one associated with the hostname, as returned by the command line (&quot;hostname&quot;). And this may be affected by your hosts file (/etc/hosts). So for instance I had the following in my hosts file (/etc/hosts)&lt;/p&gt;

&lt;p&gt;127.0.0.1       localhost&lt;br/&gt;
127.0.1.1      westy3&lt;br/&gt;
These lines were written by the OS installer, and westy3 is the name I gave that computer at install time. Minecraft was binding to the second address. I now comment out the westy3 line like so&lt;br/&gt;
127.0.0.1       localhost&lt;br/&gt;
#127.0.1.1      westy3&lt;/p&gt;

&lt;p&gt;and the problem is fixed. Some more command output for your info:&lt;br/&gt;
dave@westy3:/opt/minecraft$ hostname&lt;br/&gt;
westy3&lt;br/&gt;
dave@westy3:/opt/minecraft$ host 127.0.1.1&lt;br/&gt;
Host 1.1.0.127.in-addr.arpa. not found: 3(NXDOMAIN)&lt;br/&gt;
dave@westy3:/opt/minecraft$ host 172.20.21.103&lt;br/&gt;
103.21.20.172.in-addr.arpa domain name pointer westy3.&lt;br/&gt;
dave@westy3:/opt/minecraft$ &lt;/p&gt;

&lt;p&gt;You see now the computer name is associated with a LAN address (a Bluetooth connection as it happens) and hey presto, Minecraft&apos;s publish-to-LAN now binds to this address. (At some point I&apos;ll confirm on a real LAN that this makes the game accessible, but I&apos;m 99% certain it will).&lt;/p&gt;
</comment>
                            <comment id="14743" author="selbram" created="Sun, 28 Oct 2012 17:43:41 +0100"  >&lt;p&gt;This is true. I have seen this twice though in here, which is odd. I just ran a test on CentOS6 and it binds to *:25565. Unless these guys are updating their serverip line in server.properties. I don&apos;t know how this is breaking. The only other issue would be related to firewalls.&lt;/p&gt;</comment>
                            <comment id="14742" author="kumasasa" created="Sun, 28 Oct 2012 17:36:07 +0100"  >&lt;p&gt;It doesn&apos;t matter to what IP the server is bound, from the server-hosting PC itself the server is reachable at 192.168.1.56, 127.0.0.1 or localhost, for the rest of the LAN the server is reachable at 192.168.1.56&lt;/p&gt;</comment>
                            <comment id="14741" author="selbram" created="Sun, 28 Oct 2012 17:33:51 +0100"  >&lt;p&gt;I believe the problem is that in linux it binds it to 127.0.0.1 and other people on the lan cannot connect to that.&lt;/p&gt;</comment>
                            <comment id="14739" author="kumasasa" created="Sun, 28 Oct 2012 17:32:20 +0100"  >&lt;p&gt;If your PC has &lt;b&gt;192.168.1.56&lt;/b&gt; than is &lt;b&gt;127.0.0.1&lt;/b&gt; the same, because the latter means &lt;b&gt;localhost&lt;/b&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="11739">MC-473</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                        <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Unconfirmed]]></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_11100" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Linked</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i05epz:</customfieldvalue>

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