netdev - Re: netperf and endianness

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20120607.182038.1630334891753669027.davem@davemloft.net>
Date:	Thu, 07 Jun 2012 18:20:38 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	rick.jones2@...com
Cc:	netdev@...r.kernel.org
Subject: Re: netperf and endianness

From: Rick Jones <rick.jones2@...com>
Date: Thu, 07 Jun 2012 18:16:14 -0700

> netperf sends things in network byte order.  It is all burried in
> send/recv_request and send/recv_response (in src/netlib.c).

Aha, I was grepping for things like ENDIAN when I should have
grepped for htonl() :-)

> Over the years I've run netperf between different endian systems
> with success. Chances are good that there is a netperf version
> mismatch between the sides - at least 99 times out of 10 that is
> what is happening when netperf doesn't work (other than with
> firewalls in place).

Indeed, you are right.  I was trying to speak to 2.4.4 using
2.5.0 :-)

Thanks!
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html