From: Herbert Wolverson <herberticus@gmail.com>
To: Jan Rovner <jan.rovner@diadema.cz>
Cc: "libreqos@lists.bufferbloat.net" <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] A newbie question - bridge mode
Date: Thu, 29 Dec 2022 10:27:32 -0600 [thread overview]
Message-ID: <CA+erpM6KqFb-h4xikEF71CJg1YCWWvm1b6g1G9cSBrYo14FGEA@mail.gmail.com> (raw)
In-Reply-To: <f1a596d72f2c46e4b9e51e836a542be4@diadema.cz>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
Hi!
The default setup operates purely as a transparent bridge (one interface
in, one interface out) - LibreQoS doesn't do any routing. V1.3 can read
inside VLANs and shape traffic flows inside VLANs (including nested VLANs).
V1.4 will add an option to use a single interface with an "in" and "out"
VLAN, allowing for "on a stick" transparent bridging, and speed up the
bridge process quite a bit.
I hope I read that right, I haven't had enough coffee this morning!
Thanks,
Herbert
On Thu, Dec 29, 2022 at 10:15 AM Jan Rovner via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:
> Hello,
>
> I like libreqos project and initially I would like to ask about the
> possibility of operating in bridge mode, even not oficially fully
> supported.
>
> My question targets underlying technologies like XDP a others and their
> performance: is it possible to achieve the same (or similar) performance on
> QoS on bridging traffic shaper - with VLANs - as on routed setup?
>
> Thank you.
> Jan Rovner
>
>
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>
[-- Attachment #2: Type: text/html, Size: 2056 bytes --]
next prev parent reply other threads:[~2022-12-29 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 16:15 Jan Rovner
2022-12-29 16:27 ` Herbert Wolverson [this message]
2022-12-29 16:34 ` Dave Taht
2023-03-18 19:16 ` [LibreQoS] Bifrost XDP-Accelerated Bridge + preserve VLAN tags? Jan Rovner
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
List information: https://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+erpM6KqFb-h4xikEF71CJg1YCWWvm1b6g1G9cSBrYo14FGEA@mail.gmail.com \
--to=herberticus@gmail.com \
--cc=jan.rovner@diadema.cz \
--cc=libreqos@lists.bufferbloat.net \
/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