svn commit: r341586 - head/sys/dev/mlx5/mlx5_en

[Andrey V. Elsukov]

On 16.04.2019 18:26, Slava Shwartsman wrote:
> Thanks for letting us know about this regression.
> I would like to try to reproduce this issue in house.
> 
> Can you please share the exact steps to reproduce it?
> - Can I reproduce the issue with B2B setup?
> - What is the route command you used to make the route between the VLANs?
> - What app are you using to generate the traffic?
> 

I think this can be reproduced on simple router, where single mce(4)
interface is used as parent for several vlan(4) interfaces. E.g.

[host1] vlan100 <--> mce0.100 [gateway] mce0.200 <--> vlan200 [host2]
    10.0.0.1        10.0.0.254      192.168.0.254    192.168.0.1

gateway:
sysctl net.inet.ip.forwarding=1

host1:
route add 192.168.0.0/24 10.0.0.254

host2:
route add 10.0.0.0/24 192.168.0.254
ping 10.0.0.1

I.e. you need to make setup, where ingress and egress interface is the
same - mce0.

-- 
WBR, Andrey V. Elsukov

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 554 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/svn-src-all/attachments/20190416/41197695/attachment.sig>