Re: [vpp-dev] VNET classifier table/session

[Harish Patil]

Hi Andrew/all,
I was going thru' some of the code/doc pointers.
As I said I'm using relatively older VPP releases (16.09/17.01).
With regards to IPFIX (using VNET classifier functionality),  I do not see
any support for sending real flow statistics via IPFIX templates.
I just see that plain IPFIX templates can be sent out periodically to the
collector but with no other information entities (except packetTotalCount
which is manually calculated).
So I am trying to know what is the minimum version we need to move forward
with in order to claim basic IPFIX support? I see that 17.07 release added
FlowProbe plugin which implements some of the information entities.
Pls let me know.
Thanks,

Harish

On Tue, Jan 15, 2019 at 9:45 AM Harish Patil  wrote:

> Hi Andrew,
> Thanks much for the pointers.
> Shall go thru' them and revert back if I have further questions.
> Thanks,
>
> Harish
>
> On Tue, Jan 15, 2019 at 2:56 AM Andrew  Yourtchenko 
> wrote:
>
>> Hi Harish,
>>
>> A few links that might be helpful:
>>
>> https://wiki.fd.io/view/VPP/Introduction_To_N-tuple_Classifiers ?
>>
>> https://wiki.fd.io/view/VPP/SecurityGroups#Existing_functionality
>>
>> It talks about it more from the code perspective but hopefully this
>> should clarify things how it all works underneath...
>>
>> And an example with CLI syntax for use of classifier with IPFIX:
>>
>> https://www.mail-archive.com/vpp-dev@lists.fd.io/msg01820.html
>>
>> --a
>>
>> On 15 Jan 2019, at 08:11, Harish Patil  wrote:
>>
>> Hi,
>>
>> Can you please provide few examples (with right syntax and little
>> explanation) on to how to use VNET classify table and classify session in
>> relatively older VPP releases.
>>
>>  "classify table [miss-next|l2-miss_next|acl-miss-next ]"
>>  "\n mask  buckets  [skip ] [match ] [del]",
>>
>>
>> "classify session [hit-next|l2-hit-next|acl-hit-next ]"
>>"\n table-index  match [hex] [l2] [l3 ip4] [opaque-index ]",
>> Thanks,
>>
>> Harish
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>>
>> View/Reply Online (#11918): https://lists.fd.io/g/vpp-dev/message/11918
>> Mute This Topic: https://lists.fd.io/mt/29122272/675608
>> Group Owner: vpp-dev+ow...@lists.fd.io
>> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [ayour...@gmail.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
>>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11956): https://lists.fd.io/g/vpp-dev/message/11956
Mute This Topic: https://lists.fd.io/mt/29122272/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP 19.01 Release Milestone RC2 is Wednesday 23 January 2019

[Andrew Yourtchenko]

Hi all,

A gentle reminder that VPP 19.01 RC2 is this Wednesday January 23rd.

Note: After Wednesday's RC2 Milestone, only critical bug fixes will be
merged into stable/1901.

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 and include the jira ticket number into the commit
message.

--a

p.s. There were a few outstanding coverity issues, however, as per
Dave's email, it is in maintenance mode
(https://community.synopsys.com/s/article/Coverity-Scan-Update), so we
can not do much about them at this time.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11955): https://lists.fd.io/g/vpp-dev/message/11955
Mute This Topic: https://lists.fd.io/mt/29223583/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP 19.01 RC1 milestone is complete

[Andrew Yourtchenko]

Hi all,

The VPP 19.01 RC1 milestone is now fully complete.

The VPP 19.01 release branch (stable/1901) has been created, along
with the associated nexus and packagecloud repo's.

vpp master branch is  open for all patches slated for VPP 19.04
(and beyond).

vpp stable/1901 is now also open - but for bug fix patches only.

Per the standard process, all bug fixes to the stable branch should
follow the best practices:

All bug fixes must be double-committed to the release throttle as
well as to the master branch
Commit first to the release throttle, then "git cherry-pick" into master
Manual merges may be required, depending on the degree of
divergence between throttle and master

All bug fixes need to have a Jira ticket
Please put Jira IDs into the commit messages.
Please use the same Jira ID for both the stable branch and master.

I tested the Ubuntu and Centos packages for stable/1901 & master on
x86 following the directions on this wiki page:
https://wiki.fd.io/view/VPP/Installing_VPP_binaries_from_packages;

Thanks to Juraj Linkes for testing the ARM packages for Ubuntu.

Please let me know if there are any issues downloading/installing the artifacts.

A lot of thanks to Ed Warnicke, Eric Ball, Damjan Marion, Paul
Vinciguerra and Ole Troan for the help during this RC1 milestone
process.

--a
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11954): https://lists.fd.io/g/vpp-dev/message/11954
Mute This Topic: https://lists.fd.io/mt/29222971/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] debian/ubuntu packaging rework

