Re: [Iperf-users] (no subject)

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" wrote: > Hi Tomer, > > Thanks for posting the iperf

Re: [Iperf-users] I see UDP recvfrom() in iperf, but no sendto() .... calls write()

Which iperf version, i.e. output of iperf -v? write() can be used with UDP after a socket connect(). The socket connect occurs in Client::Connect() method for iperf 2+ UDP sockets support both connect() and bind() even though UDP connectionless.A connected UDP socket isn't connected in the T

Re: [Iperf-users] (no subject)

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, Tom

[Iperf-users] (no subject)

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.. Tha

[Iperf-users] I see UDP recvfrom() in iperf, but no sendto() .... calls write()

-- 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