<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Iperf segmentation fault]]></title><description><![CDATA[<p dir="auto">Hi guys,</p>
<p dir="auto">I'm trying to setup a constantly running iperf server on pfSense to allow our site technicians to perform a reliable speed test to our edge firewall and router. Currently I'm running iperf from SSH with the command "iperf -s". On the client side I'm running xjperf version 2.0.2 which is using the command "bin/iperf.exe -c 10.7.0.254 -P 1 -i 1 -p 5001 -f m -t 10 -r -L 5001".</p>
<p dir="auto">When doing this I receive the following logs from server and client and the iperf server segmentation faults any ideas? I was also looking for a iperf3 backported package but was unable to find such a package. Anyone have one they could build or link?</p>
<p dir="auto">Server:</p>
<h2><a class="anchor-offset" name="br-server-listening-on-tcp-port-5001-br-tcp-window-size-63.7-kbyte-default"></a>–----------------------------------------------------------<br />
Server listening on TCP port 5001<br />
TCP window size: 63.7 KByte (default)</h2>
<h2><a class="anchor-offset" name="4-local-server_ip-port-5001-connected-with-client_ip-port-55428-br-id-interval-transfer-bandwidth-br-4-0.0-10.0-sec-83.3-mbytes-69.9-mbits-sec-br-br-client-connecting-to-client_ip-tcp-port-5001-br-tcp-window-size-65.0-kbyte-default"></a>[  4] local SERVER_IP port 5001 connected with CLIENT_IP port 55428<br />
[ ID] Interval      Transfer    Bandwidth<br />
[  4]  0.0-10.0 sec  83.3 MBytes  69.9 Mbits/sec<br />
–----------------------------------------------------------<br />
Client connecting to CLIENT_IP, TCP port 5001<br />
TCP window size: 65.0 KByte (default)</h2>
<p dir="auto">[  4] local SERVER_IP port 6889 connected with CLIENT_IP port 5001<br />
Waiting for server threads to complete. Interrupt again to force quit.<br />
Segmentation fault (core dumped)</p>
<p dir="auto">Client:</p>
<h2><a class="anchor-offset" name="bin-iperf.exe-c-server_ip-p-1-i-1-p-5001-f-m-t-10-r-l-5001-br-br-server-listening-on-tcp-port-5001-br-tcp-window-size-0.01-mbyte-default"></a>bin/iperf.exe -c SERVER_IP -P 1 -i 1 -p 5001 -f m -t 10 -r -L 5001<br />
–----------------------------------------------------------<br />
Server listening on TCP port 5001<br />
TCP window size: 0.01 MByte (default)</h2>
<hr />
<h2><a class="anchor-offset" name="client-connecting-to-server_ip-tcp-port-5001-br-tcp-window-size-0.01-mbyte-default"></a>Client connecting to SERVER_IP, TCP port 5001<br />
TCP window size: 0.01 MByte (default)</h2>
<p dir="auto">[176] local CLIENT_IP port 55469 connected with SERVER_IP port 5001<br />
[ ID] Interval      Transfer    Bandwidth<br />
[176]  0.0- 1.0 sec  9.92 MBytes  83.2 Mbits/sec<br />
[176]  1.0- 2.0 sec  9.13 MBytes  76.5 Mbits/sec<br />
[176]  2.0- 3.0 sec  8.32 MBytes  69.8 Mbits/sec<br />
[176]  3.0- 4.0 sec  8.11 MBytes  68.0 Mbits/sec<br />
[176]  4.0- 5.0 sec  8.32 MBytes  69.8 Mbits/sec<br />
[176]  5.0- 6.0 sec  8.44 MBytes  70.8 Mbits/sec<br />
[176]  6.0- 7.0 sec  7.94 MBytes  66.6 Mbits/sec<br />
[176]  7.0- 8.0 sec  8.53 MBytes  71.6 Mbits/sec<br />
[176]  8.0- 9.0 sec  7.88 MBytes  66.1 Mbits/sec<br />
[176]  9.0-10.0 sec  7.92 MBytes  66.5 Mbits/sec<br />
[176]  0.0-10.0 sec  84.5 MBytes  70.9 Mbits/sec</p>
]]></description><link>https://forum.netgate.com/topic/61570/iperf-segmentation-fault</link><generator>RSS for Node</generator><lastBuildDate>Wed, 15 Apr 2026 20:13:25 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/61570.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 10 Oct 2013 19:55:28 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Iperf segmentation fault on Thu, 09 Jan 2014 00:52:26 GMT]]></title><description><![CDATA[<p dir="auto">Still was unable to get this to work. I ended up just setting up a web based (speedtest.net) mini client on a server behind the firewall works okay but I would prefer iperf if you find a solution.</p>
]]></description><link>https://forum.netgate.com/post/437911</link><guid isPermaLink="true">https://forum.netgate.com/post/437911</guid><dc:creator><![CDATA[tj.krause]]></dc:creator><pubDate>Thu, 09 Jan 2014 00:52:26 GMT</pubDate></item><item><title><![CDATA[Reply to Iperf segmentation fault on Wed, 11 Dec 2013 14:40:26 GMT]]></title><description><![CDATA[<p dir="auto">This looks like a bug in iperf 2.  See http://sourceforge.net/p/iperf/bugs/31/</p>
<p dir="auto">I looked at this in Wireshark, and it appears that the iperf client immediately sends a FIN response to the SYN coming from the server for the reverse flow. Thus the server responds connection refused.</p>
<p dir="auto">I'm going to try iperf3 and see if it works with iperf 2 server.  (Edit - it doesn't work - iperf3 is not backward compatible. Builds of iperf3 do not appear to be available for Raspberry Pi currently)</p>
]]></description><link>https://forum.netgate.com/post/433681</link><guid isPermaLink="true">https://forum.netgate.com/post/433681</guid><dc:creator><![CDATA[timg11]]></dc:creator><pubDate>Wed, 11 Dec 2013 14:40:26 GMT</pubDate></item><item><title><![CDATA[Reply to Iperf segmentation fault on Tue, 10 Dec 2013 14:29:21 GMT]]></title><description><![CDATA[<p dir="auto">I have the same problem.  Running the iperf 2.0.4 as server on a Raspberry Pi at the remote end.  Iperf 1.7 on Windows 7 for the client.</p>
<p dir="auto">It seems to run fairly well except when the -r switch is used for bidirectional flow. That causes the segmentation fault on the server within a run or two.</p>
<p dir="auto">Did you ever find a solution?</p>
<p dir="auto">PS - sheesh - a 4-step CAPTCHA to post, right after completing a 4-step CAPTCHA to register.  I guess you have to be really motivated to use this forum….</p>
]]></description><link>https://forum.netgate.com/post/433583</link><guid isPermaLink="true">https://forum.netgate.com/post/433583</guid><dc:creator><![CDATA[timg11]]></dc:creator><pubDate>Tue, 10 Dec 2013 14:29:21 GMT</pubDate></item><item><title><![CDATA[Reply to Iperf segmentation fault on Fri, 11 Oct 2013 16:54:04 GMT]]></title><description><![CDATA[<p dir="auto">Seriously? No one else has had this issue?</p>
]]></description><link>https://forum.netgate.com/post/424296</link><guid isPermaLink="true">https://forum.netgate.com/post/424296</guid><dc:creator><![CDATA[tj.krause]]></dc:creator><pubDate>Fri, 11 Oct 2013 16:54:04 GMT</pubDate></item></channel></rss>