[Damjan Marion via Lists.Fd.Io]

Dear all,

I just submitted debian/ubuntu packaging rework patch[1], and would like to 
hear feedback from people:
Instead of hardcoded shell scripts it uses CMake components to put file into 
right package, so for example:

install(FILES foo.txt DESTINATION share/vpp COMPONENT vpp-dev)

means that file will go into vpp-dev package.

Also I changed packaging, so now it looks like:

libvppinfra
libvppinfra-dev
vpp
vpp-api-python
vpp-dbg
vpp-dev
vpp-plugin-dpdk
vpp-plugin-misc

Patch needs a bit of polishing, but before that i would like to hear feedback...

Thanks,

-- 
Damjan

[1] https://gerrit.fd.io/r/#/c/16882/


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11953): https://lists.fd.io/g/vpp-dev/message/11953
Mute This Topic: https://lists.fd.io/mt/29200870/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] IpSec API call ikev2_set_profile_auth causes VPP to crash

[Neale Ranns via Lists.Fd.Io]

Hi Michal,

Thanks for the fixes. I’ll merge them when they verify.

/Neale


De :  au nom de "Michal Cmarada via Lists.Fd.Io" 

Répondre à : "Michal Cmarada -X (mcmarada - PANTHEON TECHNOLOGIES at Cisco)" 

Date : vendredi 18 janvier 2019 à 13:35
À : "vpp-dev@lists.fd.io" , "hc2...@lists.fd.io" 

Cc : "vpp-dev@lists.fd.io" 
Objet : [vpp-dev] IpSec API call ikev2_set_profile_auth causes VPP to crash

Hi,

I was testing IpSec API via honeycomb and when we called ikev2_set_profile_auth 
with “data” and “data_length” set, vpp crashed. When investigating we found out 
that “data_length” is not processed correctly. I prepared a patch that fixes 
this error. It was verified using HC via api call.
Master: https://gerrit.fd.io/r/#/c/16869/
Stable 19.01: https://gerrit.fd.io/r/#/c/16870/

Can someone take a look at this fix. Thanks

Michal

[ttps://www.cisco.com/c/dam/m/en_us/signaturetool/images/banners/standard/06_standard_graphic.png]




Michal Cmarada
Engineer - Software
mcmar...@cisco.com
Tel:










Cisco Systems, Inc.



Slovakia
cisco.com



[ttp://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]

Think before you print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here
 for Company Registration Information.







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11952): https://lists.fd.io/g/vpp-dev/message/11952
Mute This Topic: https://lists.fd.io/mt/29198001/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] wireshark vpp dispatch trace dissector merged

[Dave Barach via Lists.Fd.Io]

You must have handed wireshark a trace from an older VPP image which used 
WTAP_ENCAP_USER13 = 160, instead of the official WTAP_ENCAP_VPP = 280.

The encap type code that vpp writes changed on or about 1/9. Look for a commit 
entitled “Use the official libpcap file type” w/ SHA-1 
7b01e9e897c8f780e79ca6e64c72d700bd27f86e.

I guess you answered your own question regarding a quick way to handle that 
problem. You could also write a ten-line program to update the file type in 
place. There is no chance whatsoever of upstreaming a patch to dissect 
WTAP_ENCAP_USER13.

HTH... Dave

From: Benoit Ganne (bganne) 
Sent: Friday, January 18, 2019 6:42 AM
To: Dave Barach (dbarach) ; vpp-dev@lists.fd.io
Subject: RE: wireshark vpp dispatch trace dissector merged

I can confirm : I just cloned the master branch from the wireshark repository, 
compiled and it worked.
A minor possible improvement though: I had to go to Preferences > Protocols > 
DLT_USER > Edit to add an association between the VPP dissector and 
DLT_USER=160 so that wireshark recognize & decode the traces as VPP traces. It 
would be nice to have our own trace id associated out-of-the-box.

Best,
Ben

From: vpp-dev@lists.fd.io 
mailto:vpp-dev@lists.fd.io>> On Behalf Of Dave Barach via 
Lists.Fd.Io
Sent: jeudi 17 janvier 2019 14:12
To: vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: [vpp-dev] wireshark vpp dispatch trace dissector merged

I’m pleased to announce that our dispatch trace wireshark dissector has been 
merged. At some point in the indefinite future, everyone’s favorite distro will 
include a copy of wireshark which knows how to dissect vpp dispatch trace pcap 
files.

I’ll update the docs accordingly.

Dave

From: bugzilla-dae...@wireshark.org 
mailto:bugzilla-dae...@wireshark.org>>
Sent: Thursday, January 17, 2019 6:32 AM
To: wiresh...@barachs.net
Subject: [Bug 15411] [dissector] Add dissector for vector packet processing 
dispatch traces

Comment # 2 on 
bug 15411 from 
Gerrit Code Review

Change 31466 merged by Anders Broman:

VPP: add vpp graph dispatch trace dissector



https://code.wireshark.org/review/31466


You are receiving this mail because:

  *   You reported the bug.
  *   You are the assignee for the bug.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11951): https://lists.fd.io/g/vpp-dev/message/11951
