Hello,
For the Ethernet Gateway use cases, different tools are used to enable, configure and exercise the data paths (e.g., iproute2, iptables, iperf3, strongSwan, libfci_cli). Every ETH path has a correspondent bash script that helps you in setting up the environment, then exercise the respective path, using your host machine and the iperf3 to generate, send and receive data.
The script's logic can be simply described as the following:
- configure the target device to use a given routing path (the SJA1110 would be the exception here)
- configure the host interfaces (i.e., add them in different network namespaces to isolate the traffic)
- generate traffic using iperf3 or other tools to exercise the ETH path
- gather statistics and display them
- clean-up
Depending on what you try to achieve, and what data paths you want to exercise, the set of used tools might be different. You could refer to the documentation of each tool used to configure these data paths for more information. For the flows that make use of the PFE interfaces or the libfci_cli tool, please check the FCI API reference document (https://source.codeaurora.org/external/autobsps32/extra/pfeng/tree/). Also, the M7 core-based ETH routing makes use of the Gateway application that runs on the M7 core, so you might want to look at how the configuration looks like (<GoldVIP_install_dir>/configuration/can-gw/workspace).
Best regards,
George
