[X2Go-Dev] [X2Go-User] "connectedHost" variable contains wrong IP, reason unknown

sebastien chabrolles s.chabrolles at fr.ibm.com
Thu Jun 12 19:28:20 CEST 2014


Hi Mihai,

ppc64 support support Big and Little Endian, But... it is quite new and 
most of the OS distro are BigEndian (fedora, Radhat, Suse, ....) only 
Ubuntu propose both : ubuntu ppc64 (BE) and ubuntu ppc64el (LE).It will 
take time for the Enterprise Linux distro to move and fully support ppc64 
in Little Endian.

So, I don't say that the problem is due to Endianness, but we have to keep 
in mind that fedora 20 ppc64 is BIG Endian.

 # lscpu 
Architecture:          ppc64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Big Endian
...

For the connection, I use IPV4 addresse, no hostname. There is only one IP 
on the server.

If you need to have access to the server, this can be done with openVPN 
certificate. This is only a "sandbox server" to reproduce the x2go issue.

Cordialement / Best Regards







Sébastien Chabrolles
Power Systems Benchmark Specialist
IBM Client Center, Montpellier 
1 rue vieille poste 34000 Montpellier FRANCE 
Tel +33 4 67 34 40 95
Email : s.chabrolles at fr.ibm.com

  




From:   Mihai Moldovan <ionic at ionic.de>
To:     bellyacres at gmail.com, x2go-dev at lists.x2go.org
Date:   12/06/2014 18:46
Subject:        Re: [X2Go-Dev] [X2Go-User] "connectedHost" variable 
contains wrong IP, reason unknown
Sent by:        x2go-dev-bounces at lists.x2go.org



* On 12.06.2014 01:04 am, Mike wrote:
> I'm far from being any type of coder.  Looks like it could be an endian 
issue
> though.

No, that doesn't make sense to me.

ppc64 supports both little endian (which is compatible to x86 -- and as it 
works
on x86, it's highly doubtful this is a little endian issue) and big endian
(i.e., network byte order), the latter one being the default.

>From what I gathered skimming the code, no conversion is taking place
(understandble, as inet_ntoa does only create a string with the dotted 
quad IPv4
address from an address in _network byte order_.)

Generally, nobody needs the address in binary form in host byte order.


Sebastien, how are you connecting? Via an IPv4 address, or via a host 
name? Does
the host name by any chance contain multiple addresses?


(Though I might like to add, that actually debugging this issue really 
requires
being able to reproduce the issue, recompiling nx with debug info and 
attaching
a debugger.)


Mihai

[attachment "smime.p7s" deleted by sebastien chabrolles/France/IBM] 
_______________________________________________
x2go-dev mailing list
x2go-dev at lists.x2go.org
http://lists.x2go.org/listinfo/x2go-dev

Sauf indication contraire ci-dessus:/ Unless stated otherwise above:
Compagnie IBM France
Siège Social : 17 avenue de l'Europe, 92275 Bois-Colombes Cedex
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 655.732.332,20 ?
SIREN/SIRET : 552 118 465 03644 - Code NAF 6202A 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x2go.org/pipermail/x2go-dev/attachments/20140612/f4341fea/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 3041 bytes
Desc: not available
URL: <http://lists.x2go.org/pipermail/x2go-dev/attachments/20140612/f4341fea/attachment-0004.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 7424 bytes
Desc: not available
URL: <http://lists.x2go.org/pipermail/x2go-dev/attachments/20140612/f4341fea/attachment-0005.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 9054 bytes
Desc: not available
URL: <http://lists.x2go.org/pipermail/x2go-dev/attachments/20140612/f4341fea/attachment-0006.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 3041 bytes
Desc: not available
URL: <http://lists.x2go.org/pipermail/x2go-dev/attachments/20140612/f4341fea/attachment-0007.jpe>


More information about the x2go-dev mailing list