Re: [vpp-dev] VPP SSWAN plugin git cherry pick to stable 22.10

Hi Andrew, cherry-pick for stable/2210: https://gerrit.fd.io/r/c/vpp/+/37413 Thanks Yulong Pei From: Andrew 👽 Yourtchenko Sent: Tuesday, October 18, 2022 1:58 PM To: Pei, Yulong Cc: vpp-dev@lists.fd.io; Andrew Yourtchenko (ayourtch) ; Ji, Kai ; Zhang, Roy Fan ; Oginski, GabrielX Subject:

Re: [vpp-dev] VPP SSWAN plugin git cherry pick to stable 22.10

Hi Yulong, Cool, thanks! Then could you please make a cherry-pick into stable/2210 branch, and add me as a reviewer ? I will merge it. --a > On 18 Oct 2022, at 03:51, Pei, Yulong wrote: > >  > Hi Andrew, > > I have been working on CSIT IPSec test for a long time, CSIT IPSec test use > VP

Re: [vpp-dev] Move VNET features to plugins

Hi Dave, I fully support pluginification 😊 Is it fair though to say that if the remaining functions of vnet have a dependency on one of the modules below then that module is not a good candidate to move to a plugin? I thinking about the dependency between IPIP and TEIB. Some of the IPIP functi

Re: [vpp-dev] VPP SSWAN plugin git cherry pick to stable 22.10

Hi Andrew, I have been working on CSIT IPSec test for a long time, CSIT IPSec test use VPP python API for configuration, “SSWAN plugin https://gerrit.fd.io/r/c/vpp/+/36552” have no impact for CSIT IPSec test since it is only plugin for strongswan, and it do not build by defaut when building V

Re: [vpp-dev] pcap_write error: bad address

hi Dave： I have been  gdb before，  vl(pm->pcap_data)    =   2,806,013,189， pm->n_pcap_data_written  = 0. int  is 32 bits,size_t  is 64 bits.  n=0xA740 5D05   cast to size_t  is  0x A740 5D05. we can't use  n for   write  param. code  fragment： int n = vec_len (pm->pcap_data) - pm->n_pc

[vpp-dev] Move VNET features to plugins

Folks, There has been a long standing chore to move VNET features to plugins for which I've created a Jira ticket [0] to coordinate getting this work done for VPP 23.02 release. Can the maintainers of the VNET features [1] please sign up for the associated subtask in [0] and complete the wor

Re: [vpp-dev] pcap_write error: bad address #pcap

Use gdb to inspect the pcap_main_t. In particular, determine vec_len(pm->pcap_data) [“(gdb) vl(pm->pcap_data)”] and pm->n_pcap_data_written. For reasonable N pcap_write(...) is known to work. D. From: vpp-dev@lists.fd.io On Behalf Of aihua1...@163.com Sent: Sunday, October 16, 2022 11:2