[netperf-talk] Built trunk on Windows, OS interoperability

Cook, Jonathan jonathan.cook at nist.gov
Wed May 30 15:17:02 PDT 2012


My only suggestion is that you verify that you are using the same version of netperf and netserver on both the Linux and Windows machines.  You might also use Wireshark to verify that the packets are getting through.

This is what I see when I use the basic commands:
Windows command line:
C:\Program Files (x86)\Netperf>netperf -H 10.8.7.243
TCP STREAM TEST from 0.0.0.0 () port 0 AF_INET to 10.8.7.243 () port 0 AF_INET :
 histogram : interval : demo
Recv   Send    Send
Socket Socket  Message  Elapsed
Size   Size    Size     Time     Throughput
bytes  bytes   bytes    secs.    10^6bits/sec

 87380   8192   8192    10.00     286.41

C:\Program Files (x86)\Netperf>netserver
Starting netserver with host 'IN(6)ADDR_ANY' port '12865' and family AF_UNSPEC



Linux command line:
[demo at appserver ~]$ netperf -H 10.8.7.167
MIGRATED TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 10.8.7.167 () port 0 AF_INET : interval : demo
Recv   Send    Send
Socket Socket  Message  Elapsed
Size   Size    Size     Time     Throughput
bytes  bytes   bytes    secs.    10^6bits/sec

  8192  16384  16384    10.00     314.52
[demo at appserver ~]$ netperf -V
Netperf version pre-2.6.0-tot
[demo at appserver ~]$ netserver -V
Netperf version pre-2.6.0-tot
[demo at appserver ~]$

-----Original Message-----
From: netperf-talk-bounces at netperf.org [mailto:netperf-talk-bounces at netperf.org] On Behalf Of Jeremy Eder
Sent: Wednesday, May 30, 2012 3:00 PM
To: netperf-talk at netperf.org
Subject: Re: [netperf-talk] Built trunk on Windows, OS interoperability

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I tried it both directions, so with Windows 2008 as both a sender and as a receiver.

I was using the most basic:

> netperf.exe -H <ip_of_Linux>
> netserver.exe

And on the linux side...
# netperf -H <ip_of_win2k8>
# netserver

The machines are on the same subnet, firewalls disabled, all that.
I can telnet back and forth on the control port 12865.

Jonathan, a point of interest is that the executables you emailed me behaved the same as the ones I compiled today; in that they don't pass traffic when testing between operating systems.  telnet test still passes.  I understand those exe's work fine for you.

Further oddity, I have netperf 2.4 exe's generated eons ago by a colleague, and those have no problems between operating systems on my gear.

I suppose I'll setup a Win7 build environment to rule that out...






