Hi list,
Could you please advice a simple way to get VPP deb packages with all debug
info?
I am trying this change:
diff --git a/build-data/platforms/vpp_lite.mk b/build-data/platforms/
vpp_lite.mk
index 81ba90d..f9ee550 100644
--- a/build-data/platforms/vpp_lite.mk
+++
Thanks for confirming Billy and Thomas.
Could you also check regarding link bonding (whether deployments use link
bonding).
A single tenant interface + bonding (which means 2 phys interfaces bonded) will
exercise the bonding code in dpdk for the egress traffic..
This will also dictate the spec
Ray,
The reason is because vagrant produces a bunch of 'issues' when trying to
build from a 'mounted' share.
When running vagrant, /vpp gets mounted with where ever the source is
*outside* the vagrant VM
Once inside, if you try to build from /vpp, a variety of things can and do
break sadly :(
Hello,
Issue with VIRL servers is fixed (and small correction that should avoid such
issue in the future applied) and vpp-csit-verify job can be run now.
Recheck was applied on following affected patches:
https://gerrit.fd.io/r/#/c/4267/1
https://gerrit.fd.io/r/#/c/4197/2
On 12/13/2016 07:53 AM, Billy McFall wrote:
I consulted with some of my Red Hat colleagues (primarily ODL
developers) and they agree that the typical deployment they have seen
is with one interface, not two.
+1
Billy McFall
On Tue, Dec 13, 2016 at 2:27 AM, Pierre Pfister (ppfister)
Hi,
I noticed that tag field is not present in the tap_modify/modify_vhost_user_if
message, but is present in tap_connect/create_vhost_user_if.
Does it mean tag is meant to be unmodifiable, or value is missing because of
oversight?
Regards,
Marek
I had manually set flags=0x8 to get scapy + vpp to work correctly also.
Might be something to fix in Scapy and upstream?
Ray K
On 09/12/2016 19:34, Matej Klotton -X (mklotton - PANTHEON TECHNOLOGIES
at Cisco) wrote:
My understanding is, if is VXLAN then UDP destination port is 4789 and
must
