<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
pre
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Clive,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I received an error similar(partial
response received 0 bytes) when I used a netperf to a newer version of
netserver. The netperf was running on a windows system while netserver on a
linux system…(I remedied the problem by updating the windows netperf to
match!). <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Hope this helps!<br>
Kate <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
netperf-talk-bounces@netperf.org [mailto:netperf-talk-bounces@netperf.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Clive Barker<br>
<b><span style='font-weight:bold'>Sent:</span></b> Monday, April 13, 2009 11:53
PM<br>
<b><span style='font-weight:bold'>To:</span></b> Rick Jones<br>
<b><span style='font-weight:bold'>Cc:</span></b> netperf-talk@netperf.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [netperf-talk] Packet
size</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0>
<tr>
<td valign=top style='padding:0in 0in 0in 0in'>
<div id=yiv302125169>
<p class=MsoNormal><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>hi everyone, i am hitting another bump and this
time, although i'm able to get something across, i continue to get the same
error message while sending TCP streams across<br>
<br>
any ideas please?<br>
<br>
test1:~$ netperf -H 192.168.1.13 -p 4000 -t TCP_STREAM -- -m 128
-D <br>
recv_response: partial response received: 71 bytes<br>
<br>
test1:~$ netperf -H 192.168.1.13 -p 4000 -t TCP_STREAM -- -m 512 -D<br>
recv_response: partial response received: 71 bytes<br>
<br>
test1:~$ netperf -H 192.168.1.13 -p 4000 -t TCP_STREAM -- -m 10000 -D<br>
recv_response: partial response received: 71 bytes<br>
<br>
test1:~$ netperf -H 192.168.1.13 -p 4000 -t TCP_STREAM -- -m 10000000 -D<br>
recv_response: partial response received: 71 bytes<br>
<br>
test1:~$ netperf -H 192.168.1.13 -p 4000 -t TCP_STREAM -- -m 10000000 -D<br>
recv_response: partial response received: 71 bytes<br>
<br>
<br>
<br>
--- On <b><span style='font-weight:bold'>Thu, 3/26/09, Rick Jones <i><span
style='font-style:italic'><rick.jones2@hp.com></span></i></span></b>
wrote:<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>From: Rick Jones
<rick.jones2@hp.com><br>
Subject: Re: [netperf-talk] Packet size<br>
To: echelon360@yahoo.com<br>
Cc: netperf-talk@netperf.org<br>
Date: Thursday, March 26, 2009, 9:47 AM<o:p></o:p></span></font></p>
<pre><font size=2 face="Courier New"><span style='font-size:10.0pt'>Clive Barker wrote:<br>
> Hello,<br>
> <br>
> is there an option for me to send traffic and include a packet size, i<br>
need to generate several instances of netperf and have 3 separate runs starting<br>
from 512bytes, 256bytes then 128bytes.<br>
> <br>
> is this possible?<br>
<br>
Is<br>
this TCP or UDP? For UDP, since each send is a UDP datagram, you have<br>
direct control over the UDP datagram size with the test-specific -m option:<br>
<br>
netperf -H <remote> -t UDP_STREAM -- -m 128<br>
<br>
will have a stream of UDP datagrams<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'> with 128 byte user payloads, added to that<br>
will be 8 bytes of UDP header, 20 bytes (typically) of IPv4 header (or N bytes<br>
of IPv6 header) and then M bytes of data-link header (14 for Ethernet).<br>
<br>
If this is TCP, you have _indirect_ control over the quantity of data in each<br>
TCP segment with a combination of the -m and -D (TCP_NODELAY):<br>
<br>
netperf -H <remote> -t TCP_STREAM -- -m 128 -D<br>
<br>
will *ask* TCP to not bundle-up successive sends into larger TCP segments. So,<br>
barring packet losses and retransmissions that will be 128 bytes of user payload<br>
per segment, with 32 bytes (I'm including TCP timestamp option, 20 without<br>
it) of TCP header, and then IP and data-link headers<br>
as with UDP.<br>
<br>
Keep in mind that while 128, 256 and 512 bytes are usually smaller than a link<br>
MTU, they don't _have_ to be, and so you could have either IP fragmentation<br>
in the UDP case or TCP segmentation.<br>
<br>
Now, if you mean you<o:p></o:p></span></font></pre><pre><font size=2
face="Courier New"><span style='font-size:10.0pt'> wanted a *mix* of packet sizes in the same<br>
stream/flow/connection, that is something else, and is presently addressed in<br>
netperf4, the egg-laying-woolly-milk-pig :) netperf.<br>
<br>
rick jones<o:p></o:p></span></font></pre></div>
</td>
</tr>
</table>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>