Re: DAST: Iperf - write1 failed: Broken pipe - s84978 --at-- ss.uum.edu.my

This message usually indicates that the client is unable to connect to the
server.  If the iperf works with both the client and server running on
the same host (check both ends) the first step is to check IP routes on
both hosts.  This however looks like packets are being filtered.
You might also need to check for a firewall and any existing host
filters (e.g. iptables).
    Paul Hyder
    NOAA Forecast Systems Lab

Mitch Kutzko wrote: 
Date: Tue, 16 Aug 2005 00:33:27 -0500
To: s84978 --at-- ss.uum.edu.my
Subject: DAST: Iperf - write1 failed: Broken pipe - s84978 --at--


ss.uum.edu.my


Contacting DAST re: Bug report about Iperf
From: zara jr <s84978 --at-- ss.uum.edu.my>

Subject: write1 failed: Broken pipe

Question/Comment:
Hi and Good day.

I have a question, i was run iperf in server side and client side. In 

server side  I uses this command:

6inet# iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 64.0 KByte (default)
------------------------------------------------------------

In client side i write this comamnd:
[root --at-- localhost root]# iperf -c 202.187.80.50
connect failed: Connection refused
write1 failed: Broken pipe
write2 failed: Broken pipe
------------------------------------------------------------
Client connecting to 202.187.80.50, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 0.0.0.0 port 37099 connected with 202.187.80.50 port 5001
[  3]  0.0- 0.0 sec  0.00 Bytes  0.00 bits/sec

My question is, why this happend? What mean by "write1 failed: Broken pipe"

Hope you can help me. Thank you in advance.




--
Mitch Kutzko | mitch --at-- dast.nlanr.net | mitch --at-- ncsa.uiuc.edu | 217-333-1199
http://hobbes.ncsa.uiuc.edu/


Other Mailing lists | Author Index | Date Index | Subject Index | Thread Index