I am running TREX v2.85 in stateless mode using Intel XXV710 SRIOV/DPDK VFs as docker container. My trex_cnf.yaml looks like below. My observation is that when running stateless traffic using some python API script, TREX resolves ARP requests and answer to ICMP requests, even if not in service mode. TREX is started with single dp core; "./t-rex-64 -i".
If I instead run trex with 2 dp cores; "./t-rex-64 -i -c 2", and use same traffic script it does no longer reply to ARP requests (it can still answer ICMP requests). Is this expected behaviour?
[root@trex-sriov-10 v2.85]# cat /etc/trex_cfg.yaml
- version: 2
interfaces : ["0000:03:02.2", "0000:03:02.3"] # list of the interfaces to bind run ./dpdk_nic_bind.py --status
prefix : trex1
limit_memory : 2048
rx_desc: 4096
tx_desc: 4096
port_info : # set e.g. ip,gw,vlan,eth mac addr
- ip : 172.80.23.244
default_gw : 172.80.23.1
vlan : 823
- ip : 172.80.24.244
default_gw : 172.80.24.1
vlan : 824
platform:
master_thread_id: 1
latency_thread_id: 33
dual_if:
- socket: 0
threads: [2,34]