date:20170328

Re: [vpp-dev] Building router plugin

2017-03-28 Thread Ni, Hongjun

Thanks Dave.  Will look into it.

From: Dave Barach (dbarach) [mailto:dbar...@cisco.com]
Sent: Tuesday, March 28, 2017 7:52 PM
To: Ni, Hongjun ; Ed Warnicke ; Lukasz 
Chrustek 
Cc: Shaw, Jeffrey B ; Damjan Marion (damarion) 
; vpp-dev@lists.fd.io; Lukasz Chrustek 
Subject: RE: [vpp-dev] Building router plugin

FWIW: I sent diffs to fix the build-system integration over the weekend, as 
well as a fair fraction of the FIB 2.0 integration...

Thanks… Dave

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Ni, Hongjun
Sent: Monday, March 27, 2017 10:32 PM
To: Ed Warnicke mailto:hagb...@gmail.com>>; Lukasz Chrustek 
mailto:ski...@tlen.pl>>
Cc: Shaw, Jeffrey B 
mailto:jeffrey.b.s...@intel.com>>; Damjan Marion 
(damarion) mailto:damar...@cisco.com>>; 
vpp-dev@lists.fd.io; Lukasz Chrustek 
mailto:luk...@chrustek.net>>
Subject: Re: [vpp-dev] Building router plugin

Hi Luk,

We are using netlink and router plugin in VPP stable 17.01, and also met the 
same issue.

I have submitted a patch to fix a compile issue in netlink for review, now 
netlink could compile ok in VPP stable 17.01.
https://gerrit.fd.io/r/#/c/5881/ FIx compile issue for netlink

I am working on router plugin now, hope to address some issues and make it work 
again in VPP stable 17.01.

For VPP 17.04, make file may need to be changed as per new building system.

Regards,
Hongjun

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Ed Warnicke
Sent: Tuesday, March 28, 2017 6:10 AM
To: Łukasz Chrustek mailto:ski...@tlen.pl>>
Cc: Damjan Marion (damarion) mailto:damar...@cisco.com>>; 
Lukasz Chrustek mailto:luk...@chrustek.net>>; 
vpp-dev@lists.fd.io; Shaw, Jeffrey B 
mailto:jeffrey.b.s...@intel.com>>
Subject: Re: [vpp-dev] Building router plugin

You might also look at

https://gerrit.fd.io/r/#/c/5004/ - which introduces memif interfaces... which I 
think Damjan eventually wants a library for so that you could
use them for things like taps for routing protocol packets...

Ed

On Mon, Mar 27, 2017 at 2:43 PM, Łukasz Chrustek 
mailto:ski...@tlen.pl>> wrote:
Hi,

Ok,  thank You. I will give a try with earlier version of vpp, as Jeff
suggests.  I  have  running  netlink  plugin,  but as Ole wrote - most
important is router plugin.

Cheers,
Luk

>> You basically have two options:
>> 1. Teach your routing protocol daemon to directly talk to VPP for 
>> configuring the FIB.
>> 2. Do not modify the routing daemon and let VPP map routes written in the 
>> kernel.
>>
>> For 1, you will need the router plugin, but for packet punting only.
>>
>> For 2., you will need both netlink+router plugins. The netlink plugin (which 
>> actually more like a library), shouldn't require so much changes though.

> With TCP support in VPP I was playing with the idea of integrating exaBGP as 
> a VPP plugin.
> Use the Python API binding to program routes, and receive the BGP
> stream across a fifo (or even the API).

> Cheers,
> Ole

>>> Le 26 mars 2017 à 16:31, Łukasz Chrustek 
>>> mailto:ski...@tlen.pl>> a écrit :
>>>
>>> Hello,
>>>
>>> thank all of You for clarification of status router plugin.
>>>
>>> I'm trying to use vpp+dpdk as bare metal linux ruter with bgp and ospf 
>>> routing protocols, goal is to make very fast router with dynamic routing 
>>> protocols. Can You advice is there any other way to exchange dynamic 
>>> routing information between os and vpp ?
>>>
>>> Regards
>>> Lukasz
>>>
>>>
>>> The mailman did not let my last message go through because it was too big 
>>> so I am removing the previous threads to keep this message under 100KB 
>>> limit.
>>>
>>> Hello,
>>>
>>> Dave and Pierre are correct, the router plugin is no longer being 
>>> maintained. There was not much interest in the community for this project 
>>> at the time and I have since moved on to other things.  I’d be happy to 
>>> help a new maintainer with any questions they may have.
>>>
>>> If you really want to just test it out, I suggest attempting to checkout a 
>>> commit of VPP close to the last commit on the router plugin. Somewhere 
>>> closely following VPP commit 0bfe5d8c792abcdb, “A Protocol Independent 
>>> Hierarchical FIB (VPP-352)” will work (you might have to git bisect to get 
>>> something that compiles right away).
>>>
>>> If necessary, I can submit a patch to remove the router plugin from the VPP 
>>> sandbox with a note on the wiki page mentioning the finalization of the 
>>> project. I recall there being an 8-month time limit for these the sandbox 
>>> projects.
>>>
>>> -Jeff
>>>
>>>
>>>
>>
>> ___
>> vpp-dev mailing list
>> vpp-dev@lists.fd.io
>> https://lists.fd.io/mailman/listinfo/vpp-dev

