> On 20 Mar 2017, at 20:25, Jon Loeliger wrote:
>
> Folks,
>
> I am trying to understand a bit more about the "host" interface
> for some AF_PACKET interfaces.
>
> Currently, there is a single API call to create an AF_PACKET interface.
> It simultaneously sets the HW_ADDR (ie, MAC address) of
Hi Keith,
Sorry I forgot to mention earlier
I did create the veth pair using “ip link” and the other end is linked to a
network namespace using netns. I was able to create the host-interface on the
vpp cli using
sh-4.2# vppctl create host-interface veth0-craft0
sh-4.2# vppctl show int
Hi All,
With latest master builds of VPP (on Centos with rpm repo), it seems like
it's necessary to install vpp-plugins package for vpp to start, without it,
I get the following error when running vpp (with default config file):
vlib_plugin_early_init:360: plugin path /usr/lib/vpp_plugins
vlib_ca
Simply remove the “dpdk” stanza from /etc/vpp/startup.conf if you want to run
vpp without the dpdk plugin.
Thanks… Dave
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Feng Pan
Sent: Wednesday, March 22, 2017 1:47 PM
To: vpp-dev
Subject: [vpp-dev] vpp-plugin
Commenting out the dpdk stanza is a great workaround but we may want to
look at bit more closely at the issue... as installing the vpp project
should result in an out of the box runnable vpp.
Ed
On Wed, Mar 22, 2017 at 11:44 AM, Dave Barach (dbarach)
wrote:
> Simply remove the “dpdk” stanza fro
I was tempted to reply to Feng's post that I know what the dependency
relationship is: it is circular. But I remembered
https://www.youtube.com/watch?v=PjIzbvT6Q8c and figured I had better let
others handle this one!
On Wed, Mar 22, 2017 at 2:46 PM, Ed Warnicke wrote:
> Commenting out the dpdk s
So this would suggest that VPP by default (that is, by doing 'yum install
vpp') will not have dpdk support, and vpp-plugins must also be installed to
add it, I would think dpdk plugin should be either packaged or installed
together with VPP by default, and can be disabled if desired.
In any case,
All,
The stable/1704 branch has been pulled and tags have been laid.
Master is now open again for all changes.
With regards to stable/1704 (from the release wiki):
Once we've pulled the 17.04 release throttle
We need to be disciplined with respect to bugfix commits. Here are a few
common-sense
