Ok, not sure what those are.   The source and destination ip are loopack
addresses 127.0.0.1 and the mac addresses are null.   I think these are
being originated by the operating system and not by iperf per se.  Do the
UDP ports match the ports in you iperf command line?

Bob

On Wed, Jul 20, 2016 at 8:24 PM, Tomer Pollak <tomerpol...@gmail.com> wrote:

> Hi
> I'm sorry, the attachment probably didn't work. can you see it now?
> it's 4 messages captured from wireshark on the server side. the server
> sending 4 messages of some reports to the client
>
> Thanks
> Tomer
>
> On Jul 21, 2016 12:13 AM, "Bob McMahon" <bob.mcma...@broadcom.com> wrote:
>
>> Hi Tomer,
>>
>> Thanks for posting the iperf version.
>>
>> I'm also trying to understand what exactly the "annoying messages" are.
>> Are they something you see in a wireshark capture?    Are you seeing them
>> in a terminal windows?     Can you post the actual messages?
>>
>> Bob
>>
>> On Wed, Jul 20, 2016 at 1:18 PM, Tomer Pollak <tomerpol...@gmail.com>
>> wrote:
>>
>>> Hi
>>> i can't find the original so i copied the last thread below.
>>> Thank you Bob and sorry for the delay:
>>> 1) attached from wireshark. hope its ok
>>> 2) this is the output: iperf version 1.7.0 <13 Mar 2003> win32 threads
>>>
>>> hope you could help to figure out what are these reports and how to
>>> avoid them..
>>> Thanks
>>>
>>> Tomer
>>>
>>> Hi Tomer,
>>>
>>> It's difficult to debug per the lakc of information contained email
>>> thread.  Please post two things
>>>
>>> 1)  The actual messages that are the problem
>>> 2)  The output of iperf -v
>>>
>>> Thanks,
>>> Bob
>>>
>>> On Fri, Jul 8, 2016 at 10:18 PM, Tomer Pollak <tomerpollak@...> wrote:
>>>
>>> > Anyone could please help with this reports issue?
>>> >
>>> > Thanks in advance
>>> >
>>> > Tomer
>>> >
>>> >
>>> >
>>> >
>>> > ---------------------------------------
>>> > Thank you Bob,
>>> >
>>> > i assume that the  "annoying messages" are some reports between the server
>>> > and the client.
>>> >
>>> > this are the iperf commands, running from jperf:
>>> > client:
>>> > iperf.exe -c 190.5.0.5 -u -P 1 -i 1 -p 5001 -l 100.0B -f k -b 5.0K -t 60 
>>> > -T
>>> > 1
>>> > server:
>>> > iperf.exe -s -u -P 0 -i 1 -p 5001 -f k
>>> >
>>> > Tomer
>>> >
>>> > On Wed, Jun 29, 2016 at 1:15 AM, Bob McMahon <bob.mcmahon@...>
>>> > wrote:
>>> >
>>> > > hmm, can you post the "annoying messages," the iperf version (iperf -v)
>>> > > and the iperf command lines for both client and server?
>>> > >
>>> > > Bob
>>> > >
>>> > > On Tue, Jun 28, 2016 at 5:29 AM, Tomer Pollak <tomerpollak@...>
>>> > > wrote:
>>> > >
>>> > >> Hello everyone.
>>> > >>
>>> > >> Im running jPerf with 2 stations connected by ethernet in order to test
>>> > >> the channel.
>>> > >> I configure the iPerf to run for few seconds, say 100. No matter which
>>> > >> parameters i configure, right after it finished, the iPerf sends,
>>> > >> independantly, few more messages.
>>> > >> sometimes its 10 messages with size of 1500 bytes and sometimes its
>>> > >> different.
>>> > >> Does anyone know how to avoid this annoying messages? its ruins my
>>> > >> performance test.
>>> > >>
>>> > >> Thanks in advance
>>> > >> Tomer
>>> >
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>>> traffic
>>> patterns at an interface-level. Reveals which users, apps, and protocols
>>> are
>>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>>> planning
>>> reports.http://sdm.link/zohodev2dev
>>> _______________________________________________
>>> Iperf-users mailing list
>>> Iperf-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/iperf-users
>>>
>>>
>>
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Iperf-users mailing list
Iperf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iperf-users

Reply via email to