Mute This Topic: https://lists.fd.io/mt/29172119/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] IpSec API call ikev2_set_profile_auth causes VPP to crash

[Michal Cmarada via Lists.Fd.Io]

Hi,

I was testing IpSec API via honeycomb and when we called ikev2_set_profile_auth 
with "data" and "data_length" set, vpp crashed. When investigating we found out 
that "data_length" is not processed correctly. I prepared a patch that fixes 
this error. It was verified using HC via api call.
Master: https://gerrit.fd.io/r/#/c/16869/
Stable 19.01: https://gerrit.fd.io/r/#/c/16870/

Can someone take a look at this fix. Thanks

Michal

[https://www.cisco.com/c/dam/m/en_us/signaturetool/images/banners/standard/06_standard_graphic.png]




Michal Cmarada
Engineer - Software
mcmar...@cisco.com
Tel:










Cisco Systems, Inc.



Slovakia
cisco.com



[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]

Think before you print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here
 for Company Registration Information.







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11950): https://lists.fd.io/g/vpp-dev/message/11950
Mute This Topic: https://lists.fd.io/mt/29198001/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] wireshark vpp dispatch trace dissector merged

[Benoit Ganne (bganne) via Lists.Fd.Io]

I can confirm : I just cloned the master branch from the wireshark repository, 
compiled and it worked.
A minor possible improvement though: I had to go to Preferences > Protocols > 
DLT_USER > Edit to add an association between the VPP dissector and 
DLT_USER=160 so that wireshark recognize & decode the traces as VPP traces. It 
would be nice to have our own trace id associated out-of-the-box.

Best,
Ben

From: vpp-dev@lists.fd.io  On Behalf Of Dave Barach via 
Lists.Fd.Io
Sent: jeudi 17 janvier 2019 14:12
To: vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: [vpp-dev] wireshark vpp dispatch trace dissector merged

I’m pleased to announce that our dispatch trace wireshark dissector has been 
merged. At some point in the indefinite future, everyone’s favorite distro will 
include a copy of wireshark which knows how to dissect vpp dispatch trace pcap 
files.

I’ll update the docs accordingly.

Dave

From: bugzilla-dae...@wireshark.org 
mailto:bugzilla-dae...@wireshark.org>>
Sent: Thursday, January 17, 2019 6:32 AM
To: wiresh...@barachs.net
Subject: [Bug 15411] [dissector] Add dissector for vector packet processing 
dispatch traces

Comment # 2 on 
bug 15411 from 
Gerrit Code Review

Change 31466 merged by Anders Broman:

VPP: add vpp graph dispatch trace dissector



https://code.wireshark.org/review/31466


You are receiving this mail because:

  *   You reported the bug.
  *   You are the assignee for the bug.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11949): https://lists.fd.io/g/vpp-dev/message/11949
Mute This Topic: https://lists.fd.io/mt/29172119/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] wireshark vpp dispatch trace dissector merged

[Marco Varlese]

That's great !!!