On 05/30/2012 04:53 PM, Cook, Jonathan wrote:
> Jeremy,
> Could you send the command that you used that did not work?  Were you running netperf or netserver on Windows when it didn't work?  I have been using netserver on Linux and netperf on Windows without a problem. I built my Windows executable in the Windows XP x86 free build environment and it works on both XP and Windows 7.  You might want to try that.
> 
> As an experiment I built in the Windows Win7 x64 free build environment and did not see the error you are seeing.
> 
> Jon Cook
> 
> -----Original Message-----
> From: netperf-talk-bounces at netperf.org 
> [mailto:netperf-talk-bounces at netperf.org] On Behalf Of Jeremy Eder
> Sent: Wednesday, May 30, 2012 2:31 PM
> To: netperf-talk at netperf.org
> Subject: Re: [netperf-talk] Built trunk on Windows, OS 
> interoperability
> 
> Hi Rick, sorry for the delay.  I went and tried to build svn585 and things were significantly cleaner, and I did not have to remove the OMNI tests.
> 
> Still there was 1 error, and the built executables did not function properly when testing linux<->windows.  They did work when talking windows<->windows.
> 
> Attached is the build logs, if you'd like to have a look.
> 
> 
> 
> 
> 
> On 05/16/2012 05:24 PM, Rick Jones wrote:
>> On 05/16/2012 01:14 PM, Jeremy Eder wrote:
>>> Hi all,
>>>
>>> Using svn revision 576, I was able to get netperf/netserver compiled 
>>> on Windows 2008 R2 (had to remove -DWANT_OMNI from sources file for both).
> 
>> I've been mucking about in top-of-trunk but not compiling under 
>> Windows so would like to see the errors so I might fix things up.
> 
>>> I can use those binaries successfully to test windows-to-windows.  
>>> But receive "Unknown error 998" when trying to run a test from 
>>> Linux-to-windows.
>>>
>>> Came across this thread which indicated the potential cause as 
>>> version
>>> mismatch:
>>>
>>> http://www.netperf.org/pipermail/netperf-talk/2009-July/000576.html
> 
>> More generally, that email talks about the netserver side being asked 
>> to run a test it does not know about.  Changing versions is how one 
>> got netserver to know about the test.
> 
>>> So I compiled from svn rev 576 on Linux as well, and yet the error 
>>> persists.
>>>
>>> I saw the below post, which indicated windows compile worked (no 
>>> comments about having to remove -DWANT_OMNI), but no notes about 
>>> testing between different operating systems...
>>>
>>> http://www.netperf.org/pipermail/netperf-talk/2012-April/000956.html
>>>
>>> Any ideas what could be the cause ?
> 
>> Unless you (know to) disable the WANT_MIGRATION from config.h, the 
>> Linux version will compile things to "migrate" several of the classic 
>> tests to the "omni" code and so will have asked the Windows side to 
>> run an omni test.  Since the Windows side was compiled without omni 
>> support, it did not know about the test, and so returned the 998. I 
>> suspect if you tried from Windows to Linux it would be OK at least as far as running goes.
> 
>> happy benchmarking,
> 
>> rick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPxopRAAoJEJqn3Wey3P5nsyUP/3qFD6NffHvs/dnnkjO/BQ9n
Pr8aKPfIJoQxTbv0fvfNQjGIe2BsONxlysh6rk3CF86WJ3gZZU5nEHDVHINrTsho
taeDkY2Poz3NGqN7T0GYamd08r7V6IAAkIrYl+NoPaowe90g18jWjaAtIkJ8HELp
MXylxfvCwzUZv0HEprV+oWColPD1SOCjO0PsMv8ZOdlvdYbhtx0CUtqtp40iv7rW
VuO5ZEGwYy7Z5aS4gkv/7oFeTxd2VY+8HHItpnwHylfVTQVfVJ3zLMG+NTFZhwVe
pdHvNhz4dpgWVVj6HsrcnKElNKEGnU8cY2y12gDwLzPZEJG1DoxefmN/GTzHfOr5
nOcNzd5jcdR0WLCvwIfHdWQUtYKJXC0Vdv8CV2CTntxdMj5OVDnfOGfbidwPhKEe
Pd8e5NJFwVJhzvruG6GwlFQiv0Hat7fCiLgaYOsZfXawk7YxCeCvAZ9xmaaSKeTh
hFNFo1vu9Ih6s6BcsszmvVujuwSMf/EDOTb47r6yteJMZGRhVr5+kBW9Py6N5zP3
yrK51If9APjmYvWqp/VKdhNECFmPPF55bHkKV7GBPTh4lEkOiy2kW89QOADDayd2
wF3H8aF8FJUfaNmjcGI2elJNHuPHPx3h7mbMcvIXQ90pgwTwt1QQ29iq6XmCEB92
AqSvAPq9O3dvpOAAt0Sm
=KQl2
-----END PGP SIGNATURE-----
_______________________________________________
netperf-talk mailing list
netperf-talk at netperf.org
http://www.netperf.org/cgi-bin/mailman/listinfo/netperf-talk


More information about the netperf-talk mailing list