<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Hi Jochen, </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Could you please help here?</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Regards</div><div class="gmail_default" style="font-family:verdana,sans-serif">Amiya</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 31, 2023 at 1:10 PM David Marchand <<a href="mailto:david.marchand@redhat.com">david.marchand@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello Jochen,<br>
<br>
On Fri, Mar 31, 2023 at 9:07 AM <<a href="mailto:bugzilla@dpdk.org" target="_blank">bugzilla@dpdk.org</a>> wrote:<br>
><br>
> Bug ID 1209<br>
> Summary vmxnet3 interface not receiving any packets with dpdk-22.11.1<br>
> Product DPDK<br>
> Version 22.11<br>
> Hardware x86<br>
> OS All<br>
> Status UNCONFIRMED<br>
> Severity critical<br>
> Priority Normal<br>
> Component ethdev<br>
> Assignee <a href="mailto:dev@dpdk.org" target="_blank">dev@dpdk.org</a><br>
> Reporter <a href="mailto:amohakud@paloaltonetworks.com" target="_blank">amohakud@paloaltonetworks.com</a><br>
> Target Milestone ---<br>
><br>
> Hi,<br>
> I recently upgraded our DPDK to 22.11.1 and observed that the guest vmxnet3<br>
> interface is not receiving any unicast packets. It's able to receive the<br>
> broadcast packets though. We enable promiscuous and all-multicast on the port.<br>
><br>
> rte_eth_promiscuous_enable(port);<br>
> rte_eth_allmulticast_enable(port);<br>
><br>
> This happens when the vswitch has only 2 ports attached.<br>
><br>
> On further triaging,<br>
> - I could find out that on the same setup, dpdk-20.11 works fine.<br>
> - Upon comparing the working scenario and non-working scenario on esx host, I<br>
> could notice that there is some difference in port configuration of vswitch.<br>
><br>
> Below is the snapshot of working case, where the ethFRP:frame routing {<br>
> requested:filter flags is 0x1d.<br>
><br>
> port {<br>
> port index:365<br>
> vnic index:0x00000003<br>
> portCfg:build_1_15_2_vm-v3--p1e3-u2e3<br>
> dvPortId:<br>
> clientName:sjc-cms-esx15-csm02-pan1<br>
> clientType: 5 -> VMM Virtual NIC<br>
> clientSubType: 9 -> Vmxnet3 Client<br>
> world leader:2120158<br>
> flags: 0x40013 -> IN_USE ENABLED WORLD_ASSOC CONNECTED<br>
> Impl customized blocked flags:0x00000000<br>
> Passthru status: 0x8 -> DISABLED_BY_HOST<br>
> fixed Hw Id:00:50:56:b8:20:aa:<br>
> ethFRP:frame routing {<br>
> requested:filter {<br>
> flags:0x0000001d<br>
> unicastAddr:00:50:56:b8:20:aa:<br>
> numMulticastAddresses:0<br>
> multicastAddresses:<br>
> LADRF:[0]: 0x0<br>
> [1]: 0x0<br>
> }<br>
> accepted:filter {<br>
> flags:0x0000001d<br>
> unicastAddr:00:50:56:b8:20:aa:<br>
> numMulticastAddresses:0<br>
> multicastAddresses:<br>
> LADRF:[0]: 0x0<br>
> [1]: 0x0<br>
> }<br>
> }<br>
><br>
><br>
> For the non-working case the flag is set to 0x09.<br>
><br>
> port {<br>
> port index:365<br>
> vnic index:0x00000003<br>
> portCfg:build_1_15_2_vm-v3--p1e3-u2e3<br>
> dvPortId:<br>
> clientName:sjc-cms-esx15-csm02-pan1<br>
> clientType: 5 -> VMM Virtual NIC<br>
> clientSubType: 9 -> Vmxnet3 Client<br>
> world leader:2120158<br>
> flags: 0x40013 -> IN_USE ENABLED WORLD_ASSOC CONNECTED<br>
> Impl customized blocked flags:0x00000000<br>
> Passthru status: 0x8 -> DISABLED_BY_HOST<br>
> fixed Hw Id:00:50:56:b8:20:aa:<br>
> ethFRP:frame routing {<br>
> requested:filter {<br>
> flags:0x00000009<br>
> unicastAddr:00:50:56:b8:20:aa:<br>
> numMulticastAddresses:0<br>
> multicastAddresses:<br>
> LADRF:[0]: 0x0<br>
> [1]: 0x0<br>
> }<br>
> accepted:filter {<br>
> flags:0x00000009<br>
> unicastAddr:00:50:56:b8:20:aa:<br>
> numMulticastAddresses:0<br>
> multicastAddresses:<br>
> LADRF:[0]: 0x0<br>
> [1]: 0x0<br>
> }<br>
> }<br>
> filter supported features: 0 -> NONE<br>
> filter properties: 0 -> NONE<br>
> rx mode: 0 -> INLINE<br>
> tune mode: 0 -> default<br>
> fastpath switch ID:0xffffffff<br>
> fastpath port ID:0xffffffff<br>
> }<br>
><br>
> I think these are some of the flags set by vmxnet3 device and in dpdk-22.11,<br>
> its not updating the flags.<br>
<br>
As a maintainer of the net/vmxnet3 driver, could you please register<br>
to bugzilla?<br>
And please have a look.<br>
<br>
<br>
Thanks!<br>
<br>
-- <br>
David marchand<br>
<br>
</blockquote></div>