date:20180125

Re: [vpp-dev] openSUSE build fails

2018-01-25 Thread Ni, Hongjun

I rechecked this patch twice, and it built successfully now.

But why need to recheck twice?

-Hongjun

From: Ole Troan [mailto:otr...@employees.org]
Sent: Friday, January 26, 2018 2:53 PM
To: Ni, Hongjun 
Cc: Dave Barach (dbarach) ; Marco Varlese 
; Gabriel Ganne ; Billy McFall 
; Damjan Marion (damarion) ; vpp-dev 

Subject: Re: [vpp-dev] openSUSE build fails

Hi Hongjun,

I have no OpenSUSE at hand, and could not give it a try.

Neither do I.

Ole



From: Ole Troan [mailto:otr...@employees.org]
Sent: Friday, January 26, 2018 2:08 PM
To: Ni, Hongjun >
Cc: Dave Barach (dbarach) >; Marco 
Varlese >; Gabriel Ganne 
>; Billy McFall 
>; Damjan Marion (damarion) 
>; vpp-dev 
>
Subject: Re: [vpp-dev] openSUSE build fails

Hongjun,

This looks suspect:

03:32:31 APIGEN vlibmemory/memclnt.api.h 03:32:31 JSON API 
vlibmemory/memclnt.api.json 03:32:31 SyntaxError: invalid syntax 
(vppapigentab.py, line 11) 03:32:31 
WARNING:vppapigen:/w/workspace/vpp-verify-master-opensuse/build-root/rpmbuild/BUILD/vpp-18.04/build-data/../src/vlibmemory/memclnt.api:0:1:
 Old Style VLA: u8 data[0]; 03:32:31 Makefile:8794: recipe for target 
'vlibmemory/memclnt.api.h' failed 03:32:31 make[5]: *** 
[vlibmemory/memclnt.api.h] Error 1 03:32:31 make[5]: *** Waiting for unfinished 
jobs 03:32:31





Can you try running vppapigen manually on that platform?
Vppapigen —debug —input memclnt.api ...

Cheers
Ole


On 26 Jan 2018, at 06:38, Ni, Hongjun 
> wrote:
Hi all,

It seems that OpenSUSE build failed for this patch:
https://jenkins.fd.io/job/vpp-verify-master-opensuse/1285/console

Please help to take a

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Dave Barach (dbarach)
Sent: Friday, December 15, 2017 11:19 PM
To: Marco Varlese >; Gabriel Ganne 
>; Billy McFall 
>
Cc: Damjan Marion (damarion) >; 
vpp-dev >
Subject: Re: [vpp-dev] openSUSE build fails

Dear Marco,

Thanks very much...

Dave

From: Marco Varlese [mailto:mvarl...@suse.de]
Sent: Friday, December 15, 2017 9:06 AM
To: Dave Barach (dbarach) >; 
Gabriel Ganne >; Billy 
McFall >
Cc: Damjan Marion (damarion) >; 
vpp-dev >
Subject: Re: [vpp-dev] openSUSE build fails

We (at SUSE) are currently pushing an update to 2.2.11 for openSUSE in our 
repositories.
Once that's confirmed to be upstream, I will push a new patch to the 
ci-management repo to have the indent package upgraded to the latest version 
and re-enable the "checkstyle".


Cheers,
Marco

On Fri, 2017-12-15 at 13:51 +, Dave Barach (dbarach) wrote:
With a bit of fiddling, I was able to fix gerrit 9440 so that indent 2.2.10 and 
2.2.11 appear to produce identical results...

HTH... Dave

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Gabriel Ganne
Sent: Friday, December 15, 2017 8:42 AM
To: Billy McFall >; Marco Varlese 
>
Cc: Damjan Marion (damarion) >; 
vpp-dev >
Subject: Re: [vpp-dev] openSUSE build fails


Hi,



If you browse the source http://hg.savannah.gnu.org/hgweb/indent/

The tag 2.2.11  is there, the source seems updated regularly.



Best regards,



--

Gabriel Ganne


From: vpp-dev-boun...@lists.fd.io 
> on behalf of 
Billy McFall >
Sent: Friday, December 15, 2017 2:26:42 PM
To: Marco Varlese
Cc: Damjan Marion (damarion); vpp-dev
Subject: Re: [vpp-dev] openSUSE build fails



On Fri, Dec 15, 2017 at 5:15 AM, Marco Varlese 
> wrote:
Hi Damjan,

On Fri, 2017-12-15 at 09:06 +, Damjan Marion (damarion) wrote:


On 15 Dec 2017, at 08:52, Marco Varlese

Re: [vpp-dev] openSUSE build fails

2018-01-25 Thread Ole Troan

Hi Hongjun,

> I have no OpenSUSE at hand, and could not give it a try.

Neither do I. 

Ole


