The device will still be available in linux, it is managed via ib_uverbs
by dpdk. Thats why it is required to have ib_uverbs, mlx5_core, mlx5_ib
modules required .
-Rupesh
On Fri, Jul 8, 2022 at 9:37 PM Dave Houser wrote:
> OK I am not sure what combination got everything to work but the
>
with flushing the ARP cache,
> which will make the adj incomplete.
>
>
>
> /neale
>
>
>
>
>
> *From: *Rupesh Raghuvaran
> *Date: *Thursday, 4 February 2021 at 12:58
> *To: *Neale Ranns
> *Cc: *vpp-dev@lists.fd.io
> *Subject: *Re: [vpp-dev] Fib entries
adj_nbr_interface_state_change_one, I am not sure about what is
expected from that walk, and the above handling from arp flush have any
conflicts ?
Thanks
Rupesh
On Thu, Feb 4, 2021 at 3:50 PM Neale Ranns wrote:
>
>
> What VPP version is this?
>
>
>
> /neale
>
>
&g
;
>
>
>
> https://github.com/FDio/vpp/blob/master/docs/gettingstarted/developers/fib20/routes.rst#adjacency-source-fib-entries
>
>
>
> /neale
>
>
>
>
>
> *From: *Rupesh Raghuvaran
> *Date: *Wednesday, 3 February 2021 at 12:03
> *To: *Neale Ranns
> *C
k addresses.
>
>
>
> /neale
>
>
>
>
>
> *From: *vpp-dev@lists.fd.io on behalf of Rupesh
> Raghuvaran via lists.fd.io
> *Date: *Tuesday, 2 February 2021 at 17:08
> *To: *vpp-dev@lists.fd.io
> *Subject: *[vpp-dev] Fib entries as per show ip fib for prefi
Hi,
I would like to know the current state of the support for envoy over vpp host
stack. Is there any open source transport socket support for vpp available for
envoy.
Thanks
Rupesh
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13661):
Jon,
There was a patch Neale has provided earlier for a similar issue I faced
earlier. Please see https://lists.fd.io/g/vpp-dev/message/12325
Try out the patch https://gerrit.fd.io/r/#/c/1/
Thanks
Rupesh
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
b 22, 2019 at 6:13 PM Neale Ranns (nranns)
wrote:
>
>
> Hi Rupesh,
>
>
>
> Thank you for spending the time to investigate. I have pushed a patch to
> fix the issue, and another found, after removing the cast that was masking
> the problem.
>
> https://gerrit.fd.io/
oop0
>
> Feature paths configured on loop0...
>
> …
>
> ip6-multicast:
>
>
>
> ip6-unicast:
>
>
>
> DBGvpp# set int ip address del loop0 2001::1/64
>
> DBGvpp# sh int feat loop0
>
> Feature paths configured on loop0...
>
> …
>
> ip6-multicast
icast:
>
> ip6-not-enabled
>
>
>
> it’s the ip6-not-enabled node/feature that is enabled on the interface as
> an input feature that drops the packets.
>
>
>
> /neale
>
>
>
> *De : * au nom de Rupesh Raghuvaran <
> rupesh.raghuva...@gmail.com>
> *Da
Hi,
The vpp core observed with the following trace, this seems to occur when a
mDNS ipv6 packet is getting handled in the mfib_forward_lookup. In the
mfib_lookup, access to ip6_main.mfib_index_by_sw_if_index[sw_index]
results in assertion failure as mfib_index_by_sw_if_index in not yet
Hi,
The vpp core observed with the following trace, this seems to occur when a
mDNS ipv6 packet is getting handled in the mfib_forward_lookup. In the
mfib_lookup, access to ip6_main.mfib_index_by_sw_if_index[sw_index]
results in assertion failure as mfib_index_by_sw_if_index in not yet
12 matches
Mail list logo
