From: Marco Gaiarin <gaio@sv.lnf.it>
To: lartc@vger.kernel.org
Subject: Re: tc question about ingress bandwidth splitting
Date: Fri, 17 Apr 2020 09:58:36 +0000 [thread overview]
Message-ID: <20200417095836.GH5106@lilliput.linux.it> (raw)
In-Reply-To: <74CFEE65-9CE8-4CF7-9706-2E2E67B24E08@redfish-solutions.com>
Mandi! Grant Taylor
In chel di` si favelave...
> Say that there are two physical hosts on the network; A and B.
I think i'm missing most of the background here; there's some
doc/paper/wiki/... about NS/VETH i can read about?
Still i miss how can i 'link' various interfaces... for example:
> |
> +--+--+
> | WAN | DHCP
> | | New network namespace.
> | vE0 | Static
> +--+--+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> | vE1 | Static
> | | Original (main / default / unnamed) network namespace.
> | LAN | Static
> +--+--+
> |
>
> Apply tc rules to vE0 for traffic going down. Apply tc rules to vE1 for
> traffic going up.
This is exactly what i think to do. But... how 'routing' (in
loose/sparse sense, not literally) works on namespaces?
EG, normally i have public IP address assigned to WAN interface, and
private one assigned to LAN; LAN and WAN are not 'linked' between them,
apart routing and firewall rules.
I don't understand how NS/VETH came into this play... and is surely my
fault!
In my head i suppose that WAN is 'linked' (again, in loose/sparse
sense) to a couple of VETH interfaces as above, and i use vE1 to shape
egress traffic and vE0 to shape egress traffic (that is, ingress for
vE1).
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-17 9:58 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
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 [this message]
-- 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=20200417095836.GH5106@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.