I'm (like Sara) encoutering exactly the same problems to build sample or newplugin I believe the guide pages are obsolete or the sample code is broken./ is there another recommended process to customize an existing plugin ? For example to take one of the in-tree plugins (under /src/plugins) and make changes there ? I think this is a critical issue - because this is the entry point for VPP newbies.
Best Regards Avi > -----Original Message----- > From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Dave > Barach > Sent: Monday, 05 March, 2018 6:24 PM > To: vpp-dev@lists.fd.io > Cc: vpp-dev@lists.fd.io > Subject: Re: [vpp-dev] How to activate the sample plugins > > You might also need a bit of "autoreconf -if" / "make distclean" action. > > -----Original Message----- > From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Sara Gittlin > Sent: Monday, March 5, 2018 9:49 AM > To: vpp-dev@lists.fd.io > Cc: vpp-dev@lists.fd.io > Subject: Re: [vpp-dev] How to activate the sample plugins > > Thanks Dave > my plugin is called newplugin - I've followed this guide: > > How to create a new plugin > > To create a new plugin based on the sample plugin, copy and rename the > sample plugin directory and automake config. > > cp -r src/examples/sample-plugin/sample src/plugins/newplugin > cp src/examples/sample-plugin/sample.am src/plugins/newplugin.am > > Add the following entry to the plugins section of src/configure.ac. > > PLUGIN_ENABLED(newplugin) > > Add the following entry to the plugins section of src/plugins/Makefile.am > > if ENABLE_NEWPLUGIN > include newplugin.am > endif > > Now (re)build VPP. > > $ make wipe > $ make build > > > On Mon, Mar 5, 2018 at 4:38 PM, Dave Barach <dbar...@cisco.com> wrote: > > If your plugin is called "sample," you meant ENABLE_SAMPLE not > ENABLE_NEWPLUGIN. > > > > -----Original Message----- > > From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Sara > > Gittlin > > Sent: Monday, March 5, 2018 4:07 AM > > To: vpp-dev@lists.fd.io > > Cc: vpp-dev@lists.fd.io > > Subject: Re: [vpp-dev] How to activate the sample plugins > > > > Thank you Dave > > we are progressing > > the root failure is the new sample plugin- the variable 'sample_main' > > (type sample_main_t ) is not defined anywhere > > ------------------- > > load_one_plugin:142: /usr/lib/vpp_plugins/sample_plugin.so: undefined > > symbol: sample_main > > load_one_plugin:143: Failed to load plugin 'sample_plugin.so' > > Aborted > > ------------------------ > > so i set it in sample.c and make build - but then i get build error > > "checking > how to run the C preprocessor... plugins/Makefile.am:78: > > error: ENABLE_NEWPLUGIN does not appear in AM_CONDITIONAL" > > do i have to set an env-var for this newplugin something like > VPP_WITH_NEWPLUGIN=yes ? > > > > Thanks in advance > > -Sara > > > > On Sun, Mar 4, 2018 at 7:09 PM, Dave Barach <dbar...@cisco.com> wrote: > >> Start vpp interactively: > >> > >> # /usr/bin/vpp unix interactive > >> > >> to see if it immediately complains and/or aborts > >> > >> If that's OK, copy /etc/vpp/startup.conf to e.g. /etc/vpp/startup.conf.tmp. > Change "nodaemon" to "interactive" in the copy, and try this: > >> > >> # /usr/bin/vpp -c /etc/vpp/startup.conf.tmp > >> > >> These two experiments should give you lots more info. > >> > >> D. > >> > >> -----Original Message----- > >> From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Sara > >> Gittlin > >> Sent: Sunday, March 4, 2018 11:32 AM > >> To: vpp-dev@lists.fd.io > >> Cc: vpp-dev@lists.fd.io > >> Subject: Re: [vpp-dev] How to activate the sample plugins > >> > >> Thank you Dave > >> i've created a newplugin > >> (https://docs.fd.io/vpp/17.07/sample_plugin_doc.html) > >> and i see the sample plugin .so files under /usr/lib/vpp_plugins, > >> and /usr/lib/vpp_api_test_plugins but vpp start is failed because of > >> clib_socket_init: connect (fd 3, > >> '/run/vpp/cli.sock'): No such file or directory > >> I'm using the default startup.conf which contain the line --- > >> cli-listen /run/vpp/cli.sock --- > >> > >> service vpp status output is : > >> > >> ● vpp.service - vector packet processing engine > >> Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor > >> preset: enabled) > >> Active: failed (Result: signal) since Sun 2018-03-04 11:28:09 EST; 9s > >> ago > >> Process: 18858 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm > /dev/shm/vpe-api (code=exited, status=0/SUCCESS) > >> Process: 18855 ExecStart=/usr/bin/vpp -c /etc/vpp/startup.conf > (code=killed, signal=ABRT) > >> Process: 18852 ExecStartPre=/sbin/modprobe uio_pci_generic > (code=exited, status=0/SUCCESS) > >> Process: 18850 ExecStartPre=/bin/rm -f /dev/shm/db > >> /dev/shm/global_vm /dev/shm/vpe-api (code=exited, status=0/SUCCESS) > >> Main PID: 18855 (code=killed, signal=ABRT) > >> > >> Mar 04 11:28:09 amhost1 systemd[1]: vpp.service: Failed with result > >> 'signal'. > >> Mar 04 11:28:09 amhost1 systemd[1]: vpp.service: Service hold-off time > over, scheduling restart. > >> Mar 04 11:28:09 amhost1 systemd[1]: Stopped vector packet processing > engine. > >> Mar 04 11:28:09 amhost1 systemd[1]: vpp.service: Start request repeated > too quickly. > >> Mar 04 11:28:09 amhost1 systemd[1]: Failed to start vector packet > processing engine. > >> Mar 04 11:28:09 amhost1 systemd[1]: vpp.service: Unit entered failed state. > >> Mar 04 11:28:09 amhost1 systemd[1]: vpp.service: Failed with result > >> 'signal'. > >> > >> Thank in advance > >> -Sara > >> > >> On Wed, Feb 28, 2018 at 2:12 PM, Dave Barach <dbar...@cisco.com> > wrote: > >>> Vpp and vpp_api_test look in specific directories for plugins: > /usr/lib/vpp_plugins, and /usr/lib/vpp_api_test_plugins respectively. You can > set these paths from the command line. > >>> > >>> If your plugin .so files aren't in the right place(s), they won't be > >>> loaded. > >>> > >>> HTH... D. > >>> > >>> -----Original Message----- > >>> From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of > >>> Sara Gittlin > >>> Sent: Wednesday, February 28, 2018 3:46 AM > >>> To: vpp-dev@lists.fd.io > >>> Subject: Re: [vpp-dev] How to activate the sample plugins > >>> > >>> I've build the sample plugin as per guide page > https://docs.fd.io/vpp/17.07/sample_plugin_doc.html . > >>> when i run it I can see than many plugins are loaded but not this > >>> specific > sample plugin (see log below) this guide page applies for vpp v17.07-30- > g839fa73. > >>> my vpp is v18.04-rc0~287-gf9a968e2 > >>> > >>> Can anyone tell me whether to downgrade to vpp v17.07-30 ? other ? > >>> > >>> -------------------------log----------------------------------- > >>> load_one_plugin:184: Loaded plugin: acl_plugin.so (Access Control > >>> Lists) > >>> load_one_plugin:184: Loaded plugin: dpdk_plugin.so (Data Plane > >>> Development Kit (DPDK)) > >>> load_one_plugin:184: Loaded plugin: flowprobe_plugin.so (Flow per > >>> Packet) > >>> load_one_plugin:184: Loaded plugin: gbp_plugin.so (Group Based > >>> Policy) > >>> load_one_plugin:184: Loaded plugin: gtpu_plugin.so (GTPv1-U) > >>> load_one_plugin:184: Loaded plugin: ila_plugin.so > >>> (Identifier-locator addressing for IPv6) > >>> load_one_plugin:184: Loaded plugin: ioam_plugin.so (Inbound OAM) > >>> load_one_plugin:114: Plugin disabled (default): ixge_plugin.so > >>> load_one_plugin:184: Loaded plugin: kubeproxy_plugin.so (kube-proxy > >>> data plane) > >>> load_one_plugin:184: Loaded plugin: l2e_plugin.so (L2 Emulation) > >>> load_one_plugin:184: Loaded plugin: lb_plugin.so (Load Balancer) > >>> load_one_plugin:184: Loaded plugin: libsixrd_plugin.so (IPv6 Rapid > >>> Deployment on IPv4 Infrastructure (RFC5969)) > >>> load_one_plugin:184: Loaded plugin: memif_plugin.so (Packet Memory > >>> Interface (experimetal)) > >>> load_one_plugin:184: Loaded plugin: nat_plugin.so (Network Address > >>> Translation) > >>> load_one_plugin:184: Loaded plugin: pppoe_plugin.so (PPPoE) > >>> load_one_plugin:184: Loaded plugin: srv6ad_plugin.so (Dynamic SRv6 > >>> proxy) > >>> load_one_plugin:184: Loaded plugin: srv6am_plugin.so (Masquerading > >>> SRv6 proxy) > >>> load_one_plugin:184: Loaded plugin: srv6as_plugin.so (Static SRv6 > >>> proxy) > >>> load_one_plugin:184: Loaded plugin: stn_plugin.so (VPP Steals the > >>> NIC for Container integration) > >>> vnet_feature_arc_init:205: feature node 'acl-plugin-out-ip6-fa' not > >>> found > >>> vnet_feature_arc_init:205: feature node 'acl-plugin-out-ip4-fa' not > >>> found > >>> load_one_plugin:63: Loaded plugin: > >>> /usr/lib/vpp_api_test_plugins/ioam_trace_test_plugin.so > >>> load_one_plugin:63: Loaded plugin: > >>> /usr/lib/vpp_api_test_plugins/stn_test_plugin.so > >>> load_one_plugin:63: Loaded plugin: > >>> /usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plugin.so > >>> load_one_plugin:63: Loaded plugin: > >>> /usr/lib/vpp_api_test_plugins/memif_test_plugin.so > >>> load_one_plugin:63: Loaded plugin: > >>> /usr/lib/vpp_api_test_plugins/kubeproxy_test_plugin.so > >>> load_one_plugin:63: Loaded plugin: > >>> /usr/lib/vpp_api_test_plugins/acl_test_plugin.so > >>> load_one_plugin:63: Loaded plugin: > >>> /usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so > >>> load_one_plugin:63: Loaded plugin: > >>> /usr/lib/vpp_api_test_plugins/lb_test_plugin.so > >>> load_one_plugin:63: Loaded plugin: > >>> /usr/lib/vpp_api_test_plugins/ioam_export_test_plugin.so > >>> load_one_plugin:63: Loaded plugin: > >>> /usr/lib/vpp_api_test_plugins/ioam_pot_test_plugin.so > >>> load_one_plugin:63: Loaded plugin: > >>> /usr/lib/vpp_api_test_plugins/vxlan_gpe_ioam_export_test_plugin.so > >>> load_one_plugin:63: Loaded plugin: > >>> /usr/lib/vpp_api_test_plugins/gtpu_test_plugin.so > >>> load_one_plugin:63: Loaded plugin: > >>> /usr/lib/vpp_api_test_plugins/pppoe_test_plugin.so > >>> load_one_plugin:63: Loaded plugin: > >>> /usr/lib/vpp_api_test_plugins/nat_test_plugin.so > >>> load_one_plugin:63: Loaded plugin: > >>> /usr/lib/vpp_api_test_plugins/flowprobe_test_plugin.so > >>> load_one_plugin:63: Loaded plugin: > >>> /usr/lib/vpp_api_test_plugins/udp_ping_test_plugin.so > >>> > >>> Thanks in advance > >>> - Sara > >>> > >>> On Wed, Feb 28, 2018 at 7:57 AM, Sara Gittlin <sara.gitt...@gmail.com> > wrote: > >>>> Hello All, > >>>> Resending this -my last mail was broken by other issues I'm a vpp > >>>> newbei. > >>>> I want to activate some existing plugins - i see that many of them > >>>> are loaded (e.g, acl, flowprob ) but I cannot activate them. > >>>> another question is - I understand that i can customize the code > >>>> of these plugins examples - correct ? > >>>> > >>>> Thank you in advance > >>>> - Sara > >>> > >>> > >>> > >>> > >>> > >>> > >> > >> > >> > >> > >> > >> > > > > > > > > > > > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8409): https://lists.fd.io/g/vpp-dev/message/8409 View All Messages In Topic (11): https://lists.fd.io/g/vpp-dev/topic/13267098 Mute This Topic: https://lists.fd.io/mt/13267098/21656 New Topic: https://lists.fd.io/g/vpp-dev/post Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656 Group Home: https://lists.fd.io/g/vpp-dev Contact Group Owner: vpp-dev+ow...@lists.fd.io Terms of Service: https://lists.fd.io/static/tos Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub -=-=-=-=-=-=-=-=-=-=-=-
