Ip4-inacl != ip4-classify. If you want packets to visit ip4-classify, you need to install a classify adjacency in the FIB. See .../ip/lookup.c / “ip route 1.2.3.4/8 via classify <table-index>” debug CLI command.
I understand that not having things work the way you expect them to is frustrating. I would love to be able to drop everything and answer questions immediately, but that’s not practicable. Thanks… Dave From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Dharmaray Kundargi Sent: Friday, July 14, 2017 8:12 AM To: vpp-dev@lists.fd.io Subject: Re: [vpp-dev] VPP classifier node plugin not invoked. I don’t see ip4-classify in the next nodes for ip4-inacl. I am using 16.04 . Any suggestions please? From: Dharmaray Kundargi Sent: Friday, July 14, 2017 10:29 AM To: 'vpp-dev@lists.fd.io' <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>> Subject: RE: [vpp-dev] VPP classifier node plugin not invoked. Thanks Shwetha I tried with setting for acl. There is some change in the output of packet tracer as below. I see the node ip4-inacl in the flow. But still ip4-classifier not seen and my node is also not hit. 15:32:15:849439: dpdk-input GigabitEthernet1b/0/0 rx queue 0 buffer 0x1a2a6: current data 14, length 856, free-list 0, totlen-nifb 0, trace 0x2e PKT MBUF: port 1, nb_segs 1, pkt_len 870 buf_len 2176, data_len 870, ol_flags 0x0, packet_type 0x10 Packet Types RTE_PTYPE_L3_IPV4 (0x0010) IPv4 packet without extension headers IP4: 00:0c:29:7a:a6:81 -> 00:50:56:92:fe:49 UDP: 10.10.122.117 -> 10.10.121.179 tos 0x00, ttl 64, length 856, checksum 0x2f59 fragment id 0x0000, flags DONT_FRAGMENT UDP: 36410 -> 4096 length 836, checksum 0xd9b9 15:32:15:849442: ip4-input-no-checksum UDP: 10.10.122.117 -> 10.10.121.179 tos 0x00, ttl 64, length 856, checksum 0x2f59 fragment id 0x0000, flags DONT_FRAGMENT UDP: 36410 -> 4096 length 836, checksum 0xd9b9 15:32:15:849446: ip4-inacl INACL: sw_if_index 6, next_index 1, table 0, offset 192 15:32:15:849448: ip4-lookup fib 0 adj-idx 3 : arp GigabitEthernet13/0/0 10.10.121.220/24 flow hash: 0x00000000 UDP: 10.10.122.117 -> 10.10.121.179 tos 0x00, ttl 64, length 856, checksum 0x2f59 fragment id 0x0000, flags DONT_FRAGMENT UDP: 36410 -> 4096 length 836, checksum 0xd9b9 15:32:15:849449: ip4-arp UDP: 10.10.122.117 -> 10.10.121.179 tos 0x00, ttl 64, length 856, checksum 0x2f59 fragment id 0x0000, flags DONT_FRAGMENT UDP: 36410 -> 4096 length 836, checksum 0xd9b9 15:32:15:849454: error-drop ip4-arp: address overflow drops Packet 48 Regards Dharmaray. From: Shwetha Bhandari (shwethab) [mailto:shwet...@cisco.com] Sent: Friday, July 14, 2017 7:39 AM To: Dharmaray Kundargi <dharmaray.kunda...@mavenir.com<mailto:dharmaray.kunda...@mavenir.com>> Subject: Re: [vpp-dev] VPP classifier node plugin not invoked. Have you enabled the classifier on GigabitEthernet1b where you are receiving the packets? set int input acl intfc GigabitEthernet1b… ip4-table 0 set int input acl ? set interface input acl set interface input acl intfc <int> [ip4-table <index>] [ip6-table <index>] [l2-table <index>] [del] From: <vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io>> on behalf of Dharmaray Kundargi <dharmaray.kunda...@mavenir.com<mailto:dharmaray.kunda...@mavenir.com>> Date: Friday, July 14, 2017 at 5:19 AM To: "vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>" <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>> Subject: Re: [vpp-dev] VPP classifier node plugin not invoked. Dave, your inputs please. Thanks Get Outlook for Android<https://aka.ms/ghei36> ________________________________ From: Dharmaray Kundargi Sent: Thursday, July 13, 2017 10:17:47 PM To: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> Subject: VPP classifier node plugin not invoked. Hi, Possibly a repeat question on classifier. But could not get much help from other threads on this regards. I am trying to send UDP traffic from 10.10.122.117 to 10.10.121.179 and expect those to hit to my plugin "my4-dl-input" Don't even see the ip4-classifier in the packet tracer. Below is what I set and see the classifier table and session using CLI. #vppctl classify table mask hex <24 bit mask on IPv4 destination> //I used hex mask here. #vppctl classify session hit-next node my4-dl-input table-index 0 match l3 ip4 dst 10.10.121.x/24 //I used corresponding hex match here. #vppctl show classify table verbose TableIdx Sessions NextTbl NextNode 0 1 -1 -1 Heap: 3 objects, 208 of 2k used, 72 free, 0 reclaimed, 1k overhead, 2044k capacity nbuckets 2, skip 1 match 2 mask 0000000000000000000000000000ffffff000000000000000000000000000000 [1]: heap offset 192, len 1 0: [192]: next_index 14 advance 0 opaque -1 k: 00000000000000000000000000000a0a79000000000000000000000000000000 hits 0, last_heard 0.00 1 active elements 1 free lists And in the code of my4-dl-input node, init function has below peice. vlib_node_add_next (vm, ip4_classify_node.index, my4_dl_input_node.index); vlib_node_add_next (vm, ip6_classify_node.index, my4_dl_input_node.index); Below is the packet tracer output. 00:14:18:666771: dpdk-input GigabitEthernet1b/0/0 rx queue 0 buffer 0xf548: current data 14, length 856, free-list 0, totlen-nifb 0, trace 0x2e PKT MBUF: port 1, nb_segs 1, pkt_len 870 buf_len 2176, data_len 870, ol_flags 0x0, packet_type 0x10 Packet Types RTE_PTYPE_L3_IPV4 (0x0010) IPv4 packet without extension headers IP4: 00:0c:29:7a:a6:81 -> 00:50:56:92:fe:49 UDP: 10.10.122.117 -> 10.10.121.179 tos 0x00, ttl 64, length 856, checksum 0x2f59 fragment id 0x0000, flags DONT_FRAGMENT UDP: 56587 -> 4096 length 836, checksum 0x8ae8 00:14:18:666777: ip4-input-no-checksum UDP: 10.10.122.117 -> 10.10.121.179 tos 0x00, ttl 64, length 856, checksum 0x2f59 fragment id 0x0000, flags DONT_FRAGMENT UDP: 56587 -> 4096 length 836, checksum 0x8ae8 00:14:18:666782: ip4-lookup fib 0 adj-idx 3 : arp GigabitEthernet13/0/0 10.10.121.220/24 flow hash: 0x00000000 UDP: 10.10.122.117 -> 10.10.121.179 tos 0x00, ttl 64, length 856, checksum 0x2f59 fragment id 0x0000, flags DONT_FRAGMENT UDP: 56587 -> 4096 length 836, checksum 0x8ae8 00:14:18:666783: ip4-arp UDP: 10.10.122.117 -> 10.10.121.179 tos 0x00, ttl 64, length 856, checksum 0x2f59 fragment id 0x0000, flags DONT_FRAGMENT UDP: 56587 -> 4096 length 836, checksum 0x8ae8 00:14:18:666788: error-drop ip4-arp: address overflow drops I believe show vlib graph shows the nodes at right place. ip4-lookup ip4-miss [0] my4-dl-input ip4-drop [1] my4_lookup ip4-punt [2] my4_test_input ip4-local [3] dhcp-proxy-to-server ip4-arp [4] lisp-cp-lookup ip4-rewrite-transit [5] vxlan-gpe-encap ip4-classify [6] mpls-post-rewrite ip4-map [7] ip6-map-t-tcp-udp ip4-map-t [8] ip6-map-t-icmp ip4-sixrd [9] ip6-map-t-fragmented ip4-indirect [10] ip6-sixrd ip4-hop-by-hop [11] ip6-map-icmp-relay ip4-add-hop-by-hop [12] ip6-map-ip4-reass ip4-pop-hop-by-hop [13] ip6-map ip4-classify ip4-miss [0] ip4-pop-hop-by-hop ip4-drop [1] ip4-add-hop-by-hop ip4-punt [2] ip4-hop-by-hop ip4-local [3] ip4-lookup-multicast ip4-arp [4] ip4-indirect ip4-rewrite-transit [5] ip4-lookup ip4-classify [6] ip4-classify ip4-map [7] ip4-map-t [8] ip4-sixrd [9] ip4-indirect [10] ip4-hop-by-hop [11] ip4-add-hop-by-hop [12] ip4-pop-hop-by-hop [13] my4-dl-input [14] mpls-policy-encap [15] What’s the missing stuff ? Thanks Dharmaray ________________________________ Please Note: My email address is changing. Starting May 1st 2017 my email will solely be my Mavenir email firstname.lastn...@mavenir.com<mailto:firstname.lastn...@mavenir.com>. All other prior email accounts will become inactive. To ensure continuity, please send all emails to my Mavenir email ID which is currently active and available for use. This e-mail message may contain confidential or proprietary information of Mavenir Systems, Inc. or its affiliates and is intended solely for the use of the intended recipient(s). If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies in your control and contact us by e-mailing to secur...@mavenir.com<mailto:secur...@mavenir.com>. Thank You. This message contains the views of its author and may not necessarily reflect the views of Mavenir Systems, Inc. or its affiliates, who employ systems to monitor email messages, but make no representation that such messages are authorized, secure, uncompromised, or free from computer viruses, malware, or other defects. ________________________________ Please Note: My email address is changing. Starting May 1st 2017 my email will solely be my Mavenir email firstname.lastn...@mavenir.com<mailto:firstname.lastn...@mavenir.com>. All other prior email accounts will become inactive. To ensure continuity, please send all emails to my Mavenir email ID which is currently active and available for use. This e-mail message may contain confidential or proprietary information of Mavenir Systems, Inc. or its affiliates and is intended solely for the use of the intended recipient(s). If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies in your control and contact us by e-mailing to secur...@mavenir.com<mailto:secur...@mavenir.com>. Thank You. This message contains the views of its author and may not necessarily reflect the views of Mavenir Systems, Inc. or its affiliates, who employ systems to monitor email messages, but make no representation that such messages are authorized, secure, uncompromised, or free from computer viruses, malware, or other defects.
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
