Hi,
We have an observation that if we change the device type of our interface from
virtio to e1000 or we keep device type virtio as is and set promiscuous on for
the parent interface of vlan interface, we could get our end to end packet flow
working with VLAN interfaces configured, for both
Hi,
We are trying to debug this issue and we have a question regarding this that If
the packet is seen on the vnet interface of the VM hosting VPP, and not seen in
VPP packet trace, can we debug something at VPP level?
Thanks and Regards,
Chinmaya Agarwal.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You
Hi,
We found another similar kind of an issue
https://lists.fd.io/g/vpp-dev/topic/74220020#16397
But there is no resolution for it as of now.
Thanks and Regards,
Chinmaya Agarwal.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20608):
Hi,
After applying IP and link state from linux (as per my previous post), we
actually see IP and state being copied to VPP as well.
vpp# show interface address
GigabitEthernet0/8/0 (up):
GigabitEthernet0/8/0.1400 (up):
L3 24.24.10.101/24
L3 2001:24:10:a111::101/64
local0 (dn):
tap1 (up):
Hoi,
You have to (for now) apply the IP and link state both in Linux and in VPP
by hand - they will not copy back and forth until Linux CP is fully
committed.
if you type 'show interface address' in VPP, you are not likely to see the
addresses show up there, right?
So add a bit of
vppctl set
Hi,
We have two VMs running on Centos 8.4 and base server running on Centos 7.8.
VM1 is running VPP(v21.06) and VM2 is a normal linux machine. VM1 is connected
to VM2 on GigabitEthernet0/8/0 interface. We created a VLAN interface (with
VLAN id 1400) on both the VMs and we are trying to ping
