Re: [vpp-dev] Maintainer router plugin

[Jan Hugo Prins | BetterBe]

Hi Ole,

I really don't mind that you all derailed my discussion. I think a good
design discussion is a good thing. Especially when the end result is a
better product, or in this case, better integration between products.
What I have found with respect to OSPFv3, is that the OSPF multicast
packets are being dropped at the router edge. See my earlier message
with the PCAP file.

I currently have no idea why my OSPFv2 routers are not properly
installed in the VPP IP FIB, while they are in the Linux IP FIB.

Jan Hugo Prins


On 04/11/2018 07:37 PM, Ole Troan wrote:
> Jan Hugo,
>
>> But this basically means that, for now, it won't be possible to create a BGP 
>> router with a combination of FRR and VPP doing both IPv4 and IPv6 with OSPF 
>> and BGP.
>> Or do you see possibilities to make OSPFv3 work?
> Sorry, for derailing your thread and making it into an architectural 
> discussion. ;-)
> If you ask my opinion, I would probably prefer it not to go into the main 
> repository.
>
> That said, if it works for OSPFv2, one shouldn't think it would be that hard 
> to make it work for OSPFv3 either.
> Probably some ARP/ND issues? Ray, would you know?
>
> Best regards,
> Ole
>
>
>
>> Jan Hugo Prins
>>
>>
>> On 04/11/2018 03:20 PM, Ray Kinsella wrote:
>>> Hi Ole,
>>>
>>> I agree - but completely reinventing the wheel is not a the best course 
>>> either. These are tried and tested implementations and are worth reusing, I 
>>> do agree that integrating through the Linux Kernel is not ideal.
>>>
>>> We developed the router plugin to show that integration was possible we 
>>> never claimed that it was the 'best' way to integrate either.
>>>
>>> Plugging a Quagga/FRR/Bird etc into VPP/HC is definitely the better path. 
>>> Historically it has been hard with Quagga due to GPL licensing, I 
>>> understand that FRR is the easiest path.
>>>
>>> Ray K
>>>
>>> On 11/04/2018 09:33, Ole Troan wrote:
 Hi Jan,

> Is someone actively maintaining the router plugin?
 I'm not a big fan of the router plugin.
 The starting point of the router plugin is "how can you take an unmodified 
 routing protocol implementation and make it work with VPP".
 That leads to all kinds of complexities as the two methods they tried 
 shows.

 If we change the premise does the solution space look better?

 I think we could change the routing protocol implementation to talk 
 directly with VPP's API for interfaces / interface events, it programs the 
 VPP FIB directly.
 Then it could send and receive packets somewhat similar to what we have 
 for the punt Unix domain socket.
 We might need a better punt path mechanism, where a Linux application can 
 register for a particular IP protocol (like 89 for OSPF) on a particular 
 interface. But that should be easy to do.

 I did have a brief chat with David Lamparter of Quagga fame and he had 
 thought about doing it in a similar way.

 What is your particular use case? Is it just a routing protocol you need?

 Best regards,
 Ole





>>>
>>>
>> --
>> Kind regards
>>
>> Jan Hugo Prins
>> DevOps Engineer
>> 
>> Auke Vleerstraat 140 E
>> 7547 AN Enschede
>> CC no. 08097527  T +31 (0) 53 48 00 694
>> E jpr...@betterbe.com
>> M +31 (0)6 263 58 951www.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/

Auke Vleerstraat 140 E
7547 AN Enschede
CC no. 08097527

*T* +31 (0) 53 48 00 694 
*E* jpr...@betterbe.com 
*M* +31 (0)6 263 58 951 
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.

Re: [vpp-dev] Maintainer router plugin

[Jan Hugo Prins | BetterBe]

But this basically means that, for now, it won't be possible to create a
BGP router with a combination of FRR and VPP doing both IPv4 and IPv6
with OSPF and BGP.
Or do you see possibilities to make OSPFv3 work?

Jan Hugo Prins


