Also note that for realistic results u should use more parrallel data streams, it can be configured with flag -P <value><\/strong>.<\/p>\n All options can be checked with diag traffictest run -h <\/strong>command.<\/p>\n <\/p>\n Ok, let’s start with iperf3 for the WAN connection. The configuration will look as follows:<\/p>\n diag traffictest client-intf <string> – Define a FortiGate interface. If we want to use a different iperf server, we need to set the client and server intf to the same port. In the image above, you can see that I’m using the WAN_1 interface – this is an EMAC Vlan that I’ve configured under the physical wan interface, which has no IP address assigned.<\/p>\n This is important to keep in mind – interfaces must be assigned an IP address<\/strong>.<\/p>\n <\/p>\n Another use case is to run iperf between fortigate ports – to test the basic functions of the device. Just set up the server and client interfaces and run the test.<\/p>\n In the image above, traffic is initiated from the CORE_PC interface – this is the vlan under port “a” on my fortigate, the target server is vlan WAN_1, which is under the physical interface “wan”.<\/p>\n Both VLANs are at the same VDOM.<\/p>\n If you want to test iperf between virtual domains, you will need the right routing and security rules to allow traffic<\/p>\n Note that I chose the LOOP-MGMT interface as the client’s intf – this is the loopback interface on the vdom root and has an IP address of 10.0.99.254. Nevertheless, you can see that the local IP address is set to 10.255.255.2 – this is the IP address of the VDOM link.<\/p>\n It appears that fortigate will select the source interface based on the routing table if the interface is of the loopback type.<\/p>\n If I choose a vlan interface as the intf client, the local IP address is not changed (WAN_2 is the EMAC Vlan in vdom root).<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":"
\ndiag traffictest server-intf <string> – Define a FortiGate interface.
\ndiag traffictest port <port_num> – Define the iPerf3 port running on the server.
\ndiag traffictest run -c <IP_ADDR> – Run iPerf3<\/p>\n![\"\"](\"http:\/\/pprzybyla.com\/blog\/wp-content\/uploads\/2024\/08\/Zrzut-ekranu-2024-08-02-073231-300x258.png\")
<\/p>\n![\"\"](\"http:\/\/pprzybyla.com\/blog\/wp-content\/uploads\/2024\/08\/Zrzut-ekranu-2024-08-02-074411-300x214.png\")
<\/p>\n![\"\"](\"http:\/\/pprzybyla.com\/blog\/wp-content\/uploads\/2024\/08\/Zrzut-ekranu-2024-08-02-080859-300x249.png\")
<\/p>\n![\"\"](\"http:\/\/pprzybyla.com\/blog\/wp-content\/uploads\/2024\/08\/Zrzut-ekranu-2024-08-02-081138-300x23.png\")
<\/p>\n![\"\"](\"http:\/\/pprzybyla.com\/blog\/wp-content\/uploads\/2024\/08\/Zrzut-ekranu-2024-08-02-081310-300x132.png\")
<\/p>\n![\"\"](\"http:\/\/pprzybyla.com\/blog\/wp-content\/uploads\/2024\/08\/Zrzut-ekranu-2024-08-02-081713-300x69.png\")
<\/p>\n