netdev - Re: SR-IOV + switchdev + vlan + Mellanox: Cannot ping

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAFtQo5B5oveWMr9PoUEmFnsbxwjQbxtHDcFpsUg646=Z__fJtw@mail.gmail.com>
Date: Tue, 30 Apr 2024 17:29:26 -0400
From: Shane Miller <gshanemiller6@...il.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: netdev@...r.kernel.org
Subject: Re: SR-IOV + switchdev + vlan + Mellanox: Cannot ping

On Mon, Apr 29, 2024 at 7:29 AM Jiri Pirko <jiri@...nulli.us> wrote:
> Nope. Think of it as another switch inside the NIC that connects VFs and
> uplink port. You have representors that represent the switch port. Each
> representor has counter part VF. You have to configure the forwarding
> between the representor, similar to switch ports. In switch, there is
> also no default forwarding.

The salient phrase is "forward between the representor". You seem to
be saying to forward ARP packets from the uplink port (ieth3 e.g.
the NIC that was virtualized) to a port representer (ieth3r0)? Are those
the correct endpoints?

Second, what UNIX tool do I use to forward? As far as I can tell, the
correct methodology is to first create a bridge:

    ip link add name br0 type bridge
    ip link set br0 up

Then do something (but what?) with bridge fdr add as described
here:

https://www.kernel.org/doc/html/v5.8/networking/switchdev.html#static-fdb-entries