[solved] QHostAddress::toSring() backwards?

[ucntcme]

This is odd, to me at least.

I haver an integer that I convert to an IPv4 address using QHostAddress and setAddress(). (I pull the integers from /proc/net/tcp on Linux).

Yet when I use toString() I get the IP address backwards by octet. For examples: "1.0.0.127" and "21.1.168.192" :confused:
This is not what the docs say I should get (127.0.0.1 and 192.168.1.21, respectively) . Anyone else see this, and of so, how does one (simply) go about getting it output correctly? I could, I suppose, use split() and reverse the list order. But *ugh*, that'd be a hack plain and simple (though that could be said f using QHostAddress to convert an int to an IP address in dotted notation :p )

[wysota]

You probably have a little-endian machine and you should pass the number in network order (or vice-versa), but you are probably passing the number in host order. Try using htonl() and passing the result to setAddress().

[ucntcme]

Ah thanks, that did it.

Looking back at the docs for setAddress, it says for the ip6Addr entry to set high-order byte first, but nothing for ip4Addr. Methinks they should copy that over. ;)

funny how a totally unexpected result can really toss your wits out the window. :)