Hi,
We are trying you integrate FDIO unittest framework into our product.
Basically we have built some custom plugins and integrated those as VPP
plugins. We have our build environment where VPP is built including these
custom plugins. When we launch VPP inside our cluster it is working fine.
Hi,
> * I'm working on a plugin development,does anyone know how to share a
> global variable between two plugins?Thank you very much.
You can use vlib_get_plugin_symbol() to load an exported symbol from another
plugin.
Best
ben
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent
*
I'm working on a plugin development,does anyone know how to share a global
variable between two plugins?Thank you very much.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21190): https://lists.fd.io/g/vpp-dev/message/21190
Mute This Topic: htt
Awesome, It works.
Great job. many thanks to you.
Regards
Petr
st 26. 5. 2021 v 22:02 odesílatel Matthew Smith
napsal:
>
> Hi Petr,
>
> My earlier statement that multicast should work with no additional
> configuration required was wrong. That's only true if you have the netlink
> listener
Hi Petr,
My earlier statement that multicast should work with no additional
configuration required was wrong. That's only true if you have the netlink
listener patch (https://gerrit.fd.io/r/c/vpp/+/31122) applied. I have that
applied to my local builds and I incorrectly thought it was part of the
Hi,
thank you . answers are inline below.
Predispositions
The host is apu4d4 + Debian 10.9 + bird 1.66 (old, but in repo), clear
install + VPP 21.06-rc1~0-ge82d59f38~b1 (10.10.50.1/24). The opposite side
is MikroTik rb4011 (10.10.50.2/24). There is no disabled plugins, only
enabled linux-cp.
Hi Petr,
Responses are inline...
On Wed, May 26, 2021 at 10:23 AM wrote:
> Hello,
>
> I'm sorry for the beginner question, but I was unable to find the answer.
> I tested the linux-cp feature in VPP 21.10-rc0. Nice job, but I cannot get
> to work ospf multicast, probably I'm doing something wro
Hello,
I'm sorry for the beginner question, but I was unable to find the answer. I
tested the linux-cp feature in VPP 21.10-rc0. Nice job, but I cannot get to
work ospf multicast, probably I'm doing something wrong, or should it work?
BGP communication works fine (tcp), OSPF NBMA works fine.
Co
Hi Alex,
In order to drop some packets while passing all others on to the next node
in the feature arc, you can use vnet_feature_next(). It will find the index
of the next node on the feature arc and populate it into a pointer that you
pass in. The next_nodes in your node declaration ( .next_node
Hello, VPP developers.
I can't understand how to write plugin to filter some packets and
passing others.
I need to hook on some feature graph, check every packet and remove matched.
I bound required IP for interface, hooked arc "ip4-local" (it can also
be "ip4-unicast") with my node "checker"
Hi Team,
We developed a plugin in VPP to read data from a physical interface and forward
to our application,
Packet 2
*03:03:45:254785: dpdk-input*
*HundredGigabitEthernet12/0/0 rx queue 0*
buffer 0x1f3a68: current data 0, length 114, buffer-pool 0, ref-count 1,
totlen-nifb 132, trace handle 0x
packets are received. “show
run” on VPP does not show me any clue yet.
Thanks much!
Hemant
From: Stanislav Zaikin
Sent: Tuesday, March 02, 2021 12:29 PM
To: hem...@mnkcg.com
Cc: vpp-dev
Subject: Re: [vpp-dev] plugin tracing?
Hi Hemant,
Try something like this:
trace filter
Hi Hemant,
Try something like this:
trace filter include upf6 100
trace add dpdk-input 100
dpdk-input for regular dpdk interfaces, virtio-input for tap/virtio
interfaces, memif-input for memif interfaces.
On Tue, 2 Mar 2021 at 19:58, hemant via lists.fd.io wrote:
> Is this how a plugin enables
Is this how a plugin enables tracing?
vpp# trace filter include upf6 5
I don't see any packets with this trace yet.
Is it possible to add trace code to a plugin to support per-node trace?
vpp# trace add upf6 5
trace add: node 'upf6' doesn't support per-node tracing.
[Edited Message Follows]
Hi Team,
We developed a plugin and forwarding packets to several interfaces depending on
some filtering rules.
Now we have a requirement to create these filtering rules from Host
Application. We have a problem to use VPPCOM/Binary API.
DO we have any communication method
Hi Team,
We developed a plugin and forwarding packets to several interfaces depending on
some filtering rules.
Now we have a requirement to create these filtering rules from Host
Application. We have a problem to use VPPCOM/Binary API.
DO we have any communication method from HOSTAPP to VPP Plugi
> On 22.11.2020., at 15:28, palluhe...@gmail.com wrote:
>
> Hi,
>
> I am experimenting with VPP on CentOS-7 Virtual Machine (vpp binaries
> installed with yum install command - version 20.09). I have installed
> vpp-devel package. Now, I am trying to build the sample code in
> /usr/share/do
Hi,
I am experimenting with VPP on CentOS-7 Virtual Machine (vpp binaries installed
with yum install command - version 20.09). I have installed vpp-devel package.
Now, I am trying to build the sample code in /usr/share/doc/vpp/examples/.
But I am not able to proceed with the code build part. Is
Hi,
I've created a timestamp plugin to stamp all packets being received prior to
the ethernet-input node. The problem I'm seeing, based on debug prints I've
inserted into VLIB_NODE_FN (timestamp_node), is that my plugin node is running
way way after any other node (seconds). I have similar pr
Hi all,
I am trying to build some API client code against a copy of the
master branch I pulled a couple of days ago (ee74376 ip: refactor ip4_mtrie
to use atomic store-release). It seems like some required headers are not
getting installed for plugins.
E.g. - the LACP plugin header lacp.api.h has
>> Sorry. Let me try again.
>>
>> The semver definition seems to say that backend changes that don't change
>> the API, still should have the patch version increased.
>> Bug fixes not affecting the API increment the patch version
>> New features would either be backward compatible with the API or
> We have plugins which doesn’t expose any APIs
Then why do we track version numbers for such plugins?
Vratko.
From: Damjan Marion
Sent: Monday, 2019-May-27 13:56
To: Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco)
Cc: Paul Vinciguerra ; vpp-dev@lists.fd.io
Subject: Re: [vpp-
> On 27 May 2019, at 13:54, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at
> Cisco) via Lists.Fd.Io wrote:
>
> SemVer says:
> > Patch version Z (x.y.Z | x > 0) MUST be incremented if only backwards
> > compatible bug fixes are introduced.
> > A bug fix is defined as an internal change th
nt: Saturday, 2019-May-25 19:46
To: Paul Vinciguerra
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Plugin Versions
On 25 May 2019, at 18:42, Paul Vinciguerra
mailto:pvi...@vinciconsulting.com>> wrote:
Sorry. Let me try again.
The semver definition seems to say that backend changes th
> On 25 May 2019, at 18:42, Paul Vinciguerra wrote:
>
> Sorry. Let me try again.
>
> The semver definition seems to say that backend changes that don't change the
> API, still should have the patch version increased.
> Bug fixes not affecting the API increment the patch version
> New features
Sorry. Let me try again.
The semver definition seems to say that backend changes that don't change
the API, still should have the patch version increased.
> Bug fixes not affecting the API increment the patch version
New features would either be backward compatible with the API or not,
therefore
> On 25 May 2019, at 13:43, Paul Vinciguerra wrote:
>
> Hi Damian,
>
> That's what I initially thought as well. The semver doc says:
> For this system to work, you first need to declare a public API. This may
> consist of documentation or be enforced by the code itself. Regardless, it is
>
Hi Damian,
That's what I initially thought as well. The semver doc says:
>
> For this system to work, you first need to declare a public API. This may
> consist of documentation or be enforced by the code itself. Regardless, it
> is important that this API be clear and precise. Once you identi
if plugin code didn’t change there is no reason to bump api version, on other
side plugin version needs to change as it is linked against different core
libraries….
> On 25 May 2019, at 03:57, Paul Vinciguerra wrote:
>
> Is there any reason for having plugin versions that are distinct from t
Is there any reason for having plugin versions that are distinct from their API
versions?
If not, is there any objection to having api's such as
abf_plugin_get_version_reply return the semver[1] of the api?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply O
Ping Dave, as I'm sure he knows what could help here.
Justin
> Hi folks,
>
> After having developed a new plugin, I'm now implementing its API in order to
> use it from a GUI.
>
> Is there an official documentation of the API grammar (other than inside
> vppapigen) ? By looking at the code, I a
Hi folks,
After having developed a new plugin, I'm now implementing its API in order to
use it from a GUI.
Is there an official documentation of the API grammar (other than inside
vppapigen) ? By looking at the code, I already found that it's possible to
include a structure in a request/respon
I was looking at the lb plugins, and had some basic questions.
https://docs.fd.io/vpp/17.07/lb_plugin_doc.html
1. Other than load balancer node that need to setup VPP (+ lb plugin), is
VPP setup needed on the backend servers and client machines?
2. On the VPP load balancer node, is separate NIC car
...@lists.fd.io] On
Behalf Of
Sent: Friday, September 15, 2017 10:46
To: vpp-dev
Subject: [vpp-dev] plugin compile error
Hi, everyone:
I writed a new plugin. When i make this plugin, all the *.o files have made.
But in the end, it outputs the contents as follow:
make all-am
make[1]: Entering
Hi, everyone:
I writed a new plugin. When i make this plugin, all the *.o files have made.
But in the end, it outputs the contents as follow:
make all-am
make[1]: Entering directory `/home/plugins/myplugin'
API
at line 1ken
(null):1 syntax error
Removing myplugin.api.json
make[1]: ***
ld be
> necessary.
>
> Thanks... Dave
>
> -Original Message-
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
> Behalf Of Ratliff, Stanley
> Sent: Sunday, June 11, 2017 10:24 PM
> To: vpp-dev@lists.fd.io
> Subject: [vpp-dev] Plugin ques
ould be necessary.
Thanks... Dave
-Original Message-
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Ratliff, Stanley
Sent: Sunday, June 11, 2017 10:24 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Plugin question
Hello,
I'm trying to write a VPP
Hello,
I'm trying to write a VPP plugin. This plugin needs to be able to consume
packets from a vector - e.g., my plugin gets a frame with 10 buffers, and
when I pass the frame along via vlib_put_next_frame (if that's the right
call), there would be only 9 buffers in the frame. Actually, I
Damjan,
This looks good to me and I think it an improvement over the existing
mechanism.
Thanks,
-daw-
ps. I noticed a typo in the commit comment: s/will nor be/will not be/g
On 1/24/17 12:10 PM, Damjan Marion (damarion) wrote:
As discussed on the call, let’s continue discussion on the mail
As discussed on the call, let’s continue discussion on the mailer.
My RFC patch is at: https://gerrit.fd.io/r/#/c/4824/
copy/paste from commit log:
==
This patch replaces requirement for vlib_plugin_register function
in the plugin so file and introduces new macro:
VLIB_PLUGIN_REGISTER () =
>
> So to achieve MPLS-o-UDP one approach would be to follow this model and
> create a UDP-o-IPv[46] tunnel.
>
>
>
> Regards,
>
> neale
>
>
>
>
>
>
>
> *From: * on behalf of Calvin Ference <
> cfere...@inocybe.ca>
> *Date: *Thursday, 19 Jan
MPLS-o-UDP one approach would be to follow this model and create
a UDP-o-IPv[46] tunnel.
Regards,
neale
From: on behalf of Calvin Ference
Date: Thursday, 19 January 2017 at 00:32
To: "Damjan Marion (damarion)"
Cc: vpp-dev
Subject: Re: [vpp-dev] Plugin for mpls over gre
Actually,
Actually, MPLS over UDP has been asked by some of our clients, so that
would be perfect. Any assistance would be much appreciated, Ed.
Cheers
On 18 January 2017 at 16:42, Damjan Marion (damarion)
wrote:
>
> > On 18 Jan 2017, at 22:39, Ed Warnicke wrote:
> >
> > Calvin,
> >
> > We've had some c
> On 18 Jan 2017, at 22:39, Ed Warnicke wrote:
>
> Calvin,
>
> We've had some consumers express interest in MPLS over UDP:
> https://tools.ietf.org/html/rfc7510
>
> Would you be interested in working on that?
Or maybe, https://tools.ietf.org/html/rfc2549 . :)
Calvin let us know if you need
Calvin,
We've had some consumers express interest in MPLS over UDP:
https://tools.ietf.org/html/rfc7510
Would you be interested in working on that?
Ed
On Wed, Jan 18, 2017 at 2:37 PM, Damjan Marion (damarion) <
damar...@cisco.com> wrote:
>
>
>
> > On 18 Jan 2017, at 16:59, Calvin Ference wrot
> On 18 Jan 2017, at 16:59, Calvin Ference wrote:
>
> Hey VPP community,
>
> I was wondering if anyone had coded a plugin to do mpls over gre before? I'm
> looking at getting my hands dirty in writing a plugin and I was thinking this
> might be a good start, but if someone already did the
Hey VPP community,
I was wondering if anyone had coded a plugin to do mpls over gre before?
I'm looking at getting my hands dirty in writing a plugin and I was
thinking this might be a good start, but if someone already did the work
I'll find something else.
Regards
Calvin
__
47 matches
Mail list logo