On 04/11/2018 03:20 PM, Ray Kinsella wrote:
> Hi Ole,
>
> I agree - but completely reinventing the wheel is not a the best
> course either. These are tried and tested implementations and are
> worth reusing, I do agree that integrating through the Linux Kernel is
> not ideal.
>
> We developed the router plugin to show that integration was possible
> we never claimed that it was the 'best' way to integrate either.
>
> Plugging a Quagga/FRR/Bird etc into VPP/HC is definitely the better
> path. Historically it has been hard with Quagga due to GPL licensing,
> I understand that FRR is the easiest path.
>
> Ray K
>
> On 11/04/2018 09:33, Ole Troan wrote:
>> Hi Jan,
>>
>>> Is someone actively maintaining the router plugin?
>>
>> I'm not a big fan of the router plugin.
>> The starting point of the router plugin is "how can you take an
>> unmodified routing protocol implementation and make it work with VPP".
>> That leads to all kinds of complexities as the two methods they tried
>> shows.
>>
>> If we change the premise does the solution space look better?
>>
>> I think we could change the routing protocol implementation to talk
>> directly with VPP's API for interfaces / interface events, it
>> programs the VPP FIB directly.
>> Then it could send and receive packets somewhat similar to what we
>> have for the punt Unix domain socket.
>> We might need a better punt path mechanism, where a Linux application
>> can register for a particular IP protocol (like 89 for OSPF) on a
>> particular interface. But that should be easy to do.
>>
>> I did have a brief chat with David Lamparter of Quagga fame and he
>> had thought about doing it in a similar way.
>>
>> What is your particular use case? Is it just a routing protocol you
>> need?
>>
>> Best regards,
>> Ole
>>
>>
>>
>>
>>
>
> 
>

-- 
Kind regards

Jan Hugo Prins
/DevOps Engineer/

Auke Vleerstraat 140 E
7547 AN Enschede
CC no. 08097527

*T* +31 (0) 53 48 00 694 
*E* jpr...@betterbe.com 
*M* +31 (0)6 263 58 951 
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.

Re: [vpp-dev] Maintainer router plugin

[Jan Hugo Prins | BetterBe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello Ole,

That sounds to me like the router / rtnetlink plugins are a dead horse,
not worth any more of my time ;-)
I have setup a BGP session on IPv4 and the first results are not that
good. The session is setup, the routes are installed in the Linux
kernel, but in VPP  I don't see them at all.
I would expect to see the routes when I do "sh ip fib" but I only see a
small part of the routes directly connected to the OSPF neighbor's and
no BGP routes at all, but because the BGP routes are all behind OSPF
routes that are missing, I think this is to be expected.

It would be really great if frr would communicate directly with VPP and
install the routes and the interface configuration etc, but this sounds
like a development story that could take some time.

Jan Hugo Prins


On 04/11/2018 11:57 AM, Ole Troan wrote:
> Hi Jan Hugo, > >> The main thing I'm currently missing is OSPFv3. The 
> multicast
packets >> don't arrive in linux kernel. >> Attached is a pcap file
showing the dropped packets. >> OSPFv2 seems to be working fine. >> I
hope to test the BGP for IPv4 and IPv6 today. >> >> I have put my
findings in the vppsb-dev mailinglist. >> >> I would be really happy if
I could get this setup working. >> I currently have the possibility to
test any code changes you make :-) > > I am of course proposing a
completely different model than what's in the router plugin. > > A first
step would be to ensure we got all the functionality we need from the
VPP <--> Linux punt path. > > Best regards, > Ole > > >
 >
- -- 
Kind regards

Jan Hugo Prins
/DevOps Engineer/

Auke Vleerstraat 140 E
7547 AN Enschede
CC no. 08097527

*T* +31 (0) 53 48 00 694 
*E* jpr...@betterbe.com 
*M* +31 (0)6 263 58 951  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.

-BEGIN PGP SIGNATURE-

iF0EARECAB0WIQRlyp0kFjWHi/j64SQKby/W7MOWVwUCWs3r+wAKCRAKby/W7MOW
V6E/AKCqYzY0Zn/ot6emlTcUyh9iOQVo2QCfXfjxjqZfWJ+ot9V4iJowYrmbDaE=
=ImyJ
-END PGP SIGNATURE-

Re: [vpp-dev] Maintainer router plugin

[Jan Hugo Prins | BetterBe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello Ole,

The main thing I'm currently missing is OSPFv3. The multicast packets
don't arrive in linux kernel.
Attached is a pcap file showing the dropped packets.
OSPFv2 seems to be working fine.
I hope to test the BGP for IPv4 and IPv6 today.

I have put my findings in the vppsb-dev mailinglist.

I would be really happy if I could get this setup working.
I currently have the possibility to test any code changes you make :-)

Jan Hugo Prins


On 04/11/2018 10:33 AM, Ole Troan wrote:
> Hi Jan, > >> Is someone actively maintaining the router plugin? > > I'm not a
big fan of the router plugin. > The starting point of the router plugin
is "how can you take an unmodified routing protocol implementation and
make it work with VPP". > That leads to all kinds of complexities as the
two methods they tried shows. > > If we change the premise does the
solution space look better? > > I think we could change the routing
protocol implementation to talk directly with VPP's API for interfaces /
interface events, it programs the VPP FIB directly. > Then it could send
and receive packets somewhat similar to what we have for the punt Unix
domain socket. > We might need a better punt path mechanism, where a
Linux application can register for a particular IP protocol (like 89 for
OSPF) on a particular interface. But that should be easy to do. > > I
did have a brief chat with David Lamparter of Quagga fame and he had
thought about doing it in a similar way. > > What is your particular use
case? Is it just a routing protocol you need? > > Best regards, > Ole > >
- -- 
Kind regards

