Wishes often come true when you turn them into patches. :)
Chris.
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Burt Silverman
Sent: Saturday, May 27, 2017 10:33
To: Kinsella, Ray
Cc: Alessio Silvestro ; vpp-dev
Subject: Re: [vpp-dev] VPP/How To Build The
Thanks, Ray, this is exactly what I needed, by coincidence. I wish your
item 2. was placed commented out and almost word for word into the standard
$TOPDIR/src/vpp/conf/startup.conf -- that would make things self
documenting.
Burt
On Sat, May 27, 2017 at 8:30 AM, Kinsella, Ray
wrote:
> So there
So there is an easier way
1. make -C build-root PLATFORM=vpp TAG=vpp sample-plugin-install
2. adjusting the plugin path depending on where the VPP src is, add the
following to your startup.conf
plugins
{
path
/root/src/vpp/build-root/install-vpp-native/sample-plugin/lib64/vpp_plugins
Hi Xyxue,
One issue at a time please ☺ let’s start with getting L3VPN to work correctly.
Please describe what the 3 flows are that we you discussing;
- Fade flow
- Ip4 flow
- Mpls flow
Describe, as in what headers they have, addressing etc.
The IP chksum will change
Hi neale,
The ping we were debugging now work.'Bi-directional flow 'is the fade flow send
by tester.
I'm sure I patched and recompiled the DEBUG version of VPP on both ‘PE’s’.
The phenomenon :When there is ip4 flow ,nothing wrong with it.when there is
mpls flow ,the checksum come out is not th
Hi Xxyue,
Can you please be more specific about what is working and was is not. Does the
ping we were debugging previously now work?
What is this ‘bi-directional flow’ you speak of, if it is not the ping.
Those asserts could be related to:
https://gerrit.fd.io/r/#/c/6883/
I saw them, whilst debu
