Hello, after some pointers from Burt Silverman I was able to build the router and netlink plugin. The process is as follows:
$ git clone https://gerrit.fd.io/r/vpp $ cd vpp/build-root/vagrant/ $ export VPP_VAGRANT_DISTRO=centos7 $ vagrant up $ vagrant ssh $ sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm $ exit $ vagrant provision $ vagrant ssh $ cd ~ $ git clone https://gerrit.fd.io/r/vppsb $ sudo yum install -y python-cffi python-pycparser $ cd /vpp $ ln -sf /home/vagrant/vppsb/netlink $ ln -sf /home/vagrant/vppsb/router $ ln -sf ../../netlink/netlink.mk build-data/packages/ $ ln -sf ../../router/router.mk build-data/packages/ $ cd build-root/ $ make V=0 PLATFORM=vpp TAG=vpp_debug netlink-install router-install The rpm files are in the directory: /vpp/build-root/ The plugins are now in the directory: /vpp/build-root/install-vpp_debug-native/ librtnl.so -> /usr/lib64 testrtnl_plugin.so -> /usr/lib/vpp_plugins router.so -> /usr/lib/vpp_plugins I have not yet found how to make sure that the Fedora-Epel repository is in the image before I start building, so 'vagrant up' fails initially because it misses some packages. After putting the plugins on the target server in the correct directories, vpp is able to load the plugins and I'm able to do a 'enable tap-inject'. One side note, after doing 'enable tap-inject' I have the tap interfaces but: - Doing 'show tap TenGigabitEthernet5/0/0' crashes vpp. Have not found any stacktraces. More testing will be done in the coming week. Some quick questions: - Is it possible to give the tap interfaces created by the router plugin specific names? Can I name them like the interfaces in vpp itself? - How do I save my configuration I put in vppctl? Do I need to create a script or config file somewhere? Thanks, Jan Hugo Prins On 04/06/2018 09:10 PM, Jan Hugo Prins | BetterBe wrote: > Hello, > > I'm currently trying ot build a BGP router based on frrouter and VPP. > To do this I have tried to follow the following URL: > https://github.com/FRRouting/frr/wiki/Alternate-forwarding-planes:-VPP > > The first part works fine. > I set VPP_VAGRANT_DISTRO to centos7. > I build the vpp packages and this results in a whole lot of rpm files. > After that I have to checkout the vppsb project and create some symlinks. > But after that I have to run ./bootstrap.sh in the build-root > directory, but it ain't there. > Skipping the ./bootstrap.sh doesn't work either because the make after > that does not work at that location. > > Could someone give me some pointers on how to get the vpp rpm set > including the plugins from the vppsb project? > > I want to base the router on centos 7.4. > > -- > Kind regards > > Jan Hugo Prins > /DevOps Engineer/ > <https://betterbe.com> > Auke Vleerstraat 140 E > 7547 AN Enschede > CC no. 08097527 > <https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=080975270000> > *T* +31 (0) 53 48 00 694 <tel:+31534800694> > *E* jpr...@betterbe.com <mailto:jpr...@betterbe.com> > *M* +31 (0)6 263 58 951 <tel:+31%20%280%296%20263%2058%20951> > www.betterbe.com <https://www.betterbe.com> > BetterBe accepts no liability for the content of this email, or for > the consequences of any actions taken on the basis > of the information provided, unless that information is subsequently > confirmed in writing. If you are not the intended > recipient you are notified that disclosing, copying, distributing or > taking any action in reliance on the contents of this > information is strictly prohibited. > > -- Kind regards Jan Hugo Prins /DevOps Engineer/ <https://betterbe.com> Auke Vleerstraat 140 E 7547 AN Enschede CC no. 08097527 <https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=080975270000> *T* +31 (0) 53 48 00 694 <tel:+31534800694> *E* jpr...@betterbe.com <mailto:jpr...@betterbe.com> *M* +31 (0)6 263 58 951 <tel:+31%20%280%296%20263%2058%20951> www.betterbe.com <https://www.betterbe.com> BetterBe accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.