From: Shane Miller <gshanemiller6@gmail.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org
Subject: Re: SR-IOV + switchdev + vlan + Mellanox: Cannot ping
Date: Tue, 30 Apr 2024 17:29:26 -0400 [thread overview]
Message-ID: <CAFtQo5B5oveWMr9PoUEmFnsbxwjQbxtHDcFpsUg646=Z__fJtw@mail.gmail.com> (raw)
In-Reply-To: <Zi-Epjj3eiznjEyQ@nanopsycho>
On Mon, Apr 29, 2024 at 7:29 AM Jiri Pirko <jiri@resnulli.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
next prev parent reply other threads:[~2024-04-30 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 20:35 SR-IOV + switchdev + vlan + Mellanox: Cannot ping Shane Miller
2024-04-27 10:26 ` Jiri Pirko
2024-04-28 20:24 ` Shane Miller
2024-04-29 11:29 ` Jiri Pirko
2024-04-30 21:29 ` Shane Miller [this message]
2024-05-01 18:16 ` Benjamin Poirier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFtQo5B5oveWMr9PoUEmFnsbxwjQbxtHDcFpsUg646=Z__fJtw@mail.gmail.com' \
--to=gshanemiller6@gmail.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.