Hi Dave,Thanks for tip. I enabled feature on the rx interface. It worked.
ThanksSam M
On Tuesday, September 15, 2020, 04:16:07 AM PDT, Dave Barach via
lists.fd.io <dbarach=cisco....@lists.fd.io> wrote:
#yiv9801683627 #yiv9801683627 -- _filtered {} _filtered {} _filtered
{}#yiv9801683627 #yiv9801683627 p.yiv9801683627MsoNormal, #yiv9801683627
li.yiv9801683627MsoNormal, #yiv9801683627 div.yiv9801683627MsoNormal
{margin:0in;font-size:11.0pt;font-family:sans-serif;}#yiv9801683627
.yiv9801683627MsoChpDefault {font-size:10.0pt;} _filtered {}#yiv9801683627
div.yiv9801683627WordSection1 {}#yiv9801683627
Sounds like you may not have enabled the “test-node” feature on the rx
sw_if_index. “show interface <name> features”... Note that if the packet comes
from a bridge group, I suspect that you’ll need to enable the feature on the
bvi vs the rx interface.
This is the kind of problem which “pcap dispatch trace ...” tends to help chase
down.
D.
From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf OfCaffeine Coder via
lists.fd.io
Sent: Tuesday, September 15, 2020 2:56 AM
To: Vpp-dev <vpp-dev@lists.fd.io>
Subject: [vpp-dev] Issue with adding new new node in between ip4-input n
ip4-lookup
Hi
I am trying to add a new node to parse packet data after all vxlan decoding,
ip4-input and before doing IP lookup. This code flow is is working fine for
packets coming from vxlan-gpe/IPSec tunnels and not for vxlan.
Traffic is working fine except not going through this new "test-node".
The issue i am seeing with vxlan packet is: packet is going directly
ip4-lookup. i.e from ip4-vxlan-bypass->vxlan4-input->l2
(input,learn,fwd)->ip4-input->ip4_lookup. But I can't hook my node in between
ip4-input and ip4_lookup.
If I do vxlan-gpe or IPSEC, i can hook the test node properly i.e.
ip4-vxlan-gpe-bypass->vxlan4-gpe-input->ip4-input->test-node->ip4_lookup.
I tried adding and changing ".runs_before" and ".runs_after" in my test-node.
Still I am not able to stitch my test-node, if traffic coming from vxlan
tunnels.
"show vlib graph" is very useful command to debug for not able to find what
else might be missing for vxlan. I do see that vxlan packet going through lot
of l2 nodes. Does that need any special config for making non vpp native l3
nodes to work fine?
Any pointers will be helpful.
Thanks
Sam.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17436): https://lists.fd.io/g/vpp-dev/message/17436
Mute This Topic: https://lists.fd.io/mt/76859804/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
