Re: [vpp-dev] Classify session weird behavior

2019-04-04 Thread Raj
Hello all, I found a work around to this: { "classify-table": [ { "name": "table0", "classify-session": [ { "match": "00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:64:45:01:04:00:00

[vpp-dev] Classify session weird behavior

2019-03-28 Thread Raj
On Thu, Mar 28, 2019 at 4:38 PM Michal Cmarada -X (mcmarada - PANTHEON TECHNOLOGIES at Cisco) wrote: > > Raj: If you have more data available after testing, please provide them here. > Thanks My observation is when I use skip of 1, cli works fine while RESTCONF do not. Config using CLI: vpp#

Re: [vpp-dev] Classify session weird behavior

2019-03-28 Thread Michal Cmarada via Lists.Fd.Io
dev@lists.fd.io Subject: Re: [vpp-dev] Classify session weird behavior Where do you point into the session data vector argument when creating it ? IIRC you need to point to the point *before* the n-skip vectors - i.e. the argument needs to include the “skipped” data as well. That is if I you ha

Re: [vpp-dev] Classify session weird behavior

2019-03-28 Thread Andrew Yourtchenko
Where do you point into the session data vector argument when creating it ? IIRC you need to point to the point *before* the n-skip vectors - i.e. the argument needs to include the “skipped” data as well. That is if I you have skip 3 words and match 2, the session data vector to be passed as a

[vpp-dev] Classify session weird behavior

2019-03-28 Thread Michal Cmarada via Lists.Fd.Io
Hi VPP devs, Raj, We had an issue when configuring classify session for classify table, where the n_skip_vector value is more than zero. The same issue happens when I am creating the configuration over API or via vppctl. The match "k: " value is always all zeros