I once experienced LACP not UP because the mode on vpp (lacp-static) did not
match the mode on switch (lacp-dynamic). try changing the lacp mode on your
switch.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22281): https://lists.fd.io/g/vpp-dev/m
I have the same problem but on ipv4 where the default route on linuxCP/NL is
not read / lost from vpp, vpp only reads direct routes. but when I add a static
route from vppctl everything is back to normal.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Onli
Hi Pim,
I've tried populating the IPv6 neighbor table on the Linux side, but it still
doesn't work.
>
>
>
> najib@DPDK:~$ ip nei show dev xe1.921
>
>
>
> 2401:1700:1:1::bd lladdr c4:ad:34:4d:d2:a8 PERMANENT
>
>
>
>
>
> najib@-DPDK:~$ ping 2401:1700:1:1::bd
>
>
>
> PING 2401:1700:1:
Hi Petr,
i didn't disable the ping plugin in vpp. but that only happens in some vlan
interfaces. in other vlan ping can work from vpp and host.
>
> vpp# show interface addr
> TenGigabitEthernetb5/0/3.914 (up):
> L3 2401:1700:1:1::a2/126
>
>
> vpp# show ip neighbors TenGigabitEthernetb5/0/3.91
hello i found a problem with vpp.
i use the plugin from https://github.com/pimvanpelt/lcpng
when i put the ip in the vlan and ping to another host via vpp the result is
normal but if i ping from the linux host directly the result is not working.
>
> vpp# show ip neighbors TenGigabitEthernetb5/0
two workers
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21453): https://lists.fd.io/g/vpp-dev/message/21453
Mute This Topic: https://lists.fd.io/mt/91329115/21656
Mute #automation:https://lists.fd.io/g/vpp-dev/mutehashtag/automation
Group Owner:
