I am sure either the route for GW/Arp for the directly connected host are
missing.run packet trace and see what is happening to your ping packets.
Thanks,Sam
On Tuesday, December 15, 2020, 01:16:54 AM PST, Shiv
wrote:
Hi Team,
I am trying to get VPP working on an interface in an
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 wrote:
#yiv9801683627 #yiv9801683627 -- _filtered {} _filtered {} _filtered
{}#yiv9801683627 #yiv9801683627
HiI 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
I responsed earlier!
Hi,
Why can't you just add your plugin to run after ethernet-input and enable it on
all physical interfaces so that you can avoid spanning.
For your approach, are you sure you added your node to run after span-input and
correctly placed on a feature-arc?pls run "show vlib
Why can't you just add your plugin to run after ethernet-input and enable it
on all physical interfaces so that you can avoid spanning.
For your approach, are you sure you added your node to run after span-input and
correctly placed on a feature-arc?pls run "show vlib graph" it will tell you
Hi,I am on 18.10 and trying to enable reassembly and fragmentation. It is
working fine for vxlan and vxlan-gpe tunnels but IPSec it is not.We set
physical interface MTU to be 1500 and IPSEC interface MTU to 1350 to give room
for encryption.
The issue we are seeing is packets are getting
Hi Ole,Thanks for the quick response.
I am setting MTU to 1500 and trying to test larger packets. (by enabling
reassembly feature on interfaces)It seems to work fine on regular interfaces.
and On tunnel interfaces packets are getting struck in reassembly saying
inconsistent UDP/IP lengths.So
