From: Stephen Hemminger <stephen@networkplumber.org>
To: Ali Shirvani via Bridge <bridge@lists.linux-foundation.org>
Subject: Re: [Bridge] How to connect more than 200 interfaces to a bridge
Date: Wed, 9 Nov 2022 08:51:09 -0800 [thread overview]
Message-ID: <20221109085109.6b0f87d3@hermes.local> (raw)
In-Reply-To: <nWfVbvdboX65r0xMXv0iZCj8TH7c8vStvilCD3Ilx5Y42yoHh34rJHJBMy8y4HhqXWXM0n3tLhLD870c863UjI20HBSxM8qwJlLMxuPjg0g=@protonmail.com>
On Wed, 09 Nov 2022 10:51:27 +0000
Ali Shirvani via Bridge <bridge@lists.linux-foundation.org> wrote:
> Hello everyone,
>
> It seems we reach the Linux bridge limitation on the number of interfaces in a single bridge. Currently, we have 210 tap interface in a bridge, and we suffer from more than 50% packet loss when we ping the IP address of the virtual machine that uses one of the tap interfaces in the bridge.
> Do you know how we can connect more than 200 VMs virtual interfaces to a bridge?
>
> Best regards,
> Ali
>
> Sent with [Proton Mail](https://proton.me/) secure email.
The upper limit on interfaces per bridge should be 1023.
That limitation comes from spanning tree.
You might bet able to improve performance by disabling flooding to those tap devices.
Normally, any broadcast/unknown/multicast must be copied and flooded to each interface.
next prev parent reply other threads:[~2022-11-09 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 10:51 [Bridge] How to connect more than 200 interfaces to a bridge Ali Shirvani
2022-11-09 16:51 ` Stephen Hemminger [this message]
2022-11-09 19:25 ` Ali Shirvani
2022-11-09 19:55 ` Stephen Hemminger
2022-11-09 20:08 ` Stephen Hemminger
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=20221109085109.6b0f87d3@hermes.local \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux-foundation.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