From: Marco Gaiarin <gaio@sv.lnf.it>
To: lartc@vger.kernel.org
Subject: Re: tc question about ingress bandwidth splitting
Date: Wed, 01 Apr 2020 09:48:05 +0000 [thread overview]
Message-ID: <20200401094805.GK3678@lilliput.linux.it> (raw)
In-Reply-To: <74CFEE65-9CE8-4CF7-9706-2E2E67B24E08@redfish-solutions.com>
Mandi! Grant Taylor
In chel di` si favelave...
> > 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.
> It depends what you mean by "link".
Beh, something similar to what i do now for IFB:
tc filter add dev eth1 parent ffff: protocol ip prio 50 \
u32 match ip src 0.0.0.0/0 \
flowid :1 \
action mirred egress redirect dev ifb0
> > But after that, i need to use ebtales?
> Did you mean "bridge"?
AH! Sure, i meant 'bridge', not bond, sorry...
> You can also use traditional routing between the physical and the vEth NICs.
> You can even move the physical NIC into a Network Namespace.
> It *REALLY* depends on what you want to do.
I suppose, throw away 'ifb' and use veth in place. ;-)
With 'tc' command above, i 'pipe' ingress to ifb; surely i can create a
'route' between phisical and veth interfaces, but clearly i have to
manage a bit of routing and so on...
Can you provide me some examples? Thanks.
--
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-04-01 9:48 UTC|newest]
Thread overview: 13+ 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
2020-03-24 17:57 ` Grant Taylor
2020-03-24 18:17 ` Grant Taylor
2020-03-26 3:44 ` Philip Prindeville
2020-03-26 4:03 ` Grant Taylor
2020-04-01 9:48 ` Marco Gaiarin [this message]
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
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=20200401094805.GK3678@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox