Re: [vpp-dev] Did anything ever make vpp's native ipsec stack (ia32) work with dpdk/phy nic?

I switched cipher from aes-gcm to aes-cbc. native stack works. it seems the issue is related to aes-gcm cipher support in native stack? Probably some integration bug between aes-gcm and native stack? On Tue, Nov 19, 2019 at 10:42 AM Chuan Han via Lists.Fd.Io wrote: > Hi, Damjan, > > See

Re: [vpp-dev] request review

I just tried make test and make test-debug on 23417 in my environment - the only tests I had the problem In my environment with are the test suites with long-running CLI commands, so I presume this means without the extended tests it should pass the verification. As for the extended tests -

Re: [vpp-dev] request review

(Thinking a bit more of this - assuming the aim with the extended tests was to make the scapy upgrade a single change - I would still maintain, that it would make more sense to first port the standard tests, and then separately look at extended tests - this way it will be much easier, since

Re: [vpp-dev] request review

Paul, I looked at both - to me they appear to deal with collateral damage from undiagnosed root causes, so unfortunately I could not plus-vote them. The 23417 itself, as it appears, someone added EXTENDED_TESTS=1, which is known to have problems, the extended tests simply do not pass in the CI

[vpp-dev] request review

Can I nudge someone here to please review: https://gerrit.fd.io/r/c/vpp/+/23490 https://gerrit.fd.io/r/c/vpp/+/23521 They were added some 10 days ago to help Sunitha along with her failing job. https://gerrit.fd.io/r/c/vpp/+/23417 Latest logs here:

Re: [vpp-dev] Failover not working on X520 NIC with ixgbevf driver

Hi Greg, With out setting a breakpoint on this, I would naively try two things. I would try a more recent version of VPP and without the VM To see if the behavior is still the same and provide some clues. Ray K On 27/11/2019 11:52, Greg O'Rawe wrote: > Hi, > >   > > I have the following

[vpp-dev] Good LACP packets giving "error-drop" statistics

We are using LACP and it works fine except that the "error-drop" statistics are increased for each LACP packet that arrives. We see this behavior both for VPP 19.08 and for the current master branch. Here is an example of a packet trace for a LACP packet: 00:00:16:717846: rdma-input rdma:

Re: [vpp-dev] NAT stops processing for big amount of users

Thanks, I'll wait for your fix. I think using NAT with VPP will be mo' better than iptables/nftables. Best regards, Yurii От: Filip Varga -X (fivarga - PANTHEON TECH SRO at Cisco) Отправлено: 27 ноября 2019 г. 12:39 Кому: format_...@outlook.com ;

[vpp-dev] Coverity run FAILED as of 2019-11-27 14:02:37 UTC

Coverity run failed today. Current number of outstanding issues are 1 Newly detected: 0 Eliminated: 1 More details can be found at https://scan.coverity.com/projects/fd-io-vpp/view_defects -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14714):

[vpp-dev] Failover not working on X520 NIC with ixgbevf driver

Hi, I have the following setup: * Virtual environment with Openstack with Intel X520 NIC * Hypervisor using ixgbe driver * Virtual machine using ixgbevf driver (version 4.6.1) on Red Hat Linux 7.6 running VPP 18.01 and DPDK 17.11.4 * VM interfaces are bonded