Re: [vpp-dev] The correct usage of "classify table" and "classify session" for IOAM traffic

2019-07-29 Thread Shwetha bhandari via Lists.Fd.Io
Hi Mojtaba, I suspect that this is due to IOAM decap being broken in 18.01+. Removal of IOAM metadata added at the IOAM decap node depends on the ACL match whose result is checked during v6 hbh processing. If decap fails IOAM options are leaked to host2 in the setup below. Linux kernel network

[vpp-dev] The correct usage of "classify table" and "classify session" for IOAM traffic

2019-07-28 Thread mojtaba . eshghi
[Edited Message Follows] Hi, I'm trying to extend the usage of the following configuration to use iperf: https://github.com/CiscoDevNet/iOAM/tree/master/scripts/vpp_sandbox/example/simple-ip6 The current problem is with the acls. Which are defined this way: set ioam-trace profile trace-type

[vpp-dev] The correct usage of "classify table" and "classify session" for IOAM traffic

2019-07-01 Thread mojtaba.eshghi
Hi, I'm trying to extend the usage of the following configuration to use iperf: https://github.com/CiscoDevNet/iOAM/tree/master/scripts/vpp_sandbox/example/simple-ip6 The current problem is with the acls. Which are defined this way: set ioam-trace profile trace-type 0x9 trace-elts 3