From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marco Gaiarin Date: Wed, 01 Apr 2020 09:48:05 +0000 Subject: Re: tc question about ingress bandwidth splitting Message-Id: <20200401094805.GK3678@lilliput.linux.it> List-Id: References: <74CFEE65-9CE8-4CF7-9706-2E2E67B24E08@redfish-solutions.com> In-Reply-To: <74CFEE65-9CE8-4CF7-9706-2E2E67B24E08@redfish-solutions.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: lartc@vger.kernel.org Mandi! Grant Taylor In chel di` si favelave... > > Interesting... i've found: > > https://blog.scottlowe.org/2013/09/04/introducing-linux-network-namespa= ces/ > > 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 NI= Cs. > 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. --=20 dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia'' http://www.lanostrafamiglia.= it/ Polo FVG - Via della Bont=E0, 7 - 33078 - San Vito al Tagliamento= (PN) marco.gaiarin(at)lanostrafamiglia.it t +39-0434-842711 f +39-0434-842= 797 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)