Hi Mojtaba,
I suspect that this is due to IOAM decap being broken in 18.01+. Removal of
IOAM metadata added at the IOAM decap node depends on the ACL match whose
result is checked during v6 hbh processing. If decap fails IOAM options are
leaked to host2 in the setup below. Linux kernel network
Hi all,
just a kind reminder that in two days we have an API freeze, so only
low-risk changes with no API modifications will be accepted until we
pull the stable/1908 branch.
--a
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13603): https://list
Thanks Steven
Yes, I have 1G hugepages on container. Can you tell me how to use native vpp
virtio? How can I use it to connect container to host. I don't want to use NIC.
Thanks
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13604): https://lists
Maintenance reminder
On 07/25/2019 04:09 PM, Vanessa Valderrama wrote:
>
> *What:*
>
> FD.io system maintenance
>
> * Jenkins
> o OS updates
> o Upgrade from 2.164.3 to 2.176.2
> + https://jenkins.io/changelog-stable/
> o Update plug-ins
> o Memory upgrade
>
>
create interface virtio
Or just use memif interface. That is what it is built for.
Steven
From: on behalf of "mojtaba.eshghi"
Date: Monday, July 29, 2019 at 5:50 AM
To: "vpp-dev@lists.fd.io"
Subject: Re: [vpp-dev] #vpp Connecting a VPP inside a container to a VPP inside
host using vhost-vi
Hi,
You can reorder the route and ABF programming as a work around.
I’ll have a fix shortly.
/neale
De : au nom de "fdr.koz...@yandex.com"
Date : lundi 29 juillet 2019 à 08:24
À : "vpp-dev@lists.fd.io"
Objet : [vpp-dev] SIGSEGV when adding route and abf with the same gateway
Hi vpp-dev
Whe
Hi,
I am not able to able to access https://git.fd.io/ . Looks like certificate is
expired on 30 July 2019. I have attached the screenshot.
Thanks,
Akshay
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13608): https://lists.fd.io/g/vpp-dev/messag
