<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><div id="yiv302125169">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>Thu, 3/26/09, Rick Jones <i><rick.jones2@hp.com></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">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<br><br><pre>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
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
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<br></pre></blockquote></div></td></tr></table><br>