--
Pozdrowienia,
 Łukasz Chrustek

___
vpp-dev mailing list
vpp-dev@lists.fd.io<

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

2017-03-28 Thread Florin Coras

Hi Cristian, 

Did you try:

sudo apt-get remove —purge vpp

Florin

> On Mar 28, 2017, at 3:23 PM, Dumitrescu, Cristian 
>  wrote:
> 
> Hi Florin,
>  
> I actually removed the old git clone and created a brand new one just before 
> I started getting this error.
>  
> We are potentially considering some leftover files from previous installation 
> somewhere in the file system, if there is such possibility for VPP?
>  
> Regards,
> Cristian
>   <>
>  <>From: Florin Coras [mailto:fcoras.li...@gmail.com] 
> Sent: Tuesday, March 28, 2017 10:12 PM
> To: Dumitrescu, Cristian 
> Cc: Burt Silverman ; vpp-dev 
> Subject: Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS
>  
> Hi Cristian, 
>  
> Did you try cleaning everything up? 
>  
> git clean -fdx 
> make bootstrap 
> ..
>  
> HTH,
> Florin
>  
> On Mar 28, 2017, at 1:28 PM, Dumitrescu, Cristian 
> mailto:cristian.dumitre...@intel.com>> wrote:
>  
> Hi Burt,
>  
> No network connectivity issues I am afraid. I pasted the output of my last 
> re-run of “make install-dep” in the previous email.
>  
> Regards,
> Cristian
>  
> From: Burt Silverman [mailto:bur...@gmail.com ] 
> Sent: Tuesday, March 28, 2017 5:47 PM
> To: Dumitrescu, Cristian  >
> Cc: vpp-dev mailto:vpp-dev@lists.fd.io>>
> Subject: Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS
>  
> Also, the fact that we saw PKG_CHECK_MODULES appear in your original output 
> tells me that pkg-config was not installed when your configure was running. 
> Otherwise, I believe it would have been macro expanded and you'd only see the 
> expanded form. The mystery remains about your "make install-dep" not working. 
> Is it possible that there is a network connectivity issue, and a related 
> error message but the error message did not stick out clearly?
> 
> Baffled Burt
> 
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io 
> https://lists.fd.io/mailman/listinfo/vpp-dev 
> 
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

2017-03-28 Thread Dumitrescu, Cristian

Hi Florin,

I actually removed the old git clone and created a brand new one just before I 
started getting this error.

We are potentially considering some leftover files from previous installation 
somewhere in the file system, if there is such possibility for VPP?

Regards,
Cristian

From: Florin Coras [mailto:fcoras.li...@gmail.com]
Sent: Tuesday, March 28, 2017 10:12 PM
To: Dumitrescu, Cristian 
Cc: Burt Silverman ; vpp-dev 
Subject: Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

Hi Cristian,

Did you try cleaning everything up?

git clean -fdx
make bootstrap
..

HTH,
Florin

On Mar 28, 2017, at 1:28 PM, Dumitrescu, Cristian 
mailto:cristian.dumitre...@intel.com>> wrote:

Hi Burt,

No network connectivity issues I am afraid. I pasted the output of my last 
re-run of “make install-dep” in the previous email.

Regards,
Cristian

From: Burt Silverman [mailto:bur...@gmail.com]
Sent: Tuesday, March 28, 2017 5:47 PM
To: Dumitrescu, Cristian 
mailto:cristian.dumitre...@intel.com>>
Cc: vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

Also, the fact that we saw PKG_CHECK_MODULES appear in your original output 
tells me that pkg-config was not installed when your configure was running. 
Otherwise, I believe it would have been macro expanded and you'd only see the 
expanded form. The mystery remains about your "make install-dep" not working. 
Is it possible that there is a network connectivity issue, and a related error 
message but the error message did not stick out clearly?
Baffled Burt

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

2017-03-28 Thread Florin Coras

Hi Cristian, 

Did you try cleaning everything up? 

git clean -fdx 
make bootstrap 
..

HTH,
Florin

> On Mar 28, 2017, at 1:28 PM, Dumitrescu, Cristian 
>  wrote:
> 
> Hi Burt,
>  
> No network connectivity issues I am afraid. I pasted the output of my last 
> re-run of “make install-dep” in the previous email.
>  
> Regards,
> Cristian
>   <>
>  <>From: Burt Silverman [mailto:bur...@gmail.com] 
> Sent: Tuesday, March 28, 2017 5:47 PM
> To: Dumitrescu, Cristian 
> Cc: vpp-dev 
> Subject: Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS
>  
> Also, the fact that we saw PKG_CHECK_MODULES appear in your original output 
> tells me that pkg-config was not installed when your configure was running. 
> Otherwise, I believe it would have been macro expanded and you'd only see the 
> expanded form. The mystery remains about your "make install-dep" not working. 
> Is it possible that there is a network connectivity issue, and a related 
> error message but the error message did not stick out clearly?
> 
> Baffled Burt
> 
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

