UDP Stateless v2.89 vs v3.0x Functioning Different

[yusefMS06]

Goal is generate stateless UDP traffic between 2 Azure VMs. One sending traffic and the other receiving.

v2.89 transmitting stateless UDP traffic appears on the receiving end and has no ierrors on the receiving end.

Also to note, I made sure routing was done in azure portal with the spoofed src IPs/dst IPs as well as I did not use "--no-ofed-check" in the v2.89 because I installed MLX OFED 5.3 externally . From my understanding v3.02 this is not required because it comes within the git repo.

Server Terminal 1: Start Trex client ./t-rex-64 -i -c 2 --cfg /etc/trex_cfg_server.yaml

Client Terminal 1: Start Trex client ./t-rex-64 -i -c 2 --cfg /etc/trex_cfg_client.yaml

Client Terminal 2: ./trex-console start -f stl/bench.py -m 500000pps -p 0 -t size=1024,vm=var1

v3.02 transmitting stateless UDP traffic appears on the receiving end and all ipackets are counted as ierrors on the receiving end.

Server Terminal 1: ./t-rex-64 -i -c 2 --no-ofed-check --cfg /etc/trex_cfg_server.yaml

Client Terminal 1: ./t-rex-64 -i -c 2 --no-ofed-check --cfg /etc/trex_cfg_client.yaml

Client Terminal 2: ./trex-console start -f stl/bench.py -m 500000pps -p 0 -t size=1024,vm=var1

Is stateless udp working for Azure VMs in v3.0x?

[hhaim]

@yusefMS06 v3.01 includes a new OFED. Azure is dependent on OFED version. When we upgrade the OFED we are tested against CX-5 NIC with the bare metal RedHat distro. I would try to build trex on the machine you are running on Azure, it might solve the issue.

[pankajrodge]

can you please paste the content of these two files /etc/trex_cfg_server.yaml /etc/trex_cfg_client.yaml