Jan Hugo Prins
/DevOps Engineer/

Auke Vleerstraat 140 E
7547 AN Enschede
CC no. 08097527

*T* +31 (0) 53 48 00 694 
*E* jpr...@betterbe.com 
*M* +31 (0)6 263 58 951  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.

-BEGIN PGP SIGNATURE-

iF0EARECAB0WIQRlyp0kFjWHi/j64SQKby/W7MOWVwUCWs3RqAAKCRAKby/W7MOW
VyOLAJ9YDbq3eySyyvqpOchasdS57veZsACfWaBJCINMXrgNq0bpTlUDWf1j7HE=
=ZxtU
-END PGP SIGNATURE-



vppTestDrop.pcap
Description: application/vnd.tcpdump.pcap


vppTestDrop.pcap.sig
Description: PGP signature

[vpp-dev] Maintainer router plugin

[Jan Hugo Prins | BetterBe]

Hello,

Is someone actively maintaining the router plugin?

Jan Hugo
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [vpp-dev] 18.04 RC2 this Wednesday!

[Jan Hugo Prins | BetterBe]

The following error scrolls by a lot during compile:

    default: gcc -std=gnu99 -c -g -O3 -fwrapv -U__STRICT_ANSI__
-fno-common -Werror=attributes -W -Wall -pedantic -Wno-long-long
-Werror=implicit -Werror=missing-braces -Werror=return-type
-Werror=trigraphs -Werror=pointer-arith -Werror=missing-prototypes
-Werror=missing-declarations -Werror=comment -Werror=vla -DHAVE_CONFIG_H
-I. -I. -I./include -I./include -I./x86 -I./x86 -I./asm -I./asm
-I./disasm -I./disasm -I./output -I./output -o rdoff/rdlib.o rdoff/rdlib.c
    default: In file included from rdoff/rdfutils.h:44:0,
    default:  from rdoff/rdoff.c:50:
    default: ./include/nasmlib.h:113:11: warning: ISO C99 does not
support '_Noreturn' [-Wpedantic]
    default:  no_return nasm_assert_failed(const char *, int, const char *);
    default:    ^
    default: In file included from rdoff/rdfutils.h:45:0,
    default:  from rdoff/rdoff.c:50:
    default: ./include/error.h:47:29: warning: ISO C99 does not support
'_Noreturn' [-Wpedantic]
    default:  no_return printf_func(2, 3) nasm_fatal(int flags, const
char *fmt, ...);
    default:  ^
    default: ./include/error.h:48:29: warning: ISO C99 does not support
'_Noreturn' [-Wpedantic]
    default:  no_return printf_func(2, 3) nasm_panic(int flags, const
char *fmt, ...);
    default:  ^
    default: ./include/error.h:49:11: warning: ISO C99 does not support
'_Noreturn' [-Wpedantic]
    default:  no_return nasm_panic_from_macro(const char *file, int line);
    default:    ^
    default: In file included from rdoff/rdfutils.h:44:0,
    default:  from rdoff/rdfload.h:15,
    default:  from rdoff/rdfload.c:51:
    default: ./include/nasmlib.h:113:11: warning: ISO C99 does not
support '_Noreturn' [-Wpedantic]
    default:  no_return nasm_assert_failed(const char *, int, const char *);
    default:    ^
    default: In file included from rdoff/rdfutils.h:45:0,
    default:  from rdoff/rdfload.h:15,
    default:  from rdoff/rdfload.c:51:
    default: ./include/error.h:47:29: warning: ISO C99 does not support
'_Noreturn' [-Wpedantic]
    default:  no_return printf_func(2, 3) nasm_fatal(int flags, const
char *fmt, ...);
    default:  ^
    default: ./include/error.h:48:29: warning: ISO C99 does not support
'_Noreturn' [-Wpedantic]
    default:  no_return printf_func(2, 3) nasm_panic(int flags, const
char *fmt, ...);
    default:  ^
    default: ./include/error.h:49:11: warning: ISO C99 does not support
'_Noreturn' [-Wpedantic]
    default:  no_return nasm_panic_from_macro(const char *file, int line);
    default:    ^


And the following:


    default: make[4]: Entering directory
`/vpp/build-root/rpmbuild/vpp-18.07/build-root/build-vpp-native/vpp'
    default:   APIGEN   vlibmemory/memclnt.api.h
    default:   JSON API vlibmemory/memclnt.api.json
    default:
WARNING:vppapigen:/vpp/build-root/rpmbuild/vpp-18.07/build-data/../src/vlibmemory/memclnt.api:0:1:
Old Style VLA: u8 data[0];
    default:
WARNING:vppapigen:/vpp/build-root/rpmbuild/vpp-18.07/build-data/../src/vlibmemory/memclnt.api:0:1:
Old Style VLA: u8 data[0];


No idea if it is anywhere critical or if someone has created reports for
this in the past.

Jan Hugo



On 04/09/2018 08:43 PM, Chris Luke wrote:
>
> All,
>
>  
>
> Gentle reminder that 18.04 RC2 will be posted on Wednesday.
>
>  
>
> Note: After Wednesday's RC2 Milestone, only critical bug fixes will be
> merged into branch stable/1804.  Please review open anomalies for
> candidates to be fixed this week. Also, please remember to open a Jira
> ticket for all patches submitted to stable branches.
>
>  
>
> Cheers,
>
> Chris.
>
> 

-- 
Kind regards

Jan Hugo Prins
/DevOps Engineer/

Auke Vleerstraat 140 E
7547 AN Enschede
CC no. 08097527

*T* +31 (0) 53 48 00 694 
*E* jpr...@betterbe.com 
*M* +31 (0)6 263 58 951 
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.

Re: [vpp-dev] 18.04 RC2 this Wednesday!

[Jan Hugo Prins | BetterBe]

I understand completely.
Is the maintainer of these plugins here on the mailinglist?

Jan Hugo

On 04/09/2018 11:21 PM, Chris Luke wrote:
>
> Unfortunately it’s too late for such large features to be merged with
> VPP’s stable branch, which is now focused on bug fixes.
>
>  
>
> Additionally, it’s up to the maintainers of those plugins to propose
> merging their work with the VPP project.
>
>  
>
> Cheers,
>
> Chris.
>
>  
>
>  
>
>  
>
> *From:*vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> *On Behalf Of *Jan
> Hugo Prins | BetterBe
> *Sent:* Monday, April 9, 2018 17:15
> *To:* vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] 18.04 RC2 this Wednesday!
>
>  
>
> Hello,
>
> Would it be possible to get the router and netlink plugin, that are
> currently in the VPPSB project, merged into 18.04 ?
> I would like to work with them building a set of routers, and having
> them in the stable branche would mean that the chance of some patches
> breaking this functionality would be a lot smaller.
>
> Cheers,
> Jan Hugo Prins
>
> On 04/09/2018 08:43 PM, Chris Luke wrote:
>
> All,
>
>  
>
> Gentle reminder that 18.04 RC2 will be posted on Wednesday.
>
>  
>
> Note: After Wednesday's RC2 Milestone, only critical bug fixes
> will be merged into branch stable/1804.  Please review open
> anomalies for candidates to be fixed this week. Also, please
> remember to open a Jira ticket for all patches submitted to stable
> branches.
>
>  
>
> Cheers,
>
> Chris.
>
>  
>
> -- 
>
> 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=08097527>
>
>   
>
> *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=08097527>
*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.

Re: [vpp-dev] 18.04 RC2 this Wednesday!

[Jan Hugo Prins | BetterBe]

Hello,

Would it be possible to get the router and netlink plugin, that are
currently in the VPPSB project, merged into 18.04 ?
I would like to work with them building a set of routers, and having
them in the stable branche would mean that the chance of some patches
breaking this functionality would be a lot smaller.

Cheers,
Jan Hugo Prins


On 04/09/2018 08:43 PM, Chris Luke wrote:
>
> All,
>
>  
>
> Gentle reminder that 18.04 RC2 will be posted on Wednesday.
>
>  
>
> Note: After Wednesday's RC2 Milestone, only critical bug fixes will be
> merged into branch stable/1804.  Please review open anomalies for
> candidates to be fixed this week. Also, please remember to open a Jira
> ticket for all patches submitted to stable branches.
>
>  
>
> Cheers,
>
> Chris.
>
> 

-- 
Kind regards

Jan Hugo Prins
/DevOps Engineer/

Auke Vleerstraat 140 E
7547 AN Enschede
CC no. 08097527

*T* +31 (0) 53 48 00 694 
*E* jpr...@betterbe.com 
*M* +31 (0)6 263 58 951 
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.

Re: [vpp-dev] Building RPM's for VPP and include router and netlink plugins

[Jan Hugo Prins | BetterBe]

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=08097527>
>   *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=08097527>
*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.

[vpp-dev] Building RPM's for VPP and include router and netlink plugins

[Jan Hugo Prins | BetterBe]

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/

Auke Vleerstraat 140 E
7547 AN Enschede
CC no. 08097527

*T* +31 (0) 53 48 00 694 
*E* jpr...@betterbe.com 
*M* +31 (0)6 263 58 951 
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.