2017-03-28 Thread Dumitrescu, Cristian

Hi Burt,

No network connectivity issues I am afraid. I pasted the output of my last 
re-run of “make install-dep” in the previous email.

Regards,
Cristian

From: Burt Silverman [mailto:bur...@gmail.com]
Sent: Tuesday, March 28, 2017 5:47 PM
To: Dumitrescu, Cristian 
Cc: vpp-dev 
Subject: Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

Also, the fact that we saw PKG_CHECK_MODULES appear in your original output 
tells me that pkg-config was not installed when your configure was running. 
Otherwise, I believe it would have been macro expanded and you'd only see the 
expanded form. The mystery remains about your "make install-dep" not working. 
Is it possible that there is a network connectivity issue, and a related error 
message but the error message did not stick out clearly?
Baffled Burt

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

2017-03-28 Thread Dumitrescu, Cristian

Hi Burt,

Thanks for your hints.

Here is the output of “dpkg-query -l pkg-config”, looks same as yours:

cfdumitr@silpixa00382658:~/git_fdio/vpp$ dpkg-query -l pkg-config
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  pkg-config 0.29.1-0ubuntu1  amd64manage compile and 
link flags for libraries

I re-ran “make install-dep”, it worked again with no (obvious) error messages:

cfdumitr@silpixa00382658:~/git_fdio/vpp$ sudo make install-dep
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
Hit:2 http://ie.archive.ubuntu.com/ubuntu xenial InRelease
Hit:3 http://ie.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:4 http://ie.archive.ubuntu.com/ubuntu xenial-backports InRelease
Fetched 102 kB in 0s (245 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
autoconf is already the newest version (2.69-9).
automake is already the newest version (1:1.15-4ubuntu1).
bison is already the newest version (2:3.0.4.dfsg-1).
build-essential is already the newest version (12.1ubuntu2).
ccache is already the newest version (3.2.4-1).
debhelper is already the newest version (9.20160115ubuntu3).
default-jdk-headless is already the newest version (2:1.8-56ubuntu2).
exuberant-ctags is already the newest version (1:5.9~svn20110310-11).
git is already the newest version (1:2.7.4-0ubuntu1).
libapr1-dev is already the newest version (1.5.2-3).
libtool is already the newest version (2.4.6-0.1).
pkg-config is already the newest version (0.29.1-0ubuntu1).
python-dev is already the newest version (2.7.11-1).
chrpath is already the newest version (0.16-1).
cscope is already the newest version (15.8b-1build1).
git-review is already the newest version (1.25.0-2).
lcov is already the newest version (1.12-2).
libconfuse-dev is already the newest version (2.7-5).
libganglia1-dev is already the newest version (3.6.0-6ubuntu4).
nasm is already the newest version (2.11.08-1).
curl is already the newest version (7.47.0-1ubuntu2.2).
dkms is already the newest version (2.2.0.3-2ubuntu11.3).
libssl-dev is already the newest version (1.0.2g-1ubuntu4.6).
dh-systemd is already the newest version (1.29ubuntu4).
python-pip is already the newest version (8.1.1-2ubuntu0.4).
python-virtualenv is already the newest version (15.0.1+ds-3ubuntu1).
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

Git status: there is absolutely no change in my local copy.

Regards,
Cristian

From: Burt Silverman [mailto:bur...@gmail.com]
Sent: Tuesday, March 28, 2017 4:24 PM
To: Dumitrescu, Cristian 
Cc: vpp-dev 
Subject: Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

I am a bit baffled, Cristian. Well the config.log you have IS consistent with 
mine. g2 doesn't show up the way it does in mine because your configure did not 
complete successfully.
Can you double check
$ dpkg-query -l pkg-config
comes back with something like

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version ArchitectureDescription
+++--===-===-=
ii  pkg-config   0.29.1-0ubuntu1 amd64   manage compile and 
link flags for libraries
which it should if your "make install-dep" worked properly. You see the 
src/configure.ac has PKG_CHECK_MODULES macro that is in 
/usr/share/aclocal/pkg.m4, and that file suggests that our 
configure.ac should have more helpful hints than it 
currently does

dnl To ensure that this macro is defined, also add:
dnl m4_ifndef([PKG_PREREQ],
dnl [m4_fatal([must install pkg-config 0.29 or later before running 
autoconf/autogen])])
But we circle around to your make install-dep should have worked and obviated 
the need for extra helpful messages in configure.ac. Of 
course, you want to do a git status to make certain that nothing bad crept into 
your repo.

Burt
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Tap IF Names

2017-03-28 Thread Jon Loeliger

On Tue, Mar 28, 2017 at 2:28 PM, Pierre Pfister (ppfister) <
ppfis...@cisco.com> wrote:

>
>
> tapcli.c implements all tap nodes, plus the CLI calls.
> tapapi.c only implements api calls and then calls tapcli functions.
>
> Admittedly tapcli is not the perfect name,
>

It's not a matter of names.

but file renaming in git makes the history of changes way harder to follow.
>

I beg to differ. [*1*]

> So I don't think it is necessary to rename tapcli.c
>

Wouldn't do that anyway.  It's not a matter of file names.

My concern is that a pure user of the C API shouldn't drag in
anything to do with the VAT and vppctl CLI command infrastructure.
Having conflated the CLI bits (parsing, param checking, marshalling)
and the CLI output (format(), etc), with the underlying implementaion
of the actual TAP requirements (control sockets, setting the mac
and IP addrs, etc) runs the risk of having the pure C API users
drag in a lot of unneeded CLI code.

There should be a *new* file that has the underlying implementaion
without the CLI bits.

tuntap.c, on the other hand, I think is legacy code. There probably is some
> cleaning to be done there.
>

Haven't peered over there yet... :-/

> - Pierre
>

HTH,
jdl

[*1*] -- http://shop.oreilly.com/product/0636920022862.do
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Tap IF Names

2017-03-28 Thread Pierre Pfister (ppfister)

Le 28 mars 2017 à 13:54, Jon Loeliger 
mailto:j...@netgate.com>> a écrit :

On Tue, Mar 28, 2017 at 11:59 AM, Jon Loeliger 
mailto:j...@netgate.com>> wrote:

On Tue, Mar 28, 2017 at 11:50 AM, Damjan Marion (damarion) 
mailto:damar...@cisco.com>> wrote:

> On 28 Mar 2017, at 12:15, Kinsella, Ray 
> mailto:ray.kinse...@intel.com>> wrote:
>
> +1 to Jon's comments.
>
>
> On 24/03/2017 14:07, Pierre Pfister (ppfister) wrote:
>> Hello Jon,
>>
>> No strong opinion on my side, but I'd just like to notice that there might 
>> be cases where multiple interfaces, in linux, have the same name, if they 
>> are in different network namespaces.
>> VPP could literally control the back-end of thousands of containers' 
>> interfaces, all called eth0.
>
> Well your backend and your frontend device names are typically named 
> different. You are correct in that frontend device in the container is always 
> eth0, the backend device for each container's eth0 is uniquely named in the 
> default network namespace.

Can somebody come up with the patch proposal?

Thanks!

Happy to do so.  One question, though: what is the purpose of
the "renumber" and "custom_dev_instance" fields?

Thanks,
jdl

OK.  I've read through bunch of that custom_dev_instance code now.
I was initially not paying attention to it, as it stumbled into the so-called
"tapcli" data, and we're not using the VPP CLI.

I think the dev_custom_instance will do what we want (Allow the user
to specify the number that will be used as the "show" name for the
corresponding tap interface.  Good.).

However, I now have a different issue with this code.  Almost all the
code in the tapcli.c file is implementation that should be shared by
both the CLI and the API.  RIght now, the API sort of cannibalizes
into the CLI code.

Instead, there should be three files here: the CLI, the API and the
underlying implementation of Tap data structures.

tapcli.c implements all tap nodes, plus the CLI calls.
tapapi.c only implements api calls and then calls tapcli functions.

Admittedly tapcli is not the perfect name, but file renaming in git makes the 
history of changes way harder to follow.
So I don't think it is necessary to rename tapcli.c

tuntap.c, on the other hand, I think is legacy code. There probably is some 
cleaning to be done there.

- Pierre

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Tap IF Names

2017-03-28 Thread Jon Loeliger

On Tue, Mar 28, 2017 at 11:59 AM, Jon Loeliger  wrote:

>
>
> On Tue, Mar 28, 2017 at 11:50 AM, Damjan Marion (damarion) <
> damar...@cisco.com> wrote:
>
>>
>> > On 28 Mar 2017, at 12:15, Kinsella, Ray  wrote:
>> >
>> > +1 to Jon's comments.
>> >
>> >
>> > On 24/03/2017 14:07, Pierre Pfister (ppfister) wrote:
>> >> Hello Jon,
>> >>
>> >> No strong opinion on my side, but I'd just like to notice that there
>> might be cases where multiple interfaces, in linux, have the same name, if
>> they are in different network namespaces.
>> >> VPP could literally control the back-end of thousands of containers'
>> interfaces, all called eth0.
>> >
>> > Well your backend and your frontend device names are typically named
>> different. You are correct in that frontend device in the container is
>> always eth0, the backend device for each container's eth0 is uniquely named
>> in the default network namespace.
>>
>> Can somebody come up with the patch proposal?
>>
>> Thanks!
>
>
> Happy to do so.  One question, though: what is the purpose of
> the "renumber" and "custom_dev_instance" fields?
>
> Thanks,
> jdl
>

OK.  I've read through bunch of that custom_dev_instance code now.
I was initially not paying attention to it, as it stumbled into the
so-called
"tapcli" data, and we're not using the VPP CLI.

I think the dev_custom_instance will do what we want (Allow the user
to specify the number that will be used as the "show" name for the
corresponding tap interface.  Good.).

However, I now have a different issue with this code.  Almost all the
code in the tapcli.c file is implementation that should be shared by
both the CLI and the API.  RIght now, the API sort of cannibalizes
into the CLI code.

Instead, there should be three files here: the CLI, the API and the
underlying implementation of Tap data structures.

Will you entertain a patch down that line?

Thanks,
jdl
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

2017-03-28 Thread Burt Silverman

Wait, doh... this is probably (possibly) an imperfection in the build
system... not sure if it is easy or messy to fix. Suppose you install
pkg-config AFTER your system ran autoconf or autoreconf to generate the
configure. That means you have a bad configure script. If nobody notices
that you have added "materials" that could affect the output of autoconf
and then force autoconf/autoreconf to be run again against configure.ac, we
are screwed. So let us know if this scenario exists: you have pkg-config
installed yet the make bootstrap error occurs nevertheless. I have not
looked closely to see if my hypothesis indeed appears to be valid.

Burt

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Tap IF Names

2017-03-28 Thread Jon Loeliger

On Tue, Mar 28, 2017 at 11:50 AM, Damjan Marion (damarion) <
damar...@cisco.com> wrote:

>
> > On 28 Mar 2017, at 12:15, Kinsella, Ray  wrote:
> >
> > +1 to Jon's comments.
> >
> >
> > On 24/03/2017 14:07, Pierre Pfister (ppfister) wrote:
> >> Hello Jon,
> >>
> >> No strong opinion on my side, but I'd just like to notice that there
> might be cases where multiple interfaces, in linux, have the same name, if
> they are in different network namespaces.
> >> VPP could literally control the back-end of thousands of containers'
> interfaces, all called eth0.
> >
> > Well your backend and your frontend device names are typically named
> different. You are correct in that frontend device in the container is
> always eth0, the backend device for each container's eth0 is uniquely named
> in the default network namespace.
>
> Can somebody come up with the patch proposal?
>
> Thanks!


Happy to do so.  One question, though: what is the purpose of
the "renumber" and "custom_dev_instance" fields?

Thanks,
jdl
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Tap IF Names

2017-03-28 Thread Damjan Marion (damarion)


> On 28 Mar 2017, at 12:15, Kinsella, Ray  wrote:
> 
> +1 to Jon's comments.
> 
> 
> On 24/03/2017 14:07, Pierre Pfister (ppfister) wrote:
>> Hello Jon,
>> 
>> No strong opinion on my side, but I'd just like to notice that there might 
>> be cases where multiple interfaces, in linux, have the same name, if they 
>> are in different network namespaces.
>> VPP could literally control the back-end of thousands of containers' 
>> interfaces, all called eth0.
> 
> Well your backend and your frontend device names are typically named 
> different. You are correct in that frontend device in the container is always 
> eth0, the backend device for each container's eth0 is uniquely named in the 
> default network namespace.

Can somebody come up with the patch proposal?

Thanks!
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

2017-03-28 Thread Burt Silverman

Also, the fact that we saw PKG_CHECK_MODULES appear in your original output
tells me that pkg-config was not installed when your configure was running.
Otherwise, I believe it would have been macro expanded and you'd only see
the expanded form. The mystery remains about your "make install-dep" not
working. Is it possible that there is a network connectivity issue, and a
related error message but the error message did not stick out clearly?

Baffled Burt

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP API Test Crash - Need help debugging

2017-03-28 Thread Keith Burns

Billy,

Apologies, that was a convenience I did for the attendees of the devboot
course last year.

In the course notes I had the git checksum of the commit, but as Dave
points out, a bit stale.

I find a combo of "ldd" against the VPP binary you have built and
ultimately want to install and "ldconfig -p | grep" to be useful. Grep
against "vpp" and "vlib" tends to show what's hanging around and the diff
usually is defunct jetsam from prior packaging.

Be a little careful though as I don't believe vlib is unique to VPP/fdio

As the project evolves , so too packaging (I've felt your pain)

A "find" over /usr/include for headers is not a bad sanity check too


On Mar 27, 2017 6:52 AM, "Dave Barach (dbarach)"  wrote:

Dear Billy,



Looks like a stale tree...



vm = vlib_mains[os_get_cpu_number ()] from within vpp_api_test was always a
mistake. I cleaned this up a while ago. Vpp_api_test was spuriously linked
against libvlib.so, leading to this very crash in vpp_api_test until I
cleaned up the set of libraries, etc.



Please update, “make distclean”, rebuild, and reinstall. If that doesn’t
fix it, please unicast me.



Thanks… Dave



*From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
Behalf Of *Billy McFall
*Sent:* Monday, March 27, 2017 9:37 AM
*To:* vpp-dev@lists.fd.io
*Subject:* [vpp-dev] VPP API Test Crash - Need help debugging



I have screwed up my system and need some help fixing. Long email because
of the traces, so quick summary up front.



I was playing with pluggins and had some notes from over the summer on
running the MacSwap pluggin. I downloaded the code via:

  git clone https://github.com/alagalah/macswap-plugin



The code did not compile initially because the pluggin registration code
changed from a function call to a MACRO. I fiddle with the code and got it
to compile and install. As soon as I fired up VPP it crashed. I did not
collect the output (sorry), but in the mean time I found the sample pluggin
on the Wiki and figured it was the better route anyway. So I deleted the
all macswap*.so files I could find under /usr/* and deleted my local
sandbox with the MAC Swap changes. Now when I run VPP, it crashes, even a
recent, clean sandbox. Builds and loads fine. But when I "show
interfaces", vpp_api_test crashes (see below).



Is there something in the pluggin registration that needs to be cleaned up
that I am missing? Running on Fedora 25. Recent builds on my CentOS system
work as expect, so this most likely has something to do with how I
installed and more likely how I deleted the MAC Swap pluggin on my laptop.



Any help would be greatly appreciated,

Billy McFall





The rest is logs on the crash:



START VPP FROM CLEAN SANDBOX:



Mar 27 09:11:40 localhost systemd: Starting Vector Packet Processing
Process...

Mar 27 09:11:40 localhost systemd: Started Vector Packet Processing Process.

Mar 27 09:11:40 localhost vpp: vlib_plugin_early_init:357: plugin path
/usr/lib/vpp_plugins/

Mar 27 09:11:40 localhost vpp: load_one_plugin:187: Loaded plugin:
acl_plugin.so

Mar 27 09:11:40 localhost vpp: load_one_plugin:187: Loaded plugin:
dpdk_plugin.so

Mar 27 09:11:40 localhost vpp: load_one_plugin:187: Loaded plugin:
flowperpkt_plugin.so

Mar 27 09:11:40 localhost vpp: load_one_plugin:187: Loaded plugin:
ila_plugin.so

Mar 27 09:11:40 localhost vpp: load_one_plugin:187: Loaded plugin:
ioam_plugin.so

Mar 27 09:11:40 localhost vpp: load_one_plugin:114: Plugin disabled:
ixge_plugin.so (default)

Mar 27 09:11:40 localhost vpp: load_one_plugin:187: Loaded plugin:
lb_plugin.so

Mar 27 09:11:40 localhost vpp: load_one_plugin:187: Loaded plugin:
libsixrd_plugin.so

Mar 27 09:11:40 localhost vpp: load_one_plugin:187: Loaded plugin:
snat_plugin.so

Mar 27 09:11:40 localhost vpp: 0: load_one_plugin:63: Loaded plugin:
/usr/lib/vpp_api_test_plugins/udp_ping_test_plugin.so

Mar 27 09:11:40 localhost vpp: 0: load_one_plugin:63: Loaded plugin:
/usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plugin.so

Mar 27 09:11:40 localhost vpp: 0: load_one_plugin:63: Loaded plugin:
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so

Mar 27 09:11:40 localhost vpp: 0: load_one_plugin:63: Loaded plugin:
/usr/lib/vpp_api_test_plugins/snat_test_plugin.so

Mar 27 09:11:40 localhost vpp: 0: load_one_plugin:63: Loaded plugin:
/usr/lib/vpp_api_test_plugins/ioam_trace_test_plugin.so

Mar 27 09:11:40 localhost vpp: 0: load_one_plugin:63: Loaded plugin:
/usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so

Mar 27 09:11:40 localhost vpp: 0: load_one_plugin:63: Loaded plugin:
/usr/lib/vpp_api_test_plugins/ioam_pot_test_plugin.so

Mar 27 09:11:40 localhost vpp: 0: load_one_plugin:63: Loaded plugin:
/usr/lib/vpp_api_test_plugins/vxlan_gpe_ioam_export_test_plugin.so

Mar 27 09:11:40 localhost vpp: 0: load_one_plugin:63: Loaded plugin:
/usr/lib/vpp_api_test_plugins/flowperpkt_test_plugin.so

Mar 27 09:11:40 localhost vpp: 0: load_one_plugin:63: Loaded plugin

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

2017-03-28 Thread Burt Silverman

I am a bit baffled, Cristian. Well the config.log you have IS consistent
with mine. g2 doesn't show up the way it does in mine because your
configure did not complete successfully.

Can you double check

$ dpkg-query -l pkg-config

comes back with something like

Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version ArchitectureDescription
+++--===-===-=
ii  pkg-config   0.29.1-0ubuntu1 amd64   manage compile and
link flags for libraries

which it should if your "make install-dep" worked properly. You see the src/
configure.ac has PKG_CHECK_MODULES macro that is in
/usr/share/aclocal/pkg.m4, and that file suggests that our configure.ac
should have more helpful hints than it currently does

dnl To ensure that this macro is defined, also add:
dnl m4_ifndef([PKG_PREREQ],
dnl [m4_fatal([must install pkg-config 0.29 or later before running
autoconf/autogen])])

But we circle around to your make install-dep should have worked and
obviated the need for extra helpful messages in configure.ac. Of course,
you want to do a git status to make certain that nothing bad crept into
your repo.

Burt
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP project committer nomination: Sergio Gonzales Monroy

2017-03-28 Thread Dave Wallace


+1

On 3/27/17 7:12 AM, Damjan Marion (damarion) wrote:

Hello VPP committers,

I would like to nominate Sergio Gonzales Monroy as a VPP project committer.

History of Sergio’s merged contributions to the VPP project:

https://gerrit.fd.io/r/#/q/owner:sergio.gonzalez.monroy%2540intel.com+status:merged

shows significant amount of work done on VPP crypto/IPSec code including the 
integration with DPDK CryptoDev.

Current VPP committers please vote (+1, 0, -1) by replying to this email 
(reply-all), no later than 04.04.2017 6.00 AM PST.

Thanks,

Damjan


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

2017-03-28 Thread Jon Loeliger

On Tue, Mar 28, 2017 at 8:55 AM, Dumitrescu, Cristian <
cristian.dumitre...@intel.com> wrote:
>
> Hi Jon,
>
>
>
> I did “make install-dep” just before the “make bootstrap”, so maybe there
> is some package that I need to upgrade that is not picked up by “make
> install-dep”.
>
>
>
> One thing to mention is I had exactly the same error on Ubuntu 15.10
> first, then I upgraded to Ubuntu 16.04.2 LTS using “do-release-upgrade”,
> and I am still getting it.
>
>
>
> Any idea on how to debug this?
>
>
>
> Regards,
>
> Cristian
>

Hi Cristian,

I don't really have any more insight into this specific problem.  Sorry.

jdl
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

2017-03-28 Thread Dumitrescu, Cristian

From: Jon Loeliger [mailto:j...@netgate.com]
Sent: Monday, March 27, 2017 8:40 PM
To: Dumitrescu, Cristian 
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

On Mon, Mar 27, 2017 at 12:41 PM, Dumitrescu, Cristian 
mailto:cristian.dumitre...@intel.com>> wrote:
Hi guys,

Any idea why am I getting this error:

>make bootstrap
…
checking for python... /usr/bin/python
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.7/site-packages
checking for python extension module directory... 
${exec_prefix}/lib/python2.7/site-packages
/home/cfdumitr/git_fdio/vpp/build-root/../src/configure: line 13178: syntax 
error near unexpected token `g2,'
/home/cfdumitr/git_fdio/vpp/build-root/../src/configure: line 13178: `  
PKG_CHECK_MODULES(g2, gtk+-2.0)'
Makefile:649: recipe for target 'tools-configure' failed
make[1]: *** [tools-configure] Error 2
make[1]: Leaving directory '/home/cfdumitr/git_fdio/vpp/build-root'
Makefile:133: recipe for target 
'/home/cfdumitr/git_fdio/vpp/build-root/.bootstrap.ok' failed
make: *** [/home/cfdumitr/git_fdio/vpp/build-root/.bootstrap.ok] Error 2

Thanks,
Cristian

The bootstrap target was recently extended to ensure that each
necessary package was indeed installed on the build machine.

You may be missing a package and may need to run "make install-dep"?

jdl

Hi Jon,

I did “make install-dep” just before the “make bootstrap”, so maybe there is 
some package that I need to upgrade that is not picked up by “make install-dep”.

One thing to mention is I had exactly the same error on Ubuntu 15.10 first, 
then I upgraded to Ubuntu 16.04.2 LTS using “do-release-upgrade”, and I am 
still getting it.

Any idea on how to debug this?

Regards,
Cristian
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Building router plugin

2017-03-28 Thread Dave Barach (dbarach)

FWIW: I sent diffs to fix the build-system integration over the weekend, as 
well as a fair fraction of the FIB 2.0 integration...

Thanks… Dave

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Ni, Hongjun
Sent: Monday, March 27, 2017 10:32 PM
To: Ed Warnicke ; Lukasz Chrustek 
Cc: Shaw, Jeffrey B ; Damjan Marion (damarion) 
; vpp-dev@lists.fd.io; Lukasz Chrustek 
Subject: Re: [vpp-dev] Building router plugin

Hi Luk,

We are using netlink and router plugin in VPP stable 17.01, and also met the 
same issue.

I have submitted a patch to fix a compile issue in netlink for review, now 
netlink could compile ok in VPP stable 17.01.
https://gerrit.fd.io/r/#/c/5881/ FIx compile issue for netlink

I am working on router plugin now, hope to address some issues and make it work 
again in VPP stable 17.01.

For VPP 17.04, make file may need to be changed as per new building system.

Regards,
Hongjun

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Ed Warnicke
Sent: Tuesday, March 28, 2017 6:10 AM
To: Łukasz Chrustek mailto:ski...@tlen.pl>>
Cc: Damjan Marion (damarion) mailto:damar...@cisco.com>>; 
Lukasz Chrustek mailto:luk...@chrustek.net>>; 
vpp-dev@lists.fd.io; Shaw, Jeffrey B 
mailto:jeffrey.b.s...@intel.com>>
Subject: Re: [vpp-dev] Building router plugin

You might also look at

https://gerrit.fd.io/r/#/c/5004/ - which introduces memif interfaces... which I 
think Damjan eventually wants a library for so that you could
use them for things like taps for routing protocol packets...

Ed

On Mon, Mar 27, 2017 at 2:43 PM, Łukasz Chrustek 
mailto:ski...@tlen.pl>> wrote:
Hi,

Ok,  thank You. I will give a try with earlier version of vpp, as Jeff
suggests.  I  have  running  netlink  plugin,  but as Ole wrote - most
important is router plugin.

Cheers,
Luk

>> You basically have two options:
>> 1. Teach your routing protocol daemon to directly talk to VPP for 
>> configuring the FIB.
>> 2. Do not modify the routing daemon and let VPP map routes written in the 
>> kernel.
>>
>> For 1, you will need the router plugin, but for packet punting only.
>>
>> For 2., you will need both netlink+router plugins. The netlink plugin (which 
>> actually more like a library), shouldn't require so much changes though.

> With TCP support in VPP I was playing with the idea of integrating exaBGP as 
> a VPP plugin.
> Use the Python API binding to program routes, and receive the BGP
> stream across a fifo (or even the API).

> Cheers,
> Ole

>>> Le 26 mars 2017 à 16:31, Łukasz Chrustek 
>>> mailto:ski...@tlen.pl>> a écrit :
>>>
>>> Hello,
>>>
>>> thank all of You for clarification of status router plugin.
>>>
>>> I'm trying to use vpp+dpdk as bare metal linux ruter with bgp and ospf 
>>> routing protocols, goal is to make very fast router with dynamic routing 
>>> protocols. Can You advice is there any other way to exchange dynamic 
>>> routing information between os and vpp ?
>>>
>>> Regards
>>> Lukasz
>>>
>>>
>>> The mailman did not let my last message go through because it was too big 
>>> so I am removing the previous threads to keep this message under 100KB 
>>> limit.
>>>
>>> Hello,
>>>
>>> Dave and Pierre are correct, the router plugin is no longer being 
>>> maintained. There was not much interest in the community for this project 
>>> at the time and I have since moved on to other things.  I’d be happy to 
>>> help a new maintainer with any questions they may have.
>>>
>>> If you really want to just test it out, I suggest attempting to checkout a 
>>> commit of VPP close to the last commit on the router plugin. Somewhere 
>>> closely following VPP commit 0bfe5d8c792abcdb, “A Protocol Independent 
>>> Hierarchical FIB (VPP-352)” will work (you might have to git bisect to get 
>>> something that compiles right away).
>>>
>>> If necessary, I can submit a patch to remove the router plugin from the VPP 
>>> sandbox with a note on the wiki page mentioning the finalization of the 
>>> project. I recall there being an 8-month time limit for these the sandbox 
>>> projects.
>>>
>>> -Jeff
>>>
>>>
>>>
>>
>> ___
>> vpp-dev mailing list
>> vpp-dev@lists.fd.io
>> https://lists.fd.io/mailman/listinfo/vpp-dev


--
Pozdrowienia,
 Łukasz Chrustek

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Tap IF Names

2017-03-28 Thread Kinsella, Ray


+1 to Jon's comments.


On 24/03/2017 14:07, Pierre Pfister (ppfister) wrote:

Hello Jon,

No strong opinion on my side, but I'd just like to notice that there might be 
cases where multiple interfaces, in linux, have the same name, if they are in 
different network namespaces.
VPP could literally control the back-end of thousands of containers' 
interfaces, all called eth0.


Well your backend and your frontend device names are typically named 
different. You are correct in that frontend device in the container is 
always eth0, the backend device for each container's eth0 is uniquely 
named in the default network namespace.


Ray K
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Building router plugin

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

Re: [vpp-dev] Tap IF Names

Re: [vpp-dev] Tap IF Names

Re: [vpp-dev] Tap IF Names

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

Re: [vpp-dev] Tap IF Names

Re: [vpp-dev] Tap IF Names

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

Re: [vpp-dev] VPP API Test Crash - Need help debugging

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

Re: [vpp-dev] VPP project committer nomination: Sergio Gonzales Monroy

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

Re: [vpp-dev] VPP build issue on Ubuntu 16.04.2 LTS

Re: [vpp-dev] Building router plugin

Re: [vpp-dev] Tap IF Names

20 matches

Site Navigation

Mail list logo

Footer information