Hi everyone
From my experience from using vpp apis in honeycomb,i would like to see
approach that api does not use giant ammount of parameters(ip_add_del_route for
ex.), specialy if that api call defines more than one logical entity,of if
there is too many combinations of use of that api. It al
Hi Alessio,
If you want to extend what I did (with the punt socket.
You need to also start VPP with:
punt { socket }
Then you should see the print messages you added in on the VPP console / cli.
Best regards,
Ole
> On 5 Jun 2017, at 19:49, Alessio Silvestro wrote:
>
> Dear Ole,
>
> In order
The example you cite is not terribly convincing. The only alternative to a
large number of ip route add/del parameters would be a large number of discrete
APIs with considerable parameter overlap.
API messages need handlers, pretty-print functions, and test code; all of which
require maintenan
Hello,
We observed vpp unit test failures during verification of patch
https://gerrit.fd.io/r/#/c/7015/ where the csit operational branch has been
updated - it has no impact to vpp unit test execution. Failures have occurred
on containerised PoC builds as well as on official fd.io JJB builds:
Dear Ole,
when you say
"You need to also start VPP with:
punt { socket }"
do you mean to insert the above line in the /etc/vpp/startup.conf ?
What about the socket. Should I bind it to the NIC I am using for vpp or it
is a generic socket?
Thanks for the help. In case I will let it work I gue
Alessio,
> when you say
>
> "You need to also start VPP with:
> punt { socket }"
>
> do you mean to insert the above line in the /etc/vpp/startup.conf ?
yes, you can do that.
or you can start VPP in the root build directory with: make run
and set the environment variable STARTUP_CONF to point
Hi,
could we bump vpp version in stable/1704 branch
to 17.04.2 in order to match next release version?
Here is patch:
https://gerrit.fd.io/r/#/c/7031/
The reason is to have correct version of jvpp artifacts in nexus (more details
below).
Regards,
Marek
-Original Message-
From: Marek G
Hey all,
When I start vpp using latest code and enter "show features" in CLI in my
server, I got below output,
which is different from the log output by doing "make test".
Is there something I missed?
vpp# sh feat
Available feature paths
nsh-output:
mpls-output:
mpls-input:
ip6-output:
ip6-multi