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 stack drops the packets when it sees the unknown HbH options. Can you confirm with tcpdump in the host2 to see if the packets containing IOAM are seen? I had tried a temporary fix to overcome this that I haven’t up-streamed – you could try these diffs<https://github.com/vpp-dev/vpp/commit/f76b770d52598e69da13eb3da9e55f0cac786889>. I am in transit/time-off at the moment and can try the setup on the latest later this week. Meanwhile if you get to try this please share the results.
Thanks, Shwetha From: <vpp-dev@lists.fd.io> on behalf of "mojtaba.esh...@ut.ac.ir" <mojtaba.esh...@ut.ac.ir> Date: Sunday, July 28, 2019 at 10:58 PM To: "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io> Subject: [vpp-dev] The correct usage of "classify table" and "classify session" for IOAM traffic [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 [cid:15619775655d19e2dd184be075379808@ut.ac.ir] The current problem is with the acls. Which are defined this way: set ioam-trace profile trace-type 0x9 trace-elts 3 trace-tsp 2 node-id 0x3 classify table miss-next ip6-node ip6-lookup mask l3 ip6 dst classify session acl-hit-next ip6-node ip6-lookup table-index 0 match l3 ip6 dst db03::02 ioam-decap flow1 set int input acl intfc host-l_c2 ip6-table 0 set int input acl intfc host-l_c1 ip6-table 0 The end-to-end ping6 works fine, but iperf doesn't work. When I don't use the mentioned acls and classifications, both iperf and ping work properly (but of course the ioam in this case does not work). Does anyone know how can I properly classify the traffic to apply the ioam? There are examples in https://docs.fd.io/vpp/18.04/ioam_plugin_doc.html. However, as I said they just work for the ping and not for any type of L4 traffic (the current config files are similar to what is prescribed in these docs). I'm using the stable release 18.01 Best Regards, Mojtaba
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13602): https://lists.fd.io/g/vpp-dev/message/13602 Mute This Topic: https://lists.fd.io/mt/32270029/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
