You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
when using --xdp, tcpreplay sends traffic at maximum speed. I have a file rec1-4-4.pcap at rate ~153Mbps, but AF_XDP tcpreplay sender sends it at maximum speed:
Create veth pair (ip link add type veth, ip link set dev veth0 up, ip link set veth1 up)
Run tcpreplay --xdp --no-flow-stats -W -i veth0 file.pcap
Check if sending speed is the same as in file, compare xdp and non-xdp sending mode (remove --xdp)
Expected behavior
xdp mode should respect .pcap timestamps (send at the same speed as it was recorded)
Screenshots
System (please complete the following information):
OS: Ubuntu
OS version: 24.04
Tcpreplay Version 4.5.1
Additional context
tcpreplay version: 4.5.1 (build git:v4.5.1)
Copyright 2013-2024 by Fred Klassen <tcpreplay at appneta dot com> - AppNeta
Copyright 2000-2012 by Aaron Turner <aturner at synfin dot net>
The entire Tcpreplay Suite is licensed under the GPLv3
Cache file supported: 04
Not compiled with libdnet.
Compiled against libpcap: 1.10.4
64 bit packet counters: enabled
Verbose printing via tcpdump: disabled
Packet editing: disabled
Fragroute engine: disabled
Injection method: PF_PACKET send()
Not compiled with netmap
Optional injection method: AF_XDP```
The text was updated successfully, but these errors were encountered:
Describe the bug
when using --xdp, tcpreplay sends traffic at maximum speed. I have a file
rec1-4-4.pcap
at rate ~153Mbps, but AF_XDP tcpreplay sender sends it at maximum speed:When I use non-xdp sender variant, it works as expected (sends ~153Mbps):
To Reproduce
Steps to reproduce the behavior:
tcpreplay --xdp --no-flow-stats -W -i veth0 file.pcap
--xdp
)Expected behavior
xdp mode should respect .pcap timestamps (send at the same speed as it was recorded)
Screenshots
System (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: