Vladimir Smirnov

> the certificate is ok, your linux machine is not up to date, you can check it using a browser I'm on OSX latest (and I have linux machines) that...

What worries me is what is reported in Server header: ``` Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fip ``` If that is true and not masked, that also means that you should upgrade...

I've had the same problem as an author. With ConnectX-6, it works in a different way than above. However, it works fine with ConnectX-5 and ConnectX-4 (I hope that will...

@hhaim if that helps, I've tried to adapt DPDK 23.11 in my fork: https://github.com/Civil/trex-core/tree/dpdk2311 But as I'm not that familiar with your build system and assumptions I probably did that...

Overall, while porting, I had few small complications: 1. few functions changed their names, e.x. `rte_thread_set_name(rte_thread_self(), "TRex RX");`, also same for bonding (`rte_eth_bond_slaves_get` -> `rte_eth_bond_members_get` - and probably that would...

@hhaim port 0 and 1 is a single cx-6 2x100, port 2 and 3 is cx5 2x100, cdat (pcie gen4 version) to show that it works with older generation just...

In all cases I've started a 1kpps test before getting stats (`start -f stl/bench.py -m 1kpps`) dpdk-23.11 variant: ``` trex>stats -x --port 1 Xstats Name: | Port 1: -------------------------------+---------------- rx_good_packets...

honestly I don't see anything wrong with raw counters there, but I'll have a look at the code later, maybe I'll find a problem there. What makes me wonder is...

@hhaim pps rate doesn't change the behavior, even if I do just 1 pps it will be counted as ierrors in trex per-port stats table and in tui with dpdk...

So about `stats - Length of get_xstats_names: 78 and get_port_xstats_values: 62 ` my theory is that this error is not valid, because, quoting DPDK doc: ``` There is an assumption...