I think I finally found the trouble maker:
As I use two OPNsense in HA configuration they syncronise each and every connection state so if a OPNsense goes down the other can take over immediately without any downtime.
The setting is called "Synchronize Peer IP" and its default value is directed multicast (224.0.0.240).
In my opinion if I run iperf3 it generates a lot of multicasts which I can see at packet sniffer.
Insted of using multicast I set the proper IP address of the corresponding OPNsense VM. Now I can run iperf3 without having 100 % CPU.
I am not sure if directed multicast is a L2 or L3 topic.
As I use two OPNsense in HA configuration they syncronise each and every connection state so if a OPNsense goes down the other can take over immediately without any downtime.
The setting is called "Synchronize Peer IP" and its default value is directed multicast (224.0.0.240).
In my opinion if I run iperf3 it generates a lot of multicasts which I can see at packet sniffer.
Insted of using multicast I set the proper IP address of the corresponding OPNsense VM. Now I can run iperf3 without having 100 % CPU.
I am not sure if directed multicast is a L2 or L3 topic.
Statistics: Posted by An5teifo — Sun Jan 07, 2024 12:18 am