* traffic control on multiple interfaces
@ 2014-10-27 12:36 Akshat Kakkar
2014-10-29 15:58 ` Andy Furniss
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Akshat Kakkar @ 2014-10-27 12:36 UTC (permalink / raw)
To: lartc
I am having a linux system with 4 nics (eth0-3) which is acting as a
router. I want to give my user a fix bandwidth of 2mbps upload and
2mbps download. His traffic can come from eth0 or eth1 and it can go
out from eth2 or eth3 (depending on services he want to access). So
for this, I require tc to be working on "eth2 and eth3" as single
entity (for upload traffic); and "eth0 and eth1" as single entity (for
download traffic). I want to use egress control and not ingress (using
IMQ, etc.)
What are options available to achieve this?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: traffic control on multiple interfaces
2014-10-27 12:36 traffic control on multiple interfaces Akshat Kakkar
@ 2014-10-29 15:58 ` Andy Furniss
2014-10-29 16:01 ` Andy Furniss
2014-10-30 4:35 ` Akshat Kakkar
2 siblings, 0 replies; 4+ messages in thread
From: Andy Furniss @ 2014-10-29 15:58 UTC (permalink / raw)
To: lartc
Akshat Kakkar wrote:
> I am having a linux system with 4 nics (eth0-3) which is acting as a
> router. I want to give my user a fix bandwidth of 2mbps upload and
> 2mbps download. His traffic can come from eth0 or eth1 and it can go
> out from eth2 or eth3 (depending on services he want to access). So
> for this, I require tc to be working on "eth2 and eth3" as single
> entity (for upload traffic); and "eth0 and eth1" as single entity (for
> download traffic). I want to use egress control and not ingress (using
> IMQ, etc.)
>
> What are options available to achieve this?
Use 2 ifbs for tc and direct to one from eth0/1 and the other eth2/3.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: traffic control on multiple interfaces
2014-10-27 12:36 traffic control on multiple interfaces Akshat Kakkar
2014-10-29 15:58 ` Andy Furniss
@ 2014-10-29 16:01 ` Andy Furniss
2014-10-30 4:35 ` Akshat Kakkar
2 siblings, 0 replies; 4+ messages in thread
From: Andy Furniss @ 2014-10-29 16:01 UTC (permalink / raw)
To: lartc
Andy Furniss wrote:
> Akshat Kakkar wrote:
>> I am having a linux system with 4 nics (eth0-3) which is acting as
>> a router. I want to give my user a fix bandwidth of 2mbps upload
>> and 2mbps download. His traffic can come from eth0 or eth1 and it
>> can go out from eth2 or eth3 (depending on services he want to
>> access). So for this, I require tc to be working on "eth2 and eth3"
>> as single entity (for upload traffic); and "eth0 and eth1" as
>> single entity (for download traffic). I want to use egress control
>> and not ingress (using IMQ, etc.)
>>
>> What are options available to achieve this?
>
> Use 2 ifbs for tc and direct to one from eth0/1 and the other
> eth2/3.
Forgot to put - for egress on the eths if you don't have any "real"
qdisc on the eth you won't be able to add the filters to redirect, so
just add say prio.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: traffic control on multiple interfaces
2014-10-27 12:36 traffic control on multiple interfaces Akshat Kakkar
2014-10-29 15:58 ` Andy Furniss
2014-10-29 16:01 ` Andy Furniss
@ 2014-10-30 4:35 ` Akshat Kakkar
2 siblings, 0 replies; 4+ messages in thread
From: Akshat Kakkar @ 2014-10-30 4:35 UTC (permalink / raw)
To: lartc
Thanks Andy of the info.
I want to use htb and filters to classify traffic.
Can IFBs provide good performance when handling data rate of 1gbps
with pkt size of say 64 bytes?
On Wed, Oct 29, 2014 at 9:31 PM, Andy Furniss <adf.lists@gmail.com> wrote:
> Andy Furniss wrote:
>>
>> Akshat Kakkar wrote:
>>>
>>> I am having a linux system with 4 nics (eth0-3) which is acting as
>>> a router. I want to give my user a fix bandwidth of 2mbps upload
>>> and 2mbps download. His traffic can come from eth0 or eth1 and it
>>> can go out from eth2 or eth3 (depending on services he want to
>>> access). So for this, I require tc to be working on "eth2 and eth3"
>>> as single entity (for upload traffic); and "eth0 and eth1" as
>>> single entity (for download traffic). I want to use egress control
>>> and not ingress (using IMQ, etc.)
>>>
>>> What are options available to achieve this?
>>
>>
>> Use 2 ifbs for tc and direct to one from eth0/1 and the other
>> eth2/3.
>
>
> Forgot to put - for egress on the eths if you don't have any "real"
> qdisc on the eth you won't be able to add the filters to redirect, so
> just add say prio.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-10-30 4:35 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-10-27 12:36 traffic control on multiple interfaces Akshat Kakkar
2014-10-29 15:58 ` Andy Furniss
2014-10-29 16:01 ` Andy Furniss
2014-10-30 4:35 ` Akshat Kakkar
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.