Xiaopeng,
Sorry did I say rx? The flow probe is attached to the tx path.
Feel free to submit a patch for rx support.
Cheers
Ole
> On 25 Dec 2019, at 02:58, Xiaopeng Bai wrote:
>
>
> Hi, guys!
> Before i test the flowprobe plugin, I get the features from the FEATURE.YAML
> in the flowprob
Is this something that VPP should be enabling instead though?
Thanks,
Chris.
> On Dec 20, 2019, at 2:26 AM, jacicson1...@163.com wrote:
>
> This problem is solved.
>
> Just one command:
> ip link set enp5s0f1 allmulticast on
>
> So that VF can receive multicast packets, such as ipv6 neighbor
The while idea is that vpp or any other vf driver should not be able to enable
this
--
Damjan
> On 25 Dec 2019, at 13:48, Christian Hopps wrote:
>
> Is this something that VPP should be enabling instead though?
>
> Thanks,
> Chris.
>
>> On Dec 20, 2019, at 2:26 AM, jacicson1...@163.co
Coverity run failed today.
Current number of outstanding issues are 2
Newly detected: 0
Eliminated: 0
More details can be found at
https://scan.coverity.com/projects/fd-io-vpp/view_defects
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#14968): ht
My mistake, I thought the ip link command was being using to enable
allmulticast for the VF on the host (not the PF).
I don't know the gory details of SRIOV, but it sounds like from what you are
saying that the multicast filtering (perhaps promiscuous mode too?) is not
actually isolated per VF