Description |
This article describes that when a FortiGate device set up as an iPerf Client attempts to connect to another FortiGate device running v7.4.3 + and configured as a Speed Test server, the traffictest command on FortiGate iPerf Client produces the following error messages:
iperf3: error - control socket has closed unexpectedly
Topology:
A sniffer on FortiGate-VM shows that the connection is closed with a 'FIN'. |
Scope | FortiGate v7.4.3. and above. |
Solution |
FortiGate acting as a speed test server is not a standard iPerf server and should not be used for traffic testing. FortiGate traffictest and speedtest server functions are not designed to be connected. For information on how to use the speedtest server, refer to the following documentation: Speed tests run from the hub to the spokes in dial-up IPsec tunnels 7.0.1
The traffictest function is intended for:
Note: As described in Troubleshooting Tip: Configure FortiGate as speed test (iperf) server: to run the traffictest on the FortiGate, the speedtest-server must be disabled.
config system global sh full-configuration | grep speedtest |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.