From: Stephen Hemminger <stephen@networkplumber.org>
To: Arjun Mehta <arjunmeht@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Rx issues with Linux Bridge and thunderbolt-net
Date: Fri, 8 Dec 2023 09:37:26 -0800 [thread overview]
Message-ID: <20231208093726.371fd47e@hermes.local> (raw)
In-Reply-To: <4E2F8965-E609-44F2-A361-270082367DC9@gmail.com>
On Fri, 8 Dec 2023 10:30:39 -0700
Arjun Mehta <arjunmeht@gmail.com> wrote:
> Hi Stephen, thank you for the reply.
>
> Proxmox does use a kernel derived from Ubuntu I believe (eg. kernel for Proxmox 8.1 which is what I'm using is 6.5.11-6-pve derived from Ubuntu 23.10). Not sure if there have been any modifications to the Linux Bridge in it.
> https://pve.proxmox.com/wiki/Proxmox_VE_Kernel#Proxmox_VE_8.x
>
> Long shot, but do you happen to know of any workarounds with the Wifi interface issue you mentioned that would mitigate this issue? Maybe they would apply here.
>
> I will also post to the Proxmox forums about this issue to flag for them.
>
> Arjun
With VM's the issue is that many hosts have source address protection in
either the SW or HW for VF's to prevent address spoofing.
This means you can't run a L2 bridge in the guest.
The only mitigation is to do some form of Layer 2 NAT.
Possible, but I have never done it, and likely to have scaling issues.
prev parent reply other threads:[~2023-12-08 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 19:57 Rx issues with Linux Bridge and thunderbolt-net Arjun Mehta
2023-12-07 22:37 ` Stephen Hemminger
2023-12-08 17:30 ` Arjun Mehta
2023-12-08 17:34 ` Arjun Mehta
2023-12-08 17:37 ` Stephen Hemminger [this message]
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=20231208093726.371fd47e@hermes.local \
--to=stephen@networkplumber.org \
--cc=arjunmeht@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).