From: Marco Gaiarin <gaio@sv.lnf.it>
To: lartc@vger.kernel.org
Subject: Re: tc question about ingress bandwidth splitting
Date: Tue, 24 Mar 2020 09:21:48 +0000 [thread overview]
Message-ID: <20200324092148.GH13243@lilliput.linux.it> (raw)
In-Reply-To: <74CFEE65-9CE8-4CF7-9706-2E2E67B24E08@redfish-solutions.com>
Mandi! Philip Prindeville
In chel di` si favelave...
> > 1st: Address the fact that you can only effectively rate limit what you send. So, change the problem so that you rate limit what is sent to your router. I would do this by having the incoming connection go into a Network Namespace and a new virtual connection to the main part of the router. This Network Namespace can then easily rate limit what it sends to the main part of the router, on a single interface.
> This is the same problem that ifb solves, right?
> I’m not sure I want to assume that Namespaces are available in all scenarios.
Interesting... i've found:
https://blog.scottlowe.org/2013/09/04/introducing-linux-network-namespaces/
and i've not understood how can i 'link' phisical interfaces with
vethX.
Using bond? But after that, i need to use ebtales?
ifbX interfaces are very limited by not having connection tracking,
having some 'real' interfaces would be a must!
--
dott. Marco Gaiarin GNUPG Key ID: 240A3D66
Associazione ``La Nostra Famiglia'' http://www.lanostrafamiglia.it/
Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento (PN)
marco.gaiarin(at)lanostrafamiglia.it t +39-0434-842711 f +39-0434-842797
Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
http://www.lanostrafamiglia.it/index.php/it/sostienici/5x1000
(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)
next prev parent reply other threads:[~2020-03-24 9:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 21:56 tc question about ingress bandwidth splitting Philip Prindeville
2020-03-22 22:59 ` Grant Taylor
2020-03-24 6:51 ` Philip Prindeville
2020-03-24 9:21 ` Marco Gaiarin [this message]
2020-03-24 17:57 ` Grant Taylor
2020-03-24 18:17 ` Grant Taylor
2020-03-26 3:44 ` Philip Prindeville
2020-03-26 3:53 ` Fwd: " Philip Prindeville
2020-03-26 12:50 ` Toke Høiland-Jørgensen
2020-03-26 4:03 ` Grant Taylor
2020-04-01 9:48 ` Marco Gaiarin
2020-04-03 22:44 ` Grant Taylor
2020-04-06 9:13 ` Marco Gaiarin
2020-04-13 1:11 ` Grant Taylor
2020-04-17 9:58 ` Marco Gaiarin
-- strict thread matches above, loose matches on Subject: below --
2020-03-22 18:20 Philip Prindeville
2020-03-23 6:47 ` Gáspár Lajos
2020-03-23 9:36 ` Marc SCHAEFER
2020-03-23 18:15 ` Philip Prindeville
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=20200324092148.GH13243@lilliput.linux.it \
--to=gaio@sv.lnf.it \
--cc=lartc@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.