It depends where the failure occurs. I send udp packets to non existent hosts/IP's all the time and iperf doesn't care. If the failure is on the iperf host itself it will prolly care
----- Original Message ----- From: Jon Dugan [mailto:[email protected]] Sent: Monday, October 10, 2011 06:17 PM To: iperf-users <[email protected]> Subject: Re: [Iperf-users] Option to auto stop UDP traffic when network goes down Excerpts from Shashank Khanvilkar's message of Mon Oct 10 16:43:16 -0500 2011: > Hello, > Thanks for any response in advance. > > I would like to know if iperf supports (or planning to support) any > mechanism where the sender will automatically detect (using some sort of > keep-alives, say) that the network is down and stop pumping in UDP traffic. > Let me know if something like this exists. Well it depends on what you mean. If the far end host goes down or is partitioned from the network (it becomes unreachable fro some reason) Iperf will exit due to the conventional mechanics of using the sockets interface. For example: (192.168.1.1 is not reachable from my test host.) $ iperf -u -c 192.168.1.1 ------------------------------------------------------------ Client connecting to 192.168.1.1, UDP port 5001 Sending 1470 byte datagrams UDP buffer size: 9.00 KByte (default) ------------------------------------------------------------ [ 3] local 198.124.252.117 port 59240 connected with 192.168.1.1 port 5001 write2 failed: No route to host [ ID] Interval Transfer Bandwidth [ 3] 0.0- 0.0 sec 1.44 KBytes 1.04 Mbits/sec [ 3] Sent 1 datagrams read failed: No route to host [ 3] WARNING: did not receive ack of last datagram after 1 tries. The important bit above is: "write2 failed: No route to host" There are other classes of failures that will not get detected, which something like keep alives would probably help with. However, there are no plans at this point to implement a keep alive system in Iperf. Hope that helps, Jon ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Iperf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/iperf-users <font size="1"> <div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in'> </div> "This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system." </font> ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Iperf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/iperf-users
