Hanoh Haim

This is not a real issue. With ASTF there is a flag called accurate-schedule that “solve” this. The issue that we gather 32 packets in table and flush them together....

It is not exposed in STF. We are working on ASTF right now. Thanks, Hanoh On Fri, 24 Aug 2018 at 0:39 Matt Callaghan wrote: > This is not ASTF,...

This is expected in STF mode. Read carefully the notes in 4.1 STF manual. Either disable pcap ipg or use offline tool to create RTT between c->s or use ASTF...

In basic usage, TRex does not wait for an initiator packet to be received. The response packet will be triggered based only on timeout (IPG in this example). In advanced...

TRex play the pcap in the exact timing (~10usec) however because there are queues (TRex output queue and DUT input queue) and the queues could be with different length 10usec...

TRex scheduler (in all modes) is accurate in 10usec range. In very low speed (1kpps) it flushs every 1msec. When using 2 interfaces with real world queues (DUT and TRex)...

This is correct. TRex STF when replaying pcap with two sides requires: 1. Pcap RTT will be bigger than 10msec (latency of the DUT). 2. The capture location should be...

please close this if there is no other questions regarding this

This is foundemental to how STF works, if the manual is not clear about that you can come up with a pull-request thanks, Hanoh On Tue, Oct 2, 2018 at...

@jsmoon it is related to the ASTF multi-profile. The counters are released (as part of the profile) and then touched. We have clean up some stability issues in our regression...