On Thu, 2019-01-17 at 13:11 +, Dave Barach via Lists.Fd.Io wrote:
> 
> 
> I’m pleased to announce that our dispatch trace wireshark dissector has been
> merged. At some point in the indefinite future, everyone’s favorite distro
> will include a copy of wireshark which knows
>  how to dissect vpp dispatch trace pcap files.
>  
> I’ll update the docs accordingly.
>  
> Dave
>  
> 
> 
> From: bugzilla-dae...@wireshark.org 
> 
> 
> Sent: Thursday, January 17, 2019 6:32 AM
> 
> To: wiresh...@barachs.net
> 
> Subject: [Bug 15411] [dissector] Add dissector for vector packet processing
> dispatch traces
> 
> 
>  
> 
> Comment
>  # 2 on 
> bug 15411 from Gerrit Code Review
> 
> Change 31466 merged by Anders Broman:
> VPP: add vpp graph dispatch trace dissector
>  
> https://code.wireshark.org/review/31466
> 
> 
> 
> 
> You are receiving this mail because:
> 
> 
> 
> You reported the bug.
> You are the assignee for the bug.
> 
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-Links: You receive all messages sent to this group.
> View/Reply Online (#11939): https://lists.fd.io/g/vpp-dev/message/11939
> Mute This Topic: https://lists.fd.io/mt/29172119/675056
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [mvarl...@suse.de]-=-=-=-=-
> =-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11948): https://lists.fd.io/g/vpp-dev/message/11948
Mute This Topic: https://lists.fd.io/mt/29172119/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP statistics

[Ole Troan]

> Statistics handling did change in !8.10, see:
>   https://docs.fd.io/vpp/18.10/md_src_vpp_stats_stats.html
>  
> there is no longer an exporter thread, instead there is a shared memory 
> segment from which your client can read the stats at the period of your 
> choosing.

Yep, although there is still a thread that calculates a few aggregate counters.
Like input rate, node runtime stats etc.

Cheers,
Ole

> De :  au nom de "satish.gu...@gmail.com" 
> 
> Date : vendredi 18 janvier 2019 à 07:09
> À : "vpp-dev@lists.fd.io" 
> Objet : [vpp-dev] VPP statistics
>  
> Hi All,
> 
> One query on the VPP statistics.
> In the fd.io wiki: 
> https://wiki.fd.io/view/VPP/Using_VPP_In_A_Multi-thread_Model
> It's mentioned that VPP statistics get handled by main thread.
> However, with 18.01 version, I see a separate threads for stats. Is this a 
> recent change in 18.10 ?
> 
> vpp# show threads
> ID NameTypeLWP Sched Policy (Priority)  lcore 
>  Core   Socket State
> 0  vpp_main31  other (0)0 
>  0  0
> 1  vpp_wk_0workers 157 other (0)1 
>  1  0
> 2  vpp_wk_1workers 158 other (0)2 
>  2  0
> 3  vpp_wk_2workers 159 other (0)3 
>  3  0
> 4   stats   160 other (0) 
>0  0  0
> 
> If this is a recent change, Is there any way, we can control this behavior ( 
> getting a separate thread for stats or not ).
> 
> Thanks & Regards,
> Satish
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#11946): https://lists.fd.io/g/vpp-dev/message/11946
> Mute This Topic: https://lists.fd.io/mt/29195591/675193
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [otr...@employees.org]
> -=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11947): https://lists.fd.io/g/vpp-dev/message/11947
Mute This Topic: https://lists.fd.io/mt/29195591/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP statistics

[Neale Ranns via Lists.Fd.Io]

Hi Satish,

Statistics handling did change in !8.10, see:
  https://docs.fd.io/vpp/18.10/md_src_vpp_stats_stats.html

there is no longer an exporter thread, instead there is a shared memory segment 
from which your client can read the stats at the period of your choosing.

/neale


De :  au nom de "satish.gu...@gmail.com" 

Date : vendredi 18 janvier 2019 à 07:09
À : "vpp-dev@lists.fd.io" 
Objet : [vpp-dev] VPP statistics

Hi All,

One query on the VPP statistics.
In the fd.io wiki: https://wiki.fd.io/view/VPP/Using_VPP_In_A_Multi-thread_Model
It's mentioned that VPP statistics get handled by main thread.
However, with 18.01 version, I see a separate threads for stats. Is this a 
recent change in 18.10 ?
vpp# show threads
ID NameTypeLWP Sched Policy (Priority)  lcore  
Core   Socket State
0  vpp_main31  other (0)0  
0  0
1  vpp_wk_0workers 157 other (0)1  
1  0
2  vpp_wk_1workers 158 other (0)2  
2  0
3  vpp_wk_2workers 159 other (0)3  
3  0
4   stats   160 other (0)   
 0  0  0

If this is a recent change, Is there any way, we can control this behavior ( 
getting a separate thread for stats or not ).

Thanks & Regards,
Satish
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11946): https://lists.fd.io/g/vpp-dev/message/11946
Mute This Topic: https://lists.fd.io/mt/29195591/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-