X2Go Bug report logs - #515
"connectedHost" variable contains wrong IP, reason unknown (was: Re: [X2Go-User] Pb with x2go agent on ppc64 system)

Full log

Message #25 received at 515@bugs.x2go.org (full text, mbox, reply):

Received: (at 515) by bugs.x2go.org; 13 Jun 2014 16:21:26 +0000
From ionic@ionic.de  Fri Jun 13 18:21:24 2014
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_DKIM_INVALID,
	URIBL_BLOCKED autolearn=ham version=3.3.2
X-Greylist: delayed 356 seconds by postgrey-1.34 at ymir.das-netzwertkeam.de; Fri, 13 Jun 2014 18:21:24 CEST
Received: from Root24.de (powered.by.root24.eu [91.121.15.64])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id DCD8C5DB11
	for <515@bugs.x2go.org>; Fri, 13 Jun 2014 18:21:24 +0200 (CEST)
Received: from nopileos.local (home.ionic.de [85.183.67.131])
	by Root24.de (Postfix) with ESMTPSA id D56A03B005A6;
	Fri, 13 Jun 2014 18:15:27 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ionic.de; s=default;
	t=1402676128; bh=AFum3bvUG2iWHO3NRa+8ntsca5J8UcCUExnxy6PvgJ4=;
	h=Date:From:To:CC:Subject:References:In-Reply-To:From;
	b=Do6ocRsR/EVBmJnVRwm3BzOId7qPfdIaEo7Wd7kNitW8W+j6jsyv6umoCv8GF0sS1
	 IBggQ+BtOA6f4jLrIEdzc4ox+KVd4xyeSD8dXJHJNV1ueYb9Fsm11HJrJFzzFKcZze
	 vvoqJE8mc+OouPz0H5RH5G3tokgCWljXcWI3K1Mc=
Message-ID: <539B239F.1060401@ionic.de>
Date: Fri, 13 Jun 2014 18:15:27 +0200
From: Mihai Moldovan <ionic@ionic.de>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: sebastien chabrolles <s.chabrolles@fr.ibm.com>
CC: 515@bugs.x2go.org
Subject: Re: [X2Go-Dev] [X2Go-User] "connectedHost" variable contains wrong
 IP, reason unknown
References: <OF63CDD2EA.AB0207C6-ONC1257CF4.0033135B-C1257CF4.0039D4E6@fr.ibm.com> <20140611113037.Horde.qsAKjfq9P_p1svkMBI8Mtg1@mail.das-netzwerkteam.de> <539842C3.6010208@stefanbaur.de> <20140611124358.Horde.3fgisOaRzDKMd2835Ld1uA4@mail.das-netzwerkteam.de> <5398CE20.4090601@stefanbaur.de> <5398E061.6010000@gmail.com> <5399D7CC.9010408@ionic.de> <OF47115B4E.4B401215-ONC1257CF5.005EFDAE-C1257CF5.005FFA1D@fr.ibm.com> <539A0414.7040805@ionic.de>
In-Reply-To: <539A0414.7040805@ionic.de>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms080607070405010309090301"

[Message part 1 (text/plain, inline)]

* On 12.06.2014 09:48 pm, Mihai Moldovan wrote:
>> For the connection, I use IPV4 addresse, no hostname. There is only one IP on
>> the server.
> OK. I was asking because the code is calling gethostbyname() which, when given a
> host name, looks up the address of that specified host name. If, however, the
> host name should have multiple addresses, all of them will be returned in a list
> -- their order depending on how the DNS server spits them out. Most DNS servers
> use a round-robin method for this, so you will get a different ordering with
> each lookup.
>
> That was one possible explanation for what you might have experienced.
>
> However, if you're only using IP addresses directly everywhere, gethostbyname()
> merely converts the given string to its binary address representation in network
> byte order. Thus, the functionality is almost equal to inet_aton() (just the way
> the information is returned differs, but that's no functional change.)

Follow-up: I've written a simple program to look up hosts using the OS-provided
functions getaddrinfo() and inet_ntop(). If you (Sebastien) are interested, take
a look in /usr/src/domainlookup, although it's really boring.

Output for "./getaddrinfo localhost 127.0.0.1 loopback":

### information for localhost ###
addr 1: 127.0.0.1 (length 9)
addr 2: 127.0.0.1 (length 9)
addr 3: 127.0.0.1 (length 9)
addr 4: 127.0.0.1 (length 9)
addr 5: 127.0.0.1 (length 9)
addr 6: 127.0.0.1 (length 9)

### information for 127.0.0.1 ###
addr 1: 127.0.0.1 (length 9)
addr 2: 127.0.0.1 (length 9)
addr 3: 127.0.0.1 (length 9)

### information for loopback ###


Thus, it doesn't look like a system issue. The returned addresses are just fine.
Even if something WERE to convert 127.0.0.1 to "localhost" and back to an
address, the address list for localhost is fine and does not contain the unknown
addresses.

Seems like we're really seeing an nx bug on ppc64.

I'll supply more information later when I get back.



Mihai

[smime.p7s (application/pkcs7-signature, attachment)]

Send a report that this bug log contains spam.