>  
> From: Ole Troan [mailto:otr...@employees.org] 
> Sent: Friday, January 26, 2018 2:08 PM
> To: Ni, Hongjun 
> Cc: Dave Barach (dbarach) ; Marco Varlese 
> ; Gabriel Ganne ; Billy McFall 
> ; Damjan Marion (damarion) ; vpp-dev 
> 
> Subject: Re: [vpp-dev] openSUSE build fails
>  
> Hongjun,
>  
> This looks suspect:
> 03:32:31 APIGEN vlibmemory/memclnt.api.h 03:32:31 JSON API 
> vlibmemory/memclnt.api.json 03:32:31 SyntaxError: invalid syntax 
> (vppapigentab.py, line 11) 03:32:31 
> WARNING:vppapigen:/w/workspace/vpp-verify-master-opensuse/build-root/rpmbuild/BUILD/vpp-18.04/build-data/../src/vlibmemory/memclnt.api:0:1:
>  Old Style VLA: u8 data[0]; 03:32:31 Makefile:8794: recipe for target 
> 'vlibmemory/memclnt.api.h' failed 03:32:31 make[5]: *** 
> [vlibmemory/memclnt.api.h] Error 1 03:32:31 make[5]: *** Waiting for 
> unfinished jobs 03:32:31 
> 
> 
>  
> Can you try running vppapigen manually on that platform?
> Vppapigen —debug —input memclnt.api ...
>  
> Cheers 
> Ole
>  
> 
> On 26 Jan 2018, at 06:38, Ni, Hongjun  wrote:
> 
> Hi all,
>  
> It seems that OpenSUSE build failed for this patch:
> https://jenkins.fd.io/job/vpp-verify-master-opensuse/1285/console
>  
> Please help to take a 
>  
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
> Behalf Of Dave Barach (dbarach)
> Sent: Friday, December 15, 2017 11:19 PM
> To: Marco Varlese ; Gabriel Ganne ; 
> Billy McFall 
> Cc: Damjan Marion (damarion) ; vpp-dev 
> 
> Subject: Re: [vpp-dev] openSUSE build fails
>  
> Dear Marco,
>  
> Thanks very much...
>  
> Dave
>  
> From: Marco Varlese [mailto:mvarl...@suse.de] 
> Sent: Friday, December 15, 2017 9:06 AM
> To: Dave Barach (dbarach) ; Gabriel Ganne 
> ; Billy McFall 
> Cc: Damjan Marion (damarion) ; vpp-dev 
> 
> Subject: Re: [vpp-dev] openSUSE build fails
>  
> We (at SUSE) are currently pushing an update to 2.2.11 for openSUSE in our 
> repositories.
> Once that's confirmed to be upstream, I will push a new patch to the 
> ci-management repo to have the indent package upgraded to the latest version 
> and re-enable the "checkstyle".
>  
>  
> Cheers,
> Marco
>  
> On Fri, 2017-12-15 at 13:51 +, Dave Barach (dbarach) wrote:
> With a bit of fiddling, I was able to fix gerrit 9440 so that indent 2.2.10 
> and 2.2.11 appear to produce identical results...
>  
> HTH... Dave
>  
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
> Behalf Of Gabriel Ganne
> Sent: Friday, December 15, 2017 8:42 AM
> To: Billy McFall ; Marco Varlese 
> Cc: Damjan Marion (damarion) ; vpp-dev 
> 
> Subject: Re: [vpp-dev] openSUSE build fails
>  
> Hi,
> 
>  
> 
> If you browse the source http://hg.savannah.gnu.org/hgweb/indent/
> 
> The tag 2.2.11  is there, the source seems updated regularly.
> 
>  
> 
> Best regards,
> 
>  
> 
> --
> 
> Gabriel Ganne
> 
> From: vpp-dev-boun...@lists.fd.io  on behalf of 
> Billy McFall 
> Sent: Friday, December 15, 2017 2:26:42 PM
> To: Marco Varlese
> Cc: Damjan Marion (damarion); vpp-dev
> Subject: Re: [vpp-dev] openSUSE build fails
>  
>  
>  
> On Fri, Dec 15, 2017 at 5:15 AM, Marco Varlese  wrote:
> Hi Damjan,
>  
> On Fri, 2017-12-15 at 09:06 +, Damjan Marion (damarion) wrote:
>  
>  
> 
> On 15 Dec 2017, at 08:52, Marco Varlese  wrote:
>  
> Damjan,
> 
> On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:
> 
> Folks,
> 
> I'm hearing from multiple people that OpenSUSE verify job is failing (again).
> I haven't heard (or read) anything over the mailing list otherwise I would 
> have
> looked into it.
> Also, if you hear anything like that you can always ping me directly and I 
> will
> look into it...
>  
> yes, people pinging me...
> See 
> https://gerrit.fd.io/r/#/c/9440/
>  
> also:
>  
> https://gerrit.fd.io/r/#/c/9813/ - abandoned but it shows that something was 
> wrong
>  
> Ok, so just summarizing our conversation on IRC for others too.
>  
> That issue is connected to the different versions of INDENT (C checkstyle) 
> installed on the different distros.
>  
> openSUSE runs 2.2.10 whilst CentOS and Ubuntu run 2.2.11
>  
> What strikes me is that the upstream repo https://ftp.gnu.org/gnu/indent/ has 
> 2.2.10 as last revision.
> Our indent package maintainer is looking at possible other sources where 
> Indent could "live" these days and will let me know as soon as she

Re: [vpp-dev] openSUSE build fails

2018-01-25 Thread Ni, Hongjun

Hi Ole,

I have no OpenSUSE at hand, and could not give it a try.

-Hongjun

From: Ole Troan [mailto:otr...@employees.org]
Sent: Friday, January 26, 2018 2:08 PM
To: Ni, Hongjun 
Cc: Dave Barach (dbarach) ; Marco Varlese 
; Gabriel Ganne ; Billy McFall 
; Damjan Marion (damarion) ; vpp-dev 

Subject: Re: [vpp-dev] openSUSE build fails

Hongjun,

This looks suspect:

03:32:31 APIGEN vlibmemory/memclnt.api.h 03:32:31 JSON API 
vlibmemory/memclnt.api.json 03:32:31 SyntaxError: invalid syntax 
(vppapigentab.py, line 11) 03:32:31 
WARNING:vppapigen:/w/workspace/vpp-verify-master-opensuse/build-root/rpmbuild/BUILD/vpp-18.04/build-data/../src/vlibmemory/memclnt.api:0:1:
 Old Style VLA: u8 data[0]; 03:32:31 Makefile:8794: recipe for target 
'vlibmemory/memclnt.api.h' failed 03:32:31 make[5]: *** 
[vlibmemory/memclnt.api.h] Error 1 03:32:31 make[5]: *** Waiting for unfinished 
jobs 03:32:31

Can you try running vppapigen manually on that platform?
Vppapigen —debug —input memclnt.api ...

Cheers
Ole

On 26 Jan 2018, at 06:38, Ni, Hongjun 
> wrote:
Hi all,

It seems that OpenSUSE build failed for this patch:
https://jenkins.fd.io/job/vpp-verify-master-opensuse/1285/console

Please help to take a

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Dave Barach (dbarach)
Sent: Friday, December 15, 2017 11:19 PM
To: Marco Varlese >; Gabriel Ganne 
>; Billy McFall 
>
Cc: Damjan Marion (damarion) >; 
vpp-dev >
Subject: Re: [vpp-dev] openSUSE build fails

Dear Marco,

Thanks very much...

Dave

From: Marco Varlese [mailto:mvarl...@suse.de]
Sent: Friday, December 15, 2017 9:06 AM
To: Dave Barach (dbarach) >; 
Gabriel Ganne >; Billy 
McFall >
Cc: Damjan Marion (damarion) >; 
vpp-dev >
Subject: Re: [vpp-dev] openSUSE build fails

We (at SUSE) are currently pushing an update to 2.2.11 for openSUSE in our 
repositories.
Once that's confirmed to be upstream, I will push a new patch to the 
ci-management repo to have the indent package upgraded to the latest version 
and re-enable the "checkstyle".

Cheers,
Marco

On Fri, 2017-12-15 at 13:51 +, Dave Barach (dbarach) wrote:
With a bit of fiddling, I was able to fix gerrit 9440 so that indent 2.2.10 and 
2.2.11 appear to produce identical results...

HTH... Dave

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Gabriel Ganne
Sent: Friday, December 15, 2017 8:42 AM
To: Billy McFall >; Marco Varlese 
>
Cc: Damjan Marion (damarion) >; 
vpp-dev >
Subject: Re: [vpp-dev] openSUSE build fails

Hi,

If you browse the source http://hg.savannah.gnu.org/hgweb/indent/

The tag 2.2.11  is there, the source seems updated regularly.

Best regards,

--

Gabriel Ganne

From: vpp-dev-boun...@lists.fd.io 
> on behalf of 
Billy McFall >
Sent: Friday, December 15, 2017 2:26:42 PM
To: Marco Varlese
Cc: Damjan Marion (damarion); vpp-dev
Subject: Re: [vpp-dev] openSUSE build fails

On Fri, Dec 15, 2017 at 5:15 AM, Marco Varlese 
> wrote:
Hi Damjan,

On Fri, 2017-12-15 at 09:06 +, Damjan Marion (damarion) wrote:

On 15 Dec 2017, at 08:52, Marco Varlese 
> wrote:

Damjan,

On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:
Folks,

I'm hearing from multiple people that OpenSUSE verify job is failing (again).
I haven't heard (or read) anything over the mailing list otherwise I would have
looked into it.
Also, if you hear anything like that you can always ping me directly and I will
look into it...

yes, people pinging me...
See

Re: [vpp-dev] openSUSE build fails

2018-01-25 Thread Ole Troan

Hongjun,

This looks suspect:
03:32:31 APIGEN vlibmemory/memclnt.api.h 03:32:31 JSON API 
vlibmemory/memclnt.api.json 03:32:31 SyntaxError: invalid syntax 
(vppapigentab.py, line 11) 03:32:31 
WARNING:vppapigen:/w/workspace/vpp-verify-master-opensuse/build-root/rpmbuild/BUILD/vpp-18.04/build-data/../src/vlibmemory/memclnt.api:0:1:
 Old Style VLA: u8 data[0]; 03:32:31 Makefile:8794: recipe for target 
'vlibmemory/memclnt.api.h' failed 03:32:31 make[5]: *** 
[vlibmemory/memclnt.api.h] Error 1 03:32:31 make[5]: *** Waiting for unfinished 
jobs 03:32:31


Can you try running vppapigen manually on that platform?
Vppapigen —debug —input memclnt.api ...

Cheers 
Ole


> On 26 Jan 2018, at 06:38, Ni, Hongjun  wrote:
> 
> Hi all,
>  
> It seems that OpenSUSE build failed for this patch:
> https://jenkins.fd.io/job/vpp-verify-master-opensuse/1285/console
>  
> Please help to take a 
>  
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
> Behalf Of Dave Barach (dbarach)
> Sent: Friday, December 15, 2017 11:19 PM
> To: Marco Varlese ; Gabriel Ganne ; 
> Billy McFall 
> Cc: Damjan Marion (damarion) ; vpp-dev 
> 
> Subject: Re: [vpp-dev] openSUSE build fails
>  
> Dear Marco,
>  
> Thanks very much...
>  
> Dave
>  
> From: Marco Varlese [mailto:mvarl...@suse.de] 
> Sent: Friday, December 15, 2017 9:06 AM
> To: Dave Barach (dbarach) ; Gabriel Ganne 
> ; Billy McFall 
> Cc: Damjan Marion (damarion) ; vpp-dev 
> 
> Subject: Re: [vpp-dev] openSUSE build fails
>  
> We (at SUSE) are currently pushing an update to 2.2.11 for openSUSE in our 
> repositories.
> Once that's confirmed to be upstream, I will push a new patch to the 
> ci-management repo to have the indent package upgraded to the latest version 
> and re-enable the "checkstyle".
>  
>  
> Cheers,
> Marco
>  
> On Fri, 2017-12-15 at 13:51 +, Dave Barach (dbarach) wrote:
> With a bit of fiddling, I was able to fix gerrit 9440 so that indent 2.2.10 
> and 2.2.11 appear to produce identical results...
>  
> HTH... Dave
>  
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
> Behalf Of Gabriel Ganne
> Sent: Friday, December 15, 2017 8:42 AM
> To: Billy McFall ; Marco Varlese 
> Cc: Damjan Marion (damarion) ; vpp-dev 
> 
> Subject: Re: [vpp-dev] openSUSE build fails
>  
> Hi,
> 
>  
> 
> If you browse the source http://hg.savannah.gnu.org/hgweb/indent/
> 
> The tag 2.2.11  is there, the source seems updated regularly.
> 
>  
> 
> Best regards,
> 
>  
> 
> --
> 
> Gabriel Ganne
> 
> From: vpp-dev-boun...@lists.fd.io  on behalf of 
> Billy McFall 
> Sent: Friday, December 15, 2017 2:26:42 PM
> To: Marco Varlese
> Cc: Damjan Marion (damarion); vpp-dev
> Subject: Re: [vpp-dev] openSUSE build fails
>  
>  
>  
> On Fri, Dec 15, 2017 at 5:15 AM, Marco Varlese  wrote:
> Hi Damjan,
>  
> On Fri, 2017-12-15 at 09:06 +, Damjan Marion (damarion) wrote:
>  
>  
> 
> On 15 Dec 2017, at 08:52, Marco Varlese  wrote:
>  
> Damjan,
> 
> On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:
> 
> Folks,
> 
> I'm hearing from multiple people that OpenSUSE verify job is failing (again).
> I haven't heard (or read) anything over the mailing list otherwise I would 
> have
> looked into it.
> Also, if you hear anything like that you can always ping me directly and I 
> will
> look into it...
>  
> yes, people pinging me...
> See 
> https://gerrit.fd.io/r/#/c/9440/
>  
> also:
>  
> https://gerrit.fd.io/r/#/c/9813/ - abandoned but it shows that something was 
> wrong
>  
> Ok, so just summarizing our conversation on IRC for others too.
>  
> That issue is connected to the different versions of INDENT (C checkstyle) 
> installed on the different distros.
>  
> openSUSE runs 2.2.10 whilst CentOS and Ubuntu run 2.2.11
>  
> What strikes me is that the upstream repo https://ftp.gnu.org/gnu/indent/ has 
> 2.2.10 as last revision.
> Our indent package maintainer is looking at possible other sources where 
> Indent could "live" these days and will let me know as soon as she finds out.
>  
> @Thomas Herbert, would you know the source where the Indent package on CentOS 
> come from? Maybe that could help...
>  
> Marco, I can't find the source. I'll look around a little more. From CentoOS 
> 7.4:
>  
> $ sudo yum provides indent
> :
> indent-2.2.11-13.el7.x86_64 : A GNU program for formatting C code
> Repo: base
> :
>  
> $ sudo repoquery -i indent
> Name: indent
> Version : 2.2.11
> Release : 13.el7
> Architecture: x86_64
> Size: 359131
> Packager: CentOS BuildSystem 
> Group

Re: [vpp-dev] openSUSE build fails

2018-01-25 Thread Ni, Hongjun

Hi all,

It seems that OpenSUSE build failed for this patch:
https://jenkins.fd.io/job/vpp-verify-master-opensuse/1285/console

Please help to take a look at it.  Thanks a lot.

Thanks,
Hongjun

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Dave Barach (dbarach)
Sent: Friday, December 15, 2017 11:19 PM
To: Marco Varlese ; Gabriel Ganne ; 
Billy McFall 
Cc: Damjan Marion (damarion) ; vpp-dev 
Subject: Re: [vpp-dev] openSUSE build fails

Dear Marco,

Thanks very much...

Dave

From: Marco Varlese [mailto:mvarl...@suse.de]
Sent: Friday, December 15, 2017 9:06 AM
To: Dave Barach (dbarach) >; 
Gabriel Ganne >; Billy 
McFall >
Cc: Damjan Marion (damarion) >; 
vpp-dev >
Subject: Re: [vpp-dev] openSUSE build fails

We (at SUSE) are currently pushing an update to 2.2.11 for openSUSE in our 
repositories.
Once that's confirmed to be upstream, I will push a new patch to the 
ci-management repo to have the indent package upgraded to the latest version 
and re-enable the "checkstyle".

Cheers,
Marco

On Fri, 2017-12-15 at 13:51 +, Dave Barach (dbarach) wrote:
With a bit of fiddling, I was able to fix gerrit 9440 so that indent 2.2.10 and 
2.2.11 appear to produce identical results...

HTH... Dave

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Gabriel Ganne
Sent: Friday, December 15, 2017 8:42 AM
To: Billy McFall >; Marco Varlese 
>
Cc: Damjan Marion (damarion) >; 
vpp-dev >
Subject: Re: [vpp-dev] openSUSE build fails

Hi,

If you browse the source http://hg.savannah.gnu.org/hgweb/indent/

The tag 2.2.11  is there, the source seems updated regularly.

Best regards,

--

Gabriel Ganne

From: vpp-dev-boun...@lists.fd.io 
> on behalf of 
Billy McFall >
Sent: Friday, December 15, 2017 2:26:42 PM
To: Marco Varlese
Cc: Damjan Marion (damarion); vpp-dev
Subject: Re: [vpp-dev] openSUSE build fails

On Fri, Dec 15, 2017 at 5:15 AM, Marco Varlese 
> wrote:
Hi Damjan,

On Fri, 2017-12-15 at 09:06 +, Damjan Marion (damarion) wrote:

On 15 Dec 2017, at 08:52, Marco Varlese 
> wrote:

Damjan,

On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:
Folks,

I'm hearing from multiple people that OpenSUSE verify job is failing (again).
I haven't heard (or read) anything over the mailing list otherwise I would have
looked into it.
Also, if you hear anything like that you can always ping me directly and I will
look into it...

yes, people pinging me...
See
https://gerrit.fd.io/r/#/c/9440/

also:

https://gerrit.fd.io/r/#/c/9813/
 - abandoned but it shows that something was wrong

Ok, so just summarizing our conversation on IRC for others too.

That issue is connected to the different versions of INDENT (C checkstyle) 
installed on the different distros.

openSUSE runs 2.2.10 whilst CentOS and Ubuntu run 2.2.11

What strikes me is that the upstream repo 
https://ftp.gnu.org/gnu/indent/
 has 2.2.10 as last revision.
Our indent package maintainer is looking at possible other sources where Indent 
could "live" these days and will let me know as soon as she finds out.

@Thomas Herbert, would you know the source where the Indent package on CentOS 
come from? Maybe that could help...

Marco, I can't find the source. I'll look around a little more. From

Re: [vpp-dev] What RPM contains vpp debug symbols?

2018-01-25 Thread Dave Wallace


Thanks for the info Billy!
-daw-

On 1/25/18 8:26 PM, Billy McFall wrote:
'make pkg-rpm' is currently not generating an RPM with debug symbols. 
There is a bug in  rpmbuild for packages with short names (i.e. - vpp) 
that was not allowing RPMs to be built upstream in CentOS and RHEL. 
The work around is to add a -0 to the package name to make it long 
enough. Much later after this change was merged, it was discovered 
that the debug RPM was not being built.


Thomas Herbert is tracking the issue. rpmbuild has been fixed in 
Fedora but that fix has not been pulled into CentOS or RHEL. Not sure 
when it will make it. Thomas can give more details, I am just 
regurgitating what he previously reported to me.


Billy McFall


On Thu, Jan 25, 2018 at 6:57 PM, Dave Wallace > wrote:


Does anyone know what RPM contains debug symbols?

Back in VPP 17.07 there used to be an RPM package called
vpp-debuginfo-*.x86_64.rpm, but that package is no longer
installed on nexus.fd.io  starting with
release 17.10


https://nexus.fd.io/content/repositories/fd.io.stable.1707.centos7/io/fd/vpp/vpp-debuginfo/17.07.01-release.x86_64/vpp-debuginfo-17.07.01-release.x86_64.rpm



Thanks,
-daw-

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





--
*Billy McFall*
Networking Group
CTO Office
*Red Hat*


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

Re: [vpp-dev] What RPM contains vpp debug symbols?

2018-01-25 Thread Billy McFall

'make pkg-rpm' is currently not generating an RPM with debug symbols. There
is a bug in  rpmbuild for packages with short names (i.e. - vpp) that was
not allowing RPMs to be built upstream in CentOS and RHEL. The work around
is to add a -0 to the package name to make it long enough. Much later after
this change was merged, it was discovered that the debug RPM was not being
built.

Thomas Herbert is tracking the issue. rpmbuild has been fixed in Fedora but
that fix has not been pulled into CentOS or RHEL. Not sure when it will
make it. Thomas can give more details, I am just regurgitating what he
previously reported to me.

Billy McFall

On Thu, Jan 25, 2018 at 6:57 PM, Dave Wallace  wrote:

> Does anyone know what RPM contains debug symbols?
>
> Back in VPP 17.07 there used to be an RPM package called
> vpp-debuginfo-*.x86_64.rpm, but that package is no longer installed on
> nexus.fd.io starting with release 17.10
>
> https://nexus.fd.io/content/repositories/fd.io.stable.
> 1707.centos7/io/fd/vpp/vpp-debuginfo/17.07.01-release.
> x86_64/vpp-debuginfo-17.07.01-release.x86_64.rpm
>
> Thanks,
> -daw-
>
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
>

-- 
*Billy McFall*
Networking Group
CTO Office
*Red Hat*
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] What RPM contains vpp debug symbols?

2018-01-25 Thread Dave Wallace


Does anyone know what RPM contains debug symbols?

Back in VPP 17.07 there used to be an RPM package called 
vpp-debuginfo-*.x86_64.rpm, but that package is no longer installed on 
nexus.fd.io starting with release 17.10


https://nexus.fd.io/content/repositories/fd.io.stable.1707.centos7/io/fd/vpp/vpp-debuginfo/17.07.01-release.x86_64/vpp-debuginfo-17.07.01-release.x86_64.rpm

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

Re: [vpp-dev] Howto implement L3 p2p tunnel interface without assigning IP to the interface?

2018-01-25 Thread Andreas Schultz

Ole Troan  schrieb am Do., 25. Jan. 2018 um 22:07 Uhr:

> > Not accepting IP[46] packets on any interface type that is not IP[46]
> enabled is a basic security feature. To IP4 enable an interface you have
> two option;
> > 1)   Assign it an IP address
> > 2)   Make it IP unnumbered to another interface that does have an
> address, e.g.
> > set int ip addr loop0 some-private-addr/32
> > set int unnumbered gtpu-tunnel-0 use loop0
> > set int unnumbered gtpu-tunnel-1 use loop0
> > set int unnumbered gtpu-tunnel-2 use loop0
> > etc…
> > It doesn’t have to be a loopback, I use that only as an example.
> >
> > To IP6 enable an interface instead of the unnumbered trick one can just
> do;
> > 1)   enable ip6 interface gtpu-tunnel0
>
> Although all IPv6 interfaces by definition have an IPv6 address (the IPv6
> link-local) I do wonder if we shouldn't allow for IP processing to be
> enabled for both IP4 and IP6 independently of having an address configured.
> (Of course that would imply that some protocols wouldn't work.)
>

ip4_sw_interface_enable_disable() and/or ip6_sw_interface_enable_disable()
did the trick. It works now without having to use the unnumbered option or
having to assign a IPv4 address. I didn't check IPv6, though.

Thanks for the help,
Andreas

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

Re: [vpp-dev] [csit-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

2018-01-25 Thread George Zhao

Congratulations, way to go.


From: csit-dev-boun...@lists.fd.io [mailto:csit-dev-boun...@lists.fd.io] On 
Behalf Of Dave Wallace
Sent: Wednesday, January 24, 2018 9:23 PM
To: vpp-dev@lists.fd.io; csit-...@lists.fd.io
Subject: [csit-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

Folks,

The VPP 18.01 Release artifacts are now available on nexus.fd.io

The ubuntu.xenial and centos packages can be installed following the recipe on 
the wiki: https://wiki.fd.io/view/VPP/Installing_VPP_binaries_from_packages

Thank you to all of the VPP community who have contributed to the 18.01 VPP 
Release.


Elvis has left the building!
-daw-
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Howto implement L3 p2p tunnel interface without assigning IP to the interface?

2018-01-25 Thread John Lo (loj)

Hi Andrea,

Typically a tunnel used for tx/rx of L3/IP payload would have IP address and 
optionally table-id set on the interface.  It will then allow packets to be 
routed into the tunnel for tx and, for rx packets, forward the payload IP 
packets using the correct fib-index.

I see that you are inserting FIB entries for tx to the tunnel. Then, you also 
need to enable the tunnel for IP forwarding on rx packets. The functions for it 
is ip4_sw_interface_enable_disable() or ip6_sw_interface_enable_disable() from 
ip4.h and ip6.h respectively.  If routine for IP into and from the tunnel is 
other than the global table, you still need to set tunnel interface with the 
desired table index and the programmed FIB entries.

Regards,
John

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Andreas Schultz
Sent: Thursday, January 25, 2018 11:34 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Howto implement L3 p2p tunnel interface without assigning IP 
to the interface?

Hi,

Short story:

The VPP tunnel implementation HOWTO [1] says that a L3 tunnel needs an IP 
address. How do I implement a P2P tunnel interface without assigning an IP 
address to it?

Long story:

I'm implementing a GTP-U User Plane Node that conforms to 3GPP TS 29.244 [2] & 
[3]. For each Sx Session a VPP tunnel interface is created (a Sx Session can 
consist of multiple GTP tunnels that all belong to the same UE IP). A reverse 
route for the UE IP is inserted into the FIB pointing to the session tunnel 
interface.
So far this all works nicely. However when a GTP-U packet arrives, a trace 
shows that it is decapsulated, handed to ip4-input and the immediatly dropped 
without any error indication:

00:00:59:474894: ip4-udp-lookup
  UDP: src-port 2152 dst-port 2152
00:00:59:474902: gtpu4-input
  GTPU decap from gtpu_session0 teid 1 next 1 error 0
00:00:59:474942: ip4-input
  ICMP: 10.180.125.105 -> 8.8.8.8
tos 0x00, ttl 63, length 84, checksum 0xa484
fragment id 0xfef7, flags DONT_FRAGMENT
  ICMP echo_request checksum 0xc7d
00:00:59:475013: ip4-drop
ICMP: 10.180.125.105 -> 8.8.8.8
  tos 0x00, ttl 63, length 84, checksum 0xa484
  fragment id 0xfef7, flags DONT_FRAGMENT
ICMP echo_request checksum 0xc7d
00:00:59:475020: error-drop
  ip4-input: valid ip4 packets
I have traced the cause of the drop to vnet_feature_arc_start and from there to 
vnet_get_config_data. It turns out the IP feature is not configured on the 
ARC/sw_if_index combination.
When I manually add a IP address to the tunnel interface it starts to work.

I already looked at the PPPoE and the IPSec plugins, They must be doing 
something simmilar, but I can't spot the difference.

So how do I get the tunnel interface to work without having to add an IP 
address to it? Or, do I need to handle the input/decap chain differently?

My current code is at: 
https://github.com/RoadRunnr/vpp/tree/feature/gtp-dp/src/plugins/gtpdp

Thanks
Andreas

1: https://wiki.fd.io/view/VPP/How_to_add_a_tunnel_encapsulation
2: https://github.com/RoadRunnr/vpp/tree/feature/gtp-dp
3: 
http://www.etsi.org/deliver/etsi_ts/129200_129299/129244/14.01.00_60/ts_129244v140100p.pdf

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

Re: [vpp-dev] Howto implement L3 p2p tunnel interface without assigning IP to the interface?

2018-01-25 Thread Neale Ranns (nranns)

Hi Andreas,

Not accepting IP[46] packets on any interface type that is not IP[46] enabled 
is a basic security feature. To IP4 enable an interface you have two option;

1)   Assign it an IP address

2)   Make it IP unnumbered to another interface that does have an address, 
e.g.
set int ip addr loop0 some-private-addr/32
set int unnumbered gtpu-tunnel-0 use loop0
set int unnumbered gtpu-tunnel-1 use loop0
set int unnumbered gtpu-tunnel-2 use loop0
etc…
It doesn’t have to be a loopback, I use that only as an example.

To IP6 enable an interface instead of the unnumbered trick one can just do;

1)   enable ip6 interface gtpu-tunnel0

hth
/neale

From:  on behalf of Andreas Schultz 

Date: Thursday, 25 January 2018 at 17:34
To: "vpp-dev@lists.fd.io" 
Subject: [vpp-dev] Howto implement L3 p2p tunnel interface without assigning IP 
to the interface?

Hi,

Short story:

The VPP tunnel implementation HOWTO [1] says that a L3 tunnel needs an IP 
address. How do I implement a P2P tunnel interface without assigning an IP 
address to it?

Long story:

I'm implementing a GTP-U User Plane Node that conforms to 3GPP TS 29.244 [2] & 
[3]. For each Sx Session a VPP tunnel interface is created (a Sx Session can 
consist of multiple GTP tunnels that all belong to the same UE IP). A reverse 
route for the UE IP is inserted into the FIB pointing to the session tunnel 
interface.
So far this all works nicely. However when a GTP-U packet arrives, a trace 
shows that it is decapsulated, handed to ip4-input and the immediatly dropped 
without any error indication:

00:00:59:474894: ip4-udp-lookup
  UDP: src-port 2152 dst-port 2152
00:00:59:474902: gtpu4-input
  GTPU decap from gtpu_session0 teid 1 next 1 error 0
00:00:59:474942: ip4-input
  ICMP: 10.180.125.105 -> 8.8.8.8
tos 0x00, ttl 63, length 84, checksum 0xa484
fragment id 0xfef7, flags DONT_FRAGMENT
  ICMP echo_request checksum 0xc7d
00:00:59:475013: ip4-drop
ICMP: 10.180.125.105 -> 8.8.8.8
  tos 0x00, ttl 63, length 84, checksum 0xa484
  fragment id 0xfef7, flags DONT_FRAGMENT
ICMP echo_request checksum 0xc7d
00:00:59:475020: error-drop
  ip4-input: valid ip4 packets
I have traced the cause of the drop to vnet_feature_arc_start and from there to 
vnet_get_config_data. It turns out the IP feature is not configured on the 
ARC/sw_if_index combination.
When I manually add a IP address to the tunnel interface it starts to work.

I already looked at the PPPoE and the IPSec plugins, They must be doing 
something simmilar, but I can't spot the difference.

So how do I get the tunnel interface to work without having to add an IP 
address to it? Or, do I need to handle the input/decap chain differently?

My current code is at: 
https://github.com/RoadRunnr/vpp/tree/feature/gtp-dp/src/plugins/gtpdp

Thanks
Andreas

1: https://wiki.fd.io/view/VPP/How_to_add_a_tunnel_encapsulation
2: https://github.com/RoadRunnr/vpp/tree/feature/gtp-dp
3: 
http://www.etsi.org/deliver/etsi_ts/129200_129299/129244/14.01.00_60/ts_129244v140100p.pdf

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

[vpp-dev] Howto implement L3 p2p tunnel interface without assigning IP to the interface?

2018-01-25 Thread Andreas Schultz

Hi,

Short story:

The VPP tunnel implementation HOWTO [1] says that a L3 tunnel needs an IP
address. How do I implement a P2P tunnel interface without assigning an IP
address to it?

Long story:

I'm implementing a GTP-U User Plane Node that conforms to 3GPP TS 29.244
[2] & [3]. For each Sx Session a VPP tunnel interface is created (a Sx
Session can consist of multiple GTP tunnels that all belong to the same UE
IP). A reverse route for the UE IP is inserted into the FIB pointing to the
session tunnel interface.
So far this all works nicely. However when a GTP-U packet arrives, a trace
shows that it is decapsulated, handed to ip4-input and the immediatly
dropped without any error indication:

00:00:59:474894: ip4-udp-lookup
  UDP: src-port 2152 dst-port 2152
00:00:59:474902: gtpu4-input
  GTPU decap from gtpu_session0 teid 1 next 1 error 0
00:00:59:474942: ip4-input
  ICMP: 10.180.125.105 -> 8.8.8.8
tos 0x00, ttl 63, length 84, checksum 0xa484
fragment id 0xfef7, flags DONT_FRAGMENT
  ICMP echo_request checksum 0xc7d
00:00:59:475013: ip4-drop
ICMP: 10.180.125.105 -> 8.8.8.8
  tos 0x00, ttl 63, length 84, checksum 0xa484
  fragment id 0xfef7, flags DONT_FRAGMENT
ICMP echo_request checksum 0xc7d
00:00:59:475020: error-drop
  ip4-input: valid ip4 packets

I have traced the cause of the drop to vnet_feature_arc_start and from
there to vnet_get_config_data. It turns out the IP feature is not
configured on the ARC/sw_if_index combination.
When I manually add a IP address to the tunnel interface it starts to work.

I already looked at the PPPoE and the IPSec plugins, They must be doing
something simmilar, but I can't spot the difference.

So how do I get the tunnel interface to work without having to add an IP
address to it? Or, do I need to handle the input/decap chain differently?

My current code is at:
https://github.com/RoadRunnr/vpp/tree/feature/gtp-dp/src/plugins/gtpdp

Thanks
Andreas

1: https://wiki.fd.io/view/VPP/How_to_add_a_tunnel_encapsulation
2: https://github.com/RoadRunnr/vpp/tree/feature/gtp-dp
3:
http://www.etsi.org/deliver/etsi_ts/129200_129299/129244/14.01.00_60/ts_129244v140100p.pdf
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP performance tuning guide

2018-01-25 Thread Kinsella, Ray


Hi Charlie,


Please see this preso and associated paper from Kubecon - it is a pretty 
comprehensive guide on where to start.


https://wiki.fd.io/images/3/31/Benchmarking-sw-data-planes-Dec5_2017.pdf

Also consider replicating the CSIT test environment locally.
It is very well documented and you can then inspect the best way to 
benchmark VPP etc.


Ray K


On 24/01/2018 21:23, Li, Charlie wrote:

Hi All,

I am looking for some guidance on how to tune the VPP performance, specifically 
how to tune the IP Forwarding performance for small packets.

Appreciate if someone can point me to some documents or online resources on 
this topic.

My setup is simple, just an XL710-QDA2 NIC card with two 40G ports and VPP is 
configured to forward IP traffic between the two ports.

Basically I am using the default /etc/vpp/startup.conf (with PCI device address 
and core numbers modified). The throughput for bi-directional traffic with 
small packets is far below line rate. Throwing more cores does not seem to 
improve.

Regards,
Charlie Li

___
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] Build triggering on a simple commit message update?

2018-01-25 Thread Ed Kern (ejk)



On Jan 25, 2018, at 12:59 AM, Marco Varlese 
> wrote:

Hi Ed,

On Thu, 2018-01-25 at 00:28 +, Ed Kern (ejk) wrote:
hey marco,

What your looking for (imo) is not a gerrit change. Its a jenkins side change

 https://gerrit.fd.io/r/10237
Thank you for showing the path; I am not very familiar with Jenkins, etc. so 
this example is very much appreciated!


Note: I also included not running on trivial rebase which may freak some people 
out.
Yeah, possibly that should be avoided...


Well if the goal is to reduce unnecessary cycles ill throw in two little bits:
1. Just because you add this to the verify set of jobs doesnt mean you also 
have to remove from the merge set
(which also runs a make test but not a virl run)
2. trivial rebase checks like this are as much religion as anything.  So it 
doesnt hurt to float it as well and see
if anyone explodes



Ed

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

Re: [vpp-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

2018-01-25 Thread Kinsella, Ray


W00t!

On 25/01/2018 05:23, Dave Wallace wrote:

Folks,

The VPP 18.01 Release artifacts are now available on nexus.fd.io

The ubuntu.xenial and centos packages can be installed following the 
recipe on the wiki: 
https://wiki.fd.io/view/VPP/Installing_VPP_binaries_from_packages


Thank you to all of the VPP community who have contributed to the 18.01 
VPP Release.



Elvis has left the building!
-daw-



___
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 18.01 Release artifacts are now available on nexus.fd.io

2018-01-25 Thread Dave Barach (dbarach)

Congrats to DaveW and the rest of the fd.io vpp team on the 18.01 release!

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Dave Wallace
Sent: Thursday, January 25, 2018 12:23 AM
To: vpp-dev@lists.fd.io; csit-...@lists.fd.io
Subject: [vpp-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

Folks,

The VPP 18.01 Release artifacts are now available on nexus.fd.io

The ubuntu.xenial and centos packages can be installed following the recipe on 
the wiki: https://wiki.fd.io/view/VPP/Installing_VPP_binaries_from_packages

Thank you to all of the VPP community who have contributed to the 18.01 VPP 
Release.


Elvis has left the building!
-daw-
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

2018-01-25 Thread Jerome Tollet (jtollet)

Congratulations!

De :  au nom de Dave Wallace 
Date : mercredi 24 janvier 2018 à 21:23
À : "vpp-dev@lists.fd.io" , "csit-...@lists.fd.io" 

Objet : [vpp-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

Folks,

The VPP 18.01 Release artifacts are now available on nexus.fd.io

The ubuntu.xenial and centos packages can be installed following the recipe on 
the wiki: https://wiki.fd.io/view/VPP/Installing_VPP_binaries_from_packages

Thank you to all of the VPP community who have contributed to the 18.01 VPP 
Release.


Elvis has left the building!
-daw-


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

Re: [vpp-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

2018-01-25 Thread Marco Varlese

Great news! Congrats everybody!!!
On Thu, 2018-01-25 at 00:23 -0500, Dave Wallace wrote:
> 
> Folks,
> 
>   
> 
>   The VPP 18.01 Release artifacts are now available on nexus.fd.io
> 
>   
> 
>   The ubuntu.xenial and centos packages can be installed following
>   the recipe on the wiki:
>   https://wiki.fd.io/view/VPP/Installing_VPP_binaries_from_packages
> 
>   
> 
>   Thank you to all of the VPP community who have contributed to the
>   18.01 VPP Release.
> 
>   
> 
>   
> 
>   Elvis has left the building!
> 
>   -daw-
> 
>   
> 
> 
>   
> 
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [csit-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

2018-01-25 Thread Luke, Chris

Woohoo!

From: csit-dev-boun...@lists.fd.io [mailto:csit-dev-boun...@lists.fd.io] On 
Behalf Of Dave Wallace
Sent: Thursday, January 25, 2018 0:23
To: vpp-dev@lists.fd.io; csit-...@lists.fd.io
Subject: [csit-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

Folks,

The VPP 18.01 Release artifacts are now available on nexus.fd.io

The ubuntu.xenial and centos packages can be installed following the recipe on 
the wiki: https://wiki.fd.io/view/VPP/Installing_VPP_binaries_from_packages

Thank you to all of the VPP community who have contributed to the 18.01 VPP 
Release.


Elvis has left the building!
-daw-
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] openSUSE build fails

Re: [vpp-dev] openSUSE build fails

Re: [vpp-dev] openSUSE build fails

Re: [vpp-dev] openSUSE build fails

Re: [vpp-dev] openSUSE build fails

Re: [vpp-dev] What RPM contains vpp debug symbols?

Re: [vpp-dev] What RPM contains vpp debug symbols?

[vpp-dev] What RPM contains vpp debug symbols?

Re: [vpp-dev] Howto implement L3 p2p tunnel interface without assigning IP to the interface?

Re: [vpp-dev] [csit-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

Re: [vpp-dev] Howto implement L3 p2p tunnel interface without assigning IP to the interface?

Re: [vpp-dev] Howto implement L3 p2p tunnel interface without assigning IP to the interface?

[vpp-dev] Howto implement L3 p2p tunnel interface without assigning IP to the interface?

Re: [vpp-dev] VPP performance tuning guide

Re: [vpp-dev] Build triggering on a simple commit message update?

Re: [vpp-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

Re: [vpp-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

Re: [vpp-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

Re: [vpp-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

Re: [vpp-dev] [csit-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

20 matches

Site Navigation

Mail list